Re:Microservices Ending Up as a Distributed Monolith
by Randgalt on Friday March 04, 2016 @12:02AM
(#11222127)
It wasn't practical. But that's what we had at the time.
[ Parent
| on HN ]
Re:Microservices Ending Up as a Distributed Monolith
by hardwaresofton on Friday March 04, 2016 @02:29AM
(#11222497)
Just to chime in here -- I think this is a relatively common happening. I've found that companies with lots of teams developing software often look to "standardize" the software being used to create things like web services/pieces of infrastructure.
This often starts with creating a local nexus server (in java land), then is followed relatively quickly by creating a "X company commons" for "everyone" to use.
Re:Microservices Ending Up as a Distributed Monolith
by BurningFrog on Friday March 04, 2016 @11:28AM
(#11224816)
I see :)
That kind of problem is tricky, since nobody decided to make it that way.
A system worked great when it was instituted, and was never changed, but is now no longer good.
Anyway, if/when I become Netflix CTO, I will make sure this is fixed!