Upgrade to Pro — share decks privately, control downloads, hide ads and more …

API Gateway in Microservice Architecture

forLoop
September 03, 2016

API Gateway in Microservice Architecture

Ridwan Olalere, A software developer at PaywithCapture talked about why and how they implemented API gateway in their microservice architecture

forLoop

September 03, 2016
Tweet

More Decks by forLoop

Other Decks in Programming

Transcript

  1. Constraints • Spaghetti Integration • Unnecessary payload to clients •

    Client changes every time there is a change in any of the microservices • Tight coupling • Impossible to move fast • Latency problems for mobile clients • Multiple round trips for mobile clients • Excess network calls Complex setup
  2. What is an API Gateway ? An application layer/edge service

    that can manage client interaction with a cluster of APIs. A BFF described in the previous slide is a kind of API gateway Features of API Gateways. 1. Routing 2. Authentication 3. Rate Limiting 4. Caching 5. Dependency resolution 6. Response filtering 7. Request/Response Intercept 8. Granular control and logging 9. Response composition 10. Load balancing 11. Service discovery
  3. New Entrant → Bruff Express An API gateway built on

    Nodejs as an express middleware. https://github.com/darilldrems/bruff-express Features • Routing • Request Interceptor • Response Matching • Request dependency resolution • Response filtering • Response caching • Extensible NB: since bruff is an express middleware, you can have other middleware mapped before bruff for other functions like authentication.
  4. Experience using bruff • Its simple to use • It

    makes client apps really fast • It allowed us build core microservices for everyone • Fast delivery of composite APIs