I'm new to SA Dev space (my interactions have always been western and predominantly US).
SA Dev space is very toxic and focuses on the wrong things. People wake up everyday and comment on who is doing what wrong and what cannot be done.
They don't wake up BUILD, SHARE, REPEAT.
It's just commentary 24/7 like footie twitter. Very exhausting man. Focus on you and what you can do for yourself which might or might not benefit the wider society
๐ฌ๐ผ๐ ๐ฑ๐ผ๐ป'๐ ๐ต๐ฎ๐๐ฒ ๐ฎ๐ป ๐ฎ๐ฟ๐ฐ๐ต๐ถ๐๐ฒ๐ฐ๐๐๐ฟ๐ฒ ๐ฝ๐ฟ๐ผ๐ฏ๐น๐ฒ๐บ. ๐ฌ๐ผ๐ ๐ต๐ฎ๐๐ฒ ๐ฎ ๐๐๐ฎ๐ด๐ฒ ๐ฝ๐ฟ๐ผ๐ฏ๐น๐ฒ๐บ.
What I've seen in my career is that most teams pick architecture based on hype, not real needs. They see how Netflix runs microservices and assume that's the answer. A 5-person startup running microservices isn't engineering. It's cosplaying.
Here's what you need to know about each one:
๐ ๐ผ๐ป๐ผ๐น๐ถ๐๐ต โ You're still figuring out what to build. A monolith lets you move fast, refactor easily, and deploy one thing. Start here, especially if you're a startup. And make it modular.
๐ ๐ถ๐ฐ๐ฟ๐ผ๐๐ฒ๐ฟ๐๐ถ๐ฐ๐ฒ๐ โ Multiple teams stepping on each other. Deployments take hours. One bad change breaks everything. That's when you split, and only along real team boundaries. If you can't afford a platform team, you can't afford microservices.
๐ฆ๐ฒ๐ฟ๐๐ฒ๐ฟ๐น๐ฒ๐๐ โ You want to stop managing infrastructure for workloads that don't need it. Works well until vendor lock-in creeps in. By the time you notice, migration costs are enormous.
A well-structured (modular) monolith beats poorly designed microservices every time.
You can mix them too. Monolith core with serverless for specific workloads is often the right call.
Stop choosing architecture for where you want to be. Choose it for where you are.
I know boycotts divide us, but in this case, a boycott against Clover feels like a worthy cause. We had been moving toward a society that recognises, even in law, that children should never be the target of marketing for adult products. That line now feels increasingly blurred.