Part 3 of Microservices on Light Cloud. Push one service until Light Cloud adds instances, read what happened, and fix the two limits that surprise everyone: requests per instance and database connections.
Load test a Light Cloud service with oha, watch it scale from zero to five instances, and learn why concurrency and database connection pools decide how well autoscaling works.
Read post
Install the Light Cloud MCP server in Claude Code with one command, ask it to deploy a folder, and get a live URL. A real session with screenshots: deploy, redeploy, password.
Julia
Three minutes, no laptop, and a long drive still in my legs. I pitched the platform at KitchenPitch, FreshMango's pitch day, and left out the best thing we are building. Here is why that was the right call, what the mentors fixed afterwards, and the part where I did not recognize the accelerator CEO.
Julia
GAIA-X, EuroStack, and now a 180-million-euro sovereign tender with Google inside the tent. Europe keeps trying to build a thing when what it lacks is a property, and the property is portability.
Hyperscaler capital is stampeding toward AI factories, and the ordinary developer workload, a container, a database, a preview environment, is nobody's priority. That neglect is the opening every developer cloud is built on.
Allow several browser origins with CORS, rotate the secret your services share without dropping a request, and add a timeout between services, step by step on Light Cloud.
Julia
Deploy a React frontend, a Node.js API, a Python FastAPI API and PostgreSQL from one GitHub monorepo on Light Cloud, step by step, with every screen shown.
Julia
Three Mile Island is being restarted for a single customer. Hyperscalers are buying reactors because the constraint on cloud capacity stopped being racks or chips and became megawatts, and that breaks a decade of assumptions about regions.
CoreWeave went from crypto-mining afterthought to a public company with a $99 billion backlog by selling exactly one thing well. The specific companies may wobble. The procurement habit they taught buyers won't.
The loudest cloud exit in the industry ended quietly in the summer of 2025 when 37signals' last petabyte left S3. Their published numbers are real. So are the reasons most companies copying them would lose money.
On the morning of November 18, 2025, EU regulators published their list of critical cloud providers. That afternoon, Cloudflare fell over and demonstrated it. The autumn outage cluster wasn't three stories. It was one.
Exit egress fees died in 2024 and the EU Data Act finishes the job in January 2027. Celebrate briefly. The billing lock died precisely because it was the lock that mattered least, and the four that matter are doing fine.
Since January 2025, EU financial entities must hold documented exit strategies for critical ICT providers, and since November 2025 the providers themselves are under direct supervision. The plan is now a compliance artifact. A real one is still rare.