Containous believes that the new feature will bring higher levels of TCP routing support, advanced routing capabilities, and better developer experiences.

Gérald Croës, VP of Engineering at Containous, spoke to DevOps Online exclusively to discuss Traefik 2.0.

How has version 2.0 done thus far with users?

Users have been very eager to play with Traefik 2.0 — the announcement of its GA was very well received. We measure adoption based on the feedback we get, and we already see many developers moving to 2.0. This feedback is very important to us; it helps us steer the open source project in the right direction.

What do you attribute to the popularity of Traefik 2.0 to?

TCP support and the new possibilities available with middleware, new TLS options, canary, and mirroring are the reasons that sway people into migrating to Traefik 2.0. Traefik’s popularity has always been about two things: community and simplicity, and the two get along very well. Traefik 2.0 makes configuration logical and enables endless possibilities. Users can assemble pieces and shape routes to fit into their system perfectly. And of course, Traefik 2.0 still embeds features that go beyond routing, like metrics, tracing, and so on. For contributors, 2.0 also makes their life more comfortable; maintainers did their best to provide an architecture that will let people add many features (and we can’t wait to see what will happen).

Why does the industry need an updated version of the open source edge router?

Updating our open source edge router is the next logical step toward simplifying users’ stack. With TCP support, Traefik can now handle even more traffic than before, and users can now rely only on Traefik for routing everything. Our aim with Traefik is to continue to put it into the category of software that you run and forget… because it just works.

The post Containous discuss the need for updated open source edge routers appeared first on DevOps Online North America.

Containous hope that the new service will be lightweight, easy to use, and full-featured. To keep cloud at its core, it is built on top of the cloud-native edge router, Traefik.

By doing all of this, developers will be able to connect, secure and monitor traffic from their microservice-based application.

Using meshes

Meshes are becoming a critical part of microservice deployment as network communications become increasingly complex. Service meshes allow operations teams and developers to have the ability to manage inter-service communication with a single management layer.

The Maesh service panders to the implementation of microservices and helps to create a better experience for developers by suggesting an easy way to secure, monitor and connect to the network traffic in a Kubernetes environment.

Improvements for developers

Developers are able to optimise internal traffic, visualise traffic patterns, and secure communication channels, all while improving application performance.

“With Maesh, Containous continues to innovate with the mission to drastically simplify cloud-native adoption for all enterprises,” said Emile Vauge, CEO, Containous. “We’ve been proud of how popular Traefik has been for developers as a critical open source solution, and we’re excited to now bring them Maesh.”

The company says that the up and running of the service can be done in minimal time with a non-invasive approach which Containous feel will assist with improvements overall.

Ultimately, the company hopes that Maesh will reduce the difficulty of routing and observing service-to-service communications in any Kubernetes deployment.

The post Containous releases a simpler service to ease microservices adoption appeared first on DevOps Online North America.