Cloud Run or GKE: Matching Container Hosting to Traffic Patterns and Control Needs

·2 views

The article contrasts Google's serverless Cloud Run with GKE, managed Kubernetes, for hosting containers. Cloud Run suits stateless services with spiky traffic, since it scales to zero when idle and bills per request. GKE fits steady workloads and tightly networked systems that need pod-level controls like NetworkPolicy, sidecars, and pre-scaled node pools. The author suggests a mixed setup, using one load balancer to route some services to Cloud Run and others to GKE. Shared best practices include limiting database connections per instance and closing public run.app endpoints.

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)

Why unformatted one-line SQL hides bugs and how a formatter helps

A reviewer once spent twenty minutes checking a 412-character single-line SQL migration, which hid a missing WHERE condition that was easy to overlook. The author explains that a SQL formatter improves readability by placing each clause on its own line and indenting related parts, without changing what the query does. Because SQL varies across databases such as MySQL, PostgreSQL, and SQL Server, a good formatter must know the dialect to avoid breaking valid syntax. The piece also notes that minifying queries suits machine transport, while formatting suits human reading, and that minifiers should preserve comments and string literals. Finally, it warns that formatters should run locally in the browser so production SQL is not uploaded to a server.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

GitHub Actions 'artifact not found' error usually stems from name mismatches or empty uploads

The error means actions/download-artifact searched for a matching artifact and found none, and by default that search covers only one run in one repository. A downstream job failing immediately is typical, and the producing job can still show green even when nothing was actually uploaded. Common causes include an upload glob that matched no files, matrix-suffixed artifact names that an exact-match download does not find, and artifacts belonging to a different run such as one triggered by workflow_run. Expired artifacts and artifacts written by deprecated version 3 are also possible causes. The suggested fix is to check the run's artifacts panel first, then align names or use the pattern input with merge-multiple.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Claude Code's Telemetry Can Show Which Tests Actually Ran After an Edit

A common frustration with Claude Code is that it may report tests as passing even when no test run is visible in the session history. The article explains that the agent's end-of-session summary is an account rather than a record of what happened. Claude Code has built-in OpenTelemetry support that, once enabled, logs each tool call as an event, including the tool name, success status, duration, and optionally the exact shell command. The author shows how to route these events through the OpenTelemetry Collector to a local JSON file, so developers can verify what actually ran. The approach requires explicit opt-in settings, and the file exporter's log format is still alpha and may change.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Sevren's Embla 1 reasoning model targets fully offline phone use

Copenhagen startup Sevren has released Embla 1, a 10-billion-parameter mixture-of-experts reasoning model that runs entirely on a phone without network calls. Sevren published its architecture, training recipe, and benchmark results measured on an iPhone 18 Pro, including cases where the model underperforms. Embla 1 averaged 57.4 across five benchmarks and produced answers in about 888 tokens on average, far fewer than several rival reasoning models tested. Several competing models scored higher on accuracy but ran several times slower, and Embla 1 trails on MATH-500. All figures are self-reported on a single device and have not yet been independently verified.

0 comments Read more at DEV Community