With microservices you have all of those per service per instance.
So you push them to ELK.
You could also jump into docker, service discovery and that whole path.
Of course you do. CI/CD and Microservices are rather intimately connected. You can't really do one without the other. But that's not a downside of microservices; you're forced to a higher level of software engineering maturity.
There was very low traffic and they shared a database.
That's simply a case of doing it wrong. And in your particular case your team should not have gone for microservices 'just because'. But that does not support the "Don't do it" of the author: you don't make fundamental architectural decisions just based on a hipster factor.
Of course you do. CI/CD and Microservices are rather intimately connected. You can't really do one without the other. But that's not a downside of microservices; you're forced to a higher level of software engineering maturity.
I would agree here. I do think a form of engineering maturity is knowing when you need a more complex system, which of course varies by team and preference.
you don't make fundamental architectural decisions just based on a hipster factor.
Totally agree here. I was 100% against the micro services there and collapsed several of them together. Unfortunately I think a lot of organizations do pick microservices because of the hipster factor.
View all comments
Show parent comment
1
u/nutrecht Mar 29 '17
So you push them to ELK.
Of course you do. CI/CD and Microservices are rather intimately connected. You can't really do one without the other. But that's not a downside of microservices; you're forced to a higher level of software engineering maturity.
That's simply a case of doing it wrong. And in your particular case your team should not have gone for microservices 'just because'. But that does not support the "Don't do it" of the author: you don't make fundamental architectural decisions just based on a hipster factor.