3 ms·
You are right, I meant more in terms of software developer popularity, apologies for my bad phrasing. But I do think microservices will become bigger, we'll ha
by oreganoz 8y ago
You are right, I meant more in terms of software developer popularity, apologies for my bad phrasing.
But I do think microservices will become bigger, we'll have to wait and see how k8s pans out.
- tannhaeuser 8y agoSorry for nitpicking, but I think the central value proposition of microservices/SOA is that you communicate with you backend via well-defined network protocols rather than eg. procedure calls so that the client and server technology stack doesn't matter. Containers have nothing to do with it.
- oreganoz 8y agoI'm just mentioning that containers may make implementing & deploying microservices easier and thus a more popular solution.
- amirouche 8y agoHow a network protocol is more specified that a procedure call?
- tannhaeuser 8y agoIt's not. The benefit is that - you can keep a service running long after the project that created it has disbanded and/or the runtime and build environment is deprecated on a given O/S - you don't necessarily need to deep-dive into the business logic of legacy services - you can replace a service implementation with another one running on another stack without having to adapt service clients - you can change auth mechanism outside of the service implementations - you can scale out (CPU-bound) services onto multiple hosts Mind you, these benefits are not achieved by using microservices/SOA in itself; the contribution of microservices/SOA, however, is that these design goals aren't impossible to achieve because of architected reasons.