5 ms·
Raises some good points, but I think the title isn't really correct. It's not "don't use microservices" - it's more about making sure you understand the implica
by BillinghamJ 10y ago
Raises some good points, but I think the title isn't really correct. It's not "don't use microservices" - it's more about making sure you understand the implications of having a microservice architecture, and making sure it's not an excuse for not writing a monolith (or SOA) properly.
- StabbyCutyou 10y agoI do wish I had titled it better, as most people have (rightfully) dinged me on this one ;)
- johnnydoebk 10y agoI'll go against the majority (or vocal minority?) and say: I like your title, it's good because it attracts attention (I wouldn't read the post if it were a "understand the implications of having a microservice architecture" or whatever others recommend).