Microservices on I am Lino

How to Make Technical Decisions Without Selling Your Soul to the Hype

Mon, 16 Mar 2026 00:00:00 +0000

There are technical decisions made with data, time, and a bit of judgment.

And then there are the other kind: the ones made after watching three conference talks, scrolling through two X threads, and half-reading a case study , that somehow end with phrases like “well… now that we’ve set it all up, we might as well get some use out of it, right?”

One day you’re perfectly happy with your API running on a plain old VPS, and the next you find yourself building a serverless-event-driven-data-mesh-multi-cloud architecture because you watched a video claiming “that’s how Netflix does it.”

Microservices, Monoliths, and Other Mythical Creatures

Mon, 09 Mar 2026 00:00:00 +0000

Some architecture decisions are made calmly, with data, over a nice cup of coffee.

And then there’s real life, where you pick your tech stack the same way you pick a favorite sports team: because you saw it in a cool conference talk, because some big-name company uses it, or because someone tweeted that “if you don’t have 80 microservices running on Kubernetes, you’re a dinosaur.”

Next thing you know, you’ve gone from a lovable monolith — a little messy but functional — to a circus of services where nobody really knows what talks to what, your cloud bill is terrifying, and the only microservice running flawlessly is the one that charges you at the end of the month. All because, at some point, somebody stopped asking the only question that actually matters:

Modern Architecture Fundamentals (No Snake Oil Included)

Mon, 02 Mar 2026 00:00:00 +0000

Imagine someone telling you: “I’ve set up my app on an on-premises server with Oracle 9i, but don’t worry, it’s modern architecture because it runs Docker.” That’s the moment you understand why people bail on architecture meetings pretending they have a dental emergency.

When we talk about “modern architecture,” we’re not talking about slapping Kubernetes onto everything or cramming as many buzzwords as possible into a slide deck. We’re talking about something far less flashy and far more difficult: building systems that survive in today’s ecosystem without going obsolete or blowing up every time the business changes a “simple” requirement. Systems that live in the cloud (or several clouds), communicate over networks that fail, store data scattered across half the planet, and still need to keep responding when someone decides “we also need to go multi-region because an important client said so.”