4 ms·
Microservices are damn hard to implement correctly. Think how much math and algorithms must there be to correctly, test, version your model and API, load balanc
by akerro 8y ago
Microservices are damn hard to implement correctly. Think how much math and algorithms must there be to correctly, test, version your model and API, load balance, gather logs, collect logs, archive logs, grep in logs, setup VMs/Dockers, DNS+DHCP and firewalls, load balance databases (master/slaves?) and your services, horizontal scaling maybe?, manage privileges and access, manage disk space, store and collect user-uploaded/generated files, isolate environments...
If you don't understand these concepts and how much work must be don't to correctly implement microservice architecture - you SHOULD STAY with monoliths, they are much easier.
http://principlesofchaos.org/ http://principlesofchaos.org/
- sobani 8y agoAll of these things you mentioned are either also required for a monolith (like DNS+DHCP) or are required for neither (isolated environments). Does that mean that because of all the work required to properly set those up for a monolith, we better stay with microservices?