Breaking News: Grepper is joining You.com. Read the official announcement!
Check it out

Main Reasons of Why should use API Gateway

Anjali Sharma answered on February 2, 2023 Popularity 5/10 Helpfulness 1/10

Contents


More Related Answers

  • api gateway lambda 502
  • What is API Gateway Pattern in Microservices?
  • Amazon API Gateway -Differences between REST - HTTP API
  • 10 differences between API gateway and load balancer in point-by-point format
  • usage of API gateways
  • API Gateway
  • What is Amazon API Gateway?
  • Explain the API Gateway pattern
  • aws api gateway java example
  • Drawbacks of the API Gateway pattern
  • pros and cons of api gateway
  • Which of the following statements about API gateways are false
  • API-Gateway with Hystrix
  • The Solution - API Gateway Patterns
  • API Gateway Pattern - Summarized
  • Request Flow of API Gateway Pattern
  • What is the primary role of an API Gateway ?
  • Which of the following is NOT typically a responsibility of an API Gateway ?
  • How does an API Gateway help to improve the performance of a microservice-based application ?
  • Which of the following is NOT related to API Gateway Pattern ?
  • exposing rest endpoint using aws lambda
  • APIS - APIS THROUGH AN API GATEWAY LAYER
  • API gateway exposing your API securely
  • options for api gateway and authorization server
  • API Gateway for calling backend services
  • API Gateway Restful API Development with Synchronous Invocations
  • API Gateway Restful API Development with Synchronous Lambda Event Sources.
  • Architecture of API Gateway
  • Amazon API Gateway Use Cases

  • Main Reasons of Why should use API Gateway

    0

    Client Can't Manage Communications

    The client applications can try to handle multiple calls to microservice endpoints,

    not manageable when it comes to communicates with different protocols like http,

    GraphQL, gRPC and WebSocket.

    ▪ Complex Client Code

    Cause to lots of requests to the backend services, create possible chatty

    communications. Increases latency and complexity on the UI side. Becomes

    complex client code.

    ▪ Strong Coupling

    Creates coupling between the client and the backend. The client needs to know

    how the specific microservices are decomposed. Increase the coupling between

    client and services and also makes it harder to maintain the client.

    ▪ Cross-cutting Concerns

    Authentication, Authorization, Rate Limiting, SSL certifications, Logging,

    Monitoring, Load Balancing and Circuit Breaker. Implementing all these crosscutting concerns for every microservice is not a good solution.

    https://www.linkedin.com/pulse/key-reasons-using-api-gateway-microservices-architecture-chad-ng/

    Popularity 5/10 Helpfulness 1/10 Language whatever
    Source: Grepper
    Link to this answer
    Share Copy Link
    Contributed on Feb 02 2023
    Anjali Sharma
    0 Answers  Avg Quality 2/10

    Closely Related Answers



    0

    Api Gateway can be used to apply authentication and authorization. However this is not always recommended. If the backend services not only called from gateway this will cause a security breach.

    https://www.linkedin.com/pulse/do-you-absolutely-need-microservice-api-gateway-its-trap-love-hasija/

    Popularity 3/10 Helpfulness 1/10 Language javascript
    Source: Grepper
    Tags: whatever
    Link to this answer
    Share Copy Link
    Contributed on Feb 21 2023
    Pragya Keshap
    0 Answers  Avg Quality 2/10


    X

    Continue with Google

    By continuing, I agree that I have read and agree to Greppers's Terms of Service and Privacy Policy.
    X
    Grepper Account Login Required

    Oops, You will need to install Grepper and log-in to perform this action.