Microservice Networking within the Enterprise
Those who want more insight into how internal corporate networks should support microservices could do worse than read a new Citrix-sponsored series on The New Stack, penned by Pankaj Gupta, senior director of cloud native application delivery solutions at Citrix.
“The choice of proxy architecture and application delivery controllers (ADCs) truly matter,” Gupta writes. “It must provide the right level of security, observability, advanced traffic management and troubleshooting capabilities and complement your open source tools strategy. Additionally, the proxy architecture must accommodate both north-south (N-S) traffic and inter-microservices east-west (E-W) traffic needs.”
In part one of the series, Gupta lays out the basic architectural options — two-tier ingress, unified ingress, service mesh and service mesh lite — and offers tips about the right approach for your enterprise. Part two takes a deep dive into the two-tier ingress proxy architecture, the quickest and simplest architecture for deploying applications in production for both cloud native novices and experts alike. And part three tackles an approach of using the service mesh, which, as TNS readers know, is a popular approach of late for handling internal, or “east-west,” traffic.
We look forward to the next, and final installment of this series where Gupta explores the “service mesh lite” approach, which promises the benefits of the service mesh, but is easier to implement and manage. Stay tuned, only on The New Stack.