Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Meshing Around and Creating Chaos in 2019

DZone 's Guide to

Meshing Around and Creating Chaos in 2019

Service meshes and the chaos engineering practices that have evolved with them will lead to more robust applications in 2019.

· DevOps Zone ·
Free Resource

It's that time of year again — time to reflect on the past year and anticipate the year ahead. This year, I expect us to be Meshing Around and Creating Chaos. Let me explain further:

In 2019, interest in and deployments of service meshes will continue to rise. Expect new emergence in the space and a number of existing offerings to affix “Mesh” onto their offering name as they jump on the coattails of this hot technology. While some service meshes assist in modernizing existing, non-containerized workloads, they are particularly helpful in sophisticated, distributed systems, given that such deployments only exacerbate the need for visibility, control, and security of their networks. The good news here is that for the non-network-savvy, service meshes immediately eliminate hard-to-solve challenges, facilitating a decoupling of developers and operators, who may now exert control over their services’ networks declaratively and independently — without the need for rolling a new release. As something of a third step in containerized deployments, service meshes captured much mind share in 2018 and will only grow in popularity and adoption in 2019 and 2020.

In 2019, the principles and tools in the emergent practice space of Chaos Engineering will evolve and expand in use as the complexity and rate of change of large-scale distributed systems demand new tools and techniques for increasing reliability and resiliency. Some organizations will push past chaos engineering tools such as Chaos Monkey inducing machine failures, skip Chaos Kong evacuating entire regions, and move to Gremlin to perform precise experiments on their path to improving resiliency through orchestrated chaos. It’s through exploration of the impact of increased latency and methodical failure of specific services that service teams will build confidence in their system’s capability to withstand turbulent conditions in production — and begin to sleep more soundly in 2019.

Topics:
devops ,chaos engineering ,service mesh ,microservices ,containers

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}