Hacker News new | ask | show | jobs
by jorgecurio 3802 days ago
I find that microservice is just splitting a problem into multiple small problems while the overhead of fixing each problem is uniform, so you end up with a huge technical debt, and eventually fall into dependency issues.

Distributed computing is going to be less efficient than centralized system, now you have multiple vectors susceptible attack...

I find the best architecture is a detached standalone-tenancy meaning a copy of the web application distributed as an image running on a different server assets distributed across different web host providers. 1 clone of your app = 1 domain = 1 customer

This way DDOS attack requires knowing all of your customer's domains which runs your web application, and it dramatically increases the cost of launching a successful and prolonged DDOS attack. The attacker even with a huge bandwidth rate now has to spread it thin across hundreds of your customers website.

Sure your own website hosted on amazon s3 could take a hit but your customers are still able to run their business without drama from foreign state actors or xbox players.

1 comments

Microservices are good, when you have a big team. Microservices are bad, if you have a small team.

Microservices is about management, not about code.