Source: thenewstack.io
Don’t Force Containers and Disrupt Workflows
How do you allow people to use their technologies in their workflows? The first thing you do is not force people to use containers, says https://github.com/devops-rob, a senior developer advocate at HashiCorp, in this episode of The New Stack Makers.
Consul from HashiCorp is one of the early implementations of service mesh technology, https://thenewstack.io/implementing-service-discovery-of-microservices-with-consul/ “It comes with a full-featured control plane with service discovery, configuration, and segmentation functionality.
“As I say, I think people feel that if you’re using service meshes, that means you’re using containers, right?
I think the idea is that if more service meshes out, they make themselves a bit more flexible and meet people where they are.
Consul from HashiCorp is one of the early implementations of service mesh technology, https://thenewstack.io/implementing-service-discovery-of-microservices-with-consul/ “It comes with a full-featured control plane with service discovery, configuration, and segmentation functionality.
“As I say, I think people feel that if you’re using service meshes, that means you’re using containers, right?
I think the idea is that if more service meshes out, they make themselves a bit more flexible and meet people where they are.
Related Articles
Community Partners
DevOps Careers