Hacker News new | ask | show | jobs
by zurawiki 1118 days ago
Happy to see the tide turning on microservices. Monoliths make sense for small teams in terms of development and operational complexity.

I was pleasantly surprised to see that AWS offers EC2 pretty beefy instances these days. 64 CPU cores, 128+ GB RAM should scale to most of what a small team would ever need...
1 comments
rbanffy 1118 days ago
The goal of microservices isn't to have many (no pun intended) "micro" "services" doing each a little bit of work, but to allow an organization to deploy parts of an application separately.

Even if all the two 64-core 128GB nodes on the cluster run copies of all the two services.

link
zurawiki 1118 days ago
When an organization is large and siloed, there is value in decoupling different parts of the application, assuming the ownership and expertise are properly distributed.

As the comment below mentions, microservices is a fashion–one that took off among overly-staffed eng teams. Having separate parts of the app to deploy can be a liability for a small team frequently deploying breaking changes.

link
rbanffy 1117 days ago
> When an organization is large and siloed

I'd argue that lose coupling is a core principle of good software architecture. Bing able to deploy separately only makes it more convenient to manage.

> frequently deploying breaking changes

That's never a good sign. Frequently deploying, yes. Frequently breaking, not so much.

link