Re:Microservices – Please, don’t
by PerfectElement on Saturday September 24, 2016 @08:30PM
(#12573261)
Those days are not gone. Outside of the HN bubble there's still a lot of successful monolithic application development going on. Not every project needs to scale to the size of Twitter.
[ Parent
| on HN ]
From what I've seen it's about 50/50 these days. Most of the monolithic applications still around are legacy J2EE or Ruby on Rails.
People seem to forget that microservices isn't new. It's just SOA all over again.
I believe that a huge amount of SOA in production wouldn't qualify as microservices - especially enterprise SOA.
Heck, I'd bet a lot of enterprise SOA is just a giant crufty monolith with a bunch of its functionality exposed via service endpoints. I suppose that a pretty decent approach - add endpoints to a monolith. As long as the service interfaces remain the same, you can bust it up into as many medium or micro sized services as are necessary on the back end and the users of your services won't notice the difference.
You can also mix'n'match. Have a monolithic entity that does most of the work, and split out the heavy stuff into it's own microservice which can be independently scaled.
(Sub in any other reason to separate a service for 'heavy stuff' - written in a more appropriate language for the function, etc)