Re:Kubernetes at Box: Microservices at Maximum Velocity
by jdoliner on Friday July 22, 2016 @03:33PM
(#12146157)
Could you explain a bit more why things get harder if service X is using service Y? I'm sort of the opposite of you in that I haven't used much of the Mesos stack yet but am familiar with Kubernetes. Services depending on each other is pretty trivial in Kubernetes so I'm wondering what makes it so hard in mesos.
[ Parent
| on HN ]
Re:Kubernetes at Box: Microservices at Maximum Velocity
by avitzurel on Friday July 22, 2016 @04:08PM
(#12146405)
It's not that it's hard to do it with Marathon/Mesos, it's just hard to maintain an application with dependent services.
It's just a matter of my personal comfort, I like to use isolated services that just use messaging and fire a message when their done with their role.
Even if Kube handles everything perfectly, it's still harder to maintain application with inner-service communication, hard to follow problems/errors/stack traces etc...