Home Cd software Solo.io Adds Legacy SOAP Integration for Gloo Edge 1.8 – The New...

Solo.io Adds Legacy SOAP Integration for Gloo Edge 1.8 – The New Stack

20
0

Service mesh integration software vendor Solo.io has released version 1.8 of its native Kubernetes ingress controller and Gloo Edge API Gateway to General Availability (GA). Version 1.8 provides integration for legacy Simple Object Access Protocol (SOAP) web services and other functionality, as Solo seeks to enhance API-centric support to evolve needs in cloud-native environments.

Based on the Envoy Proxy traffic proxy for service mesh architectures, Gloo Edge now helps DevOps teams integrate decades-old SOAP through a single API.

Gloo Edge 1.8 support for SOAP is “the biggest breakthrough feature” of the release, Chris Gaun, director of product management for Solo.io, told The New Stack.

In a blog post, Guan described how SOAP, a turn-of-the-century XML messaging protocol, “remains prevalent today for enterprise web services in a number of industries, including financial services and healthcare. health”.

Yet, “Unfortunately, SOAP (and associated legacy middleware applications) are hampering large-scale modernization efforts because there has not been a viable migration approach in the market,” Guan wrote. “Organizations have not been able to cope with the incremental depreciation of SOAP web services over time without great difficulty. “

Gloo Edge Enterprise 1.8, with the addition of support for Extensible Stylesheet Language Transformations (XSLT), was designed to “modernize SOAP / XML clients and endpoints without completely eliminating SOAP from your web services portfolio. Guan wrote.

For organizations struggling to decommission their SOAP web services – a process that can take years in some cases – using Gloo Edge Enterprise 1.8 allows DevOps teams to maintain backward compatibility while adopting modern protocols. (like Kubernetes) and run them in parallel, Guan noted.

The need for SOAP support is also an example of how organizations often struggle to integrate a wide range of their legacy infrastructures with more modern environments. As businesses move to microservices architectures, for example, they “expose more of their legacy legacy systems as services,” Erik Frieberg, chief marketing officer of Solo.io, told The New Stack. Since many systems use SOAP / XSLT as their messaging protocol, Gloo Edge 1.8 also supports the older messaging protocol “so you can combine services that use REST and gRPC with services that use SOAP,” Frieberg said. .

“This allows organizations to standardize Gloo Mesh as an API gateway for their microservices architectures, as it supports both newer, cloud-native APIs and traditional SOAP protocols,” said Frieberg.

Flagger orchestrating a Canary version in conjunction with the Gloo Edge API Gateway. (Source: Solo.io)

Additionally, Gloo Edge 1.8 was designed to improve support for CI / CD pipelines as DevOps teams adopt processes that use A / B testing, blue / green mirroring, and more secure Canary test builds. to help improve the reliability of production versions. “These processes allow organizations to release software to small groups of samples to ensure that new features work as intended before releasing them to everyone,” Frieberg said.

Solo.io also worked with platform provider GitOps Weaveworks to add Flagger, which is used to automate Canary deployments, to the upstream open source Envoy proxy and to make Flagger a native part of Gloo Edge, Frieberg explained. .

“Since the requests for these applications pass through an API gateway, it is important that the gateway is integrated with these processes to efficiently and effectively deploy the applications,” said Frieberg.

Other features of Gloo Edge 1.8 include:

  • Helm Usability Improvements: Gloo Edge 1.8 was designed to simplify exposing an organization’s own values ​​in Helm, which is used to define, install, and upgrade Kubernetes applications.
  • Schema in Gloo Edge CRDs: Gloo Edge allows the use of schemas to validate CRD functions to help “avoid accidentally breaking anything”.
  • Writing of the access log for improved security: the possibility of writing certain fields while providing a readable activity report.

Feature image via Pixabay.


Source link

LEAVE A REPLY

Please enter your comment!
Please enter your name here