Microsoft Killed CodePush: Here's What React Native Teams Need in an OTA Replacement

·1 views

Microsoft shut down its hosted Visual Studio App Center service on March 31, 2025, ending the managed CodePush service widely used by React Native developers for over-the-air (OTA) updates. While a self-hostable CodePush server was released, teams must now evaluate replacement OTA strategies that fit their production needs. Key considerations include compatibility boundaries between JavaScript bundles and native binaries, multi-channel rollout controls, and percentage-based or targeted staged deployments. Robust failure handling is equally critical, requiring device-side recovery mechanisms that can detect crash loops and revert to a last-known-good bundle without relying on a successful JavaScript launch. Teams must also account for artifact integrity verification and whether the system delivers full bundles or delta patches to manage bandwidth and update size.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Snowflake to Databricks Migration: Real Costs and Trade-offs Teams Must Know

Migrating from Snowflake to Databricks is often justified on cost savings, but teams that end up satisfied typically moved to consolidate ML, streaming, and GenAI workloads alongside analytics data. The two platforms differ significantly beneath the surface, particularly in how storage is handled — on Databricks, storage costs appear on the cloud provider's bill rather than the platform bill, a distinction finance teams must understand upfront. Migration approaches range from a quick lift-and-shift to a full re-architecture, and choosing the wrong strategy can eliminate any expected savings, since Snowflake-shaped tables on Databricks compute carry similar costs. While moving the data itself is relatively straightforward using bulk Parquet exports and Delta Lake, translating the code — especially complex stored procedures — is where timelines and budgets tend to overrun. Automated SQL conversion tools can handle standard queries, but the harder edge cases require significant manual engineering effort that is often underestimated at the planning stage.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Use Docker Engine as a Kubernetes Runtime via cri-dockerd on Ubuntu

Since Kubernetes 1.24 removed native dockershim support, users who need Docker Engine as a node runtime must now rely on cri-dockerd, an open-source CRI adapter maintained by Mirantis. The setup involves installing Docker Engine from its official repository, configuring the systemd cgroup driver, and pointing the kubelet to the cri-dockerd socket during cluster initialization. This approach is recommended only for specific use cases, such as teams with Docker-dependent tooling, shared image stores, or vendor requirements that assume Docker Engine. While the shared image store between kubelet and Docker is a convenience, administrators are advised to use crictl for managing cluster containers to avoid interfering with Kubernetes-managed processes. For most users without these specific needs, containerd remains the simpler and more reliable alternative.

0 comments Read more at DEV Community

ProgrammingHacker News ·

Insufficient source content to report accurately

The provided source contains only a link and metadata, with no article body or factual details available. Summarizing without the full text would require fabricating information. No reliable summary can be produced from this input. Please provide the full article text for accurate reporting.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

Developer builds real-world quoting system with .NET 10 and Blazor Server

A developer built a full budget management system for a glass shop that previously handled all quotes manually, using .NET 10 and Blazor Server as the core stack. The project included a product catalogue with multi-supplier pricing, margin calculations, PDF export, and local network deployment. Key challenges included designing Entity Framework Core delete rules to reflect actual business logic, such as preventing client deletion when quotes exist. A recursive in-memory search component was built to filter a nested product catalogue without hitting the database on every keystroke. The hardest bug involved Blazor buttons silently stopping work due to global layout components rendering in static mode outside the interactive render tree, revealing that render mode in Blazor Web App propagates only to descendants, not sibling components.

0 comments Read more at DEV Community