Search for a command to run...
A breakdown of microservices architecture, how it reduces downtime, improves deployment speed, and when it makes sense over a monolith.
Self-taught Software Engineer from Singapore (that eventually goes to school for it). Passionate about building new stuff that helps people save time!
No comments yet. Be the first to comment.
My stint with Apple Music has come to an unfortunate end. I’m not trying to make it sound like a huge breakup note reveal. I’m actually writing this to reflect on my time with both services. It was an
Why my RAG system failed using ChromaDB and local embeddings — and how better context and data structuring fixed retrieval accuracy.
How we used Roblox Studio and Lua to build a 3D cybersecurity CTF game for students — and what we learned from bugs, refactors, and live demos.
Is Swift worth learning for React Native developers? An in-depth comparison of SwiftUI, SwiftData, DX, performance, and ecosystem maturity.
How I built a personalized graduation website with Next.js, Redis, access codes, and a server-side countdown to stop cheating.
While intern-ing at a small company, one of the problems we face is our infrastructure of software. It was never built to scale. Sure, scaling is managed by our service providers but we're talking about maintenance of the application and urgent bug fixes in the application. Here is the current infrastructure of our application:
Now here comes a problem that occurs a lot. We receive notice that one of our modules are broken (Payment Module). This would require the whole backend to have a downtime while we fix/patch and re-deploy. Other modules (e.g. Search) would be affected too because of the downtime. In this modern world where there are millions, if not billions of users of the internet, is this really the way to go?
Micro-services solves the problem by lifting different modules of our application in a separate container. This allows for the easy plug-in-plug-out scenario. Let's say here is the proposed Micro-services architecture of our current app (not comprehensive):
Simple, we do not need to bring down the whole backend to fix one module. We can instead plug-out, fix and plug it back in, redeploy the affected service without affecting other services (that are not reliant)
In the old architecture, the Backend is affected (as a whole)
In the new architecture, only the Payment service is affected
While discovering this new technology, I am sure that I am not the only one who sees Micro-services the same way. Companies such as Shopee, Google and Netflix are adopting and using Micro-services in their products to serve large scale software.
You can run Micro-services locally using Docker. Writing backend services that adopts the Micro-services pattern is available using Nest.js
