Looking for a reference architecture for microservices and load balancing

[#1]

We use fairly basic API proxies in Apigee Edge that route API calls to a couple of target services. One of the services is a microservice hosted in AWS (ECS containers). We plan to add more microservices, and are researching different options for routing, load balancing, and service discovery. Apigee has some built in load balancing, AWS offers its own load balancing. Would someone point me at a example or reference architectures that could be used as a starting point?

[gnanasekaran]

Hello @Alexey Dmitriyev, good question - I am not sure if we have published any reference architecture.

Just sharing my opinions -

> Apigee Edge is great for routing across different microservices,

> Apigee Edge is great for Service discovery as well as visibility

But Apigee Load balancing a multiple instances of a single microservice will be tricky

A container management / orchestration service like ECS would typically offer deep integration for management, scaling of a single microservice which could be really hard to replicate or there is no reason to replicate in Apigee

I don't know about ECS much, but my opinion is based on our recent work with Cloud Foundry and Kubernetes

So I would leave management of a individual microservice [configuration, management, scale etc..] to a container managed solution and use Edge for managing how different microservices and external consumers would discover and interact with each other

EDIT - found some materials on this topic

http://docs.apigee.com/api-services/content/edge-integration-aws

http://apigee.com/about/tags/pivotal

Thanks,

Mukundha

[#3]

Hello

Is there any documentation for how Apigee does service discovery when backend services are deployed on Kubernetes?

[shuklaankur]

Hey Kavitha - does this help? https://community.apigee.com/questions/44330/apigee-integration-with-kubernetes-service-discove.html