Best of API Gateway2022

  1. 1
    Article
    Avatar of communityCommunity Picks·3y

    Netflix System Design- Backend Architecture

    Netflix accounts for about 15% of the world's internet bandwidth traffic. Netflix operates in two clouds Amazon Web Services and Open Connect (Netflix content delivery network) The overall Netflix system consists of three main parts. Zuul as its API gateway is built to allow dynamic routing, traffic monitoring, and security, resilience to The Netty handlers on the front and back of the filters.

  2. 2
    Article
    Avatar of devtoDEV·4y

    What is CORS?

    Cross-Origin Resource Sharing (CORS) is an HTTP-based security mechanism controlled and enforced by the client. It allows a service to indicate any origin other than its own from which the client can request resources. A request may be blocked by CORS policy not only because of the incorrect origin, but also incorrect HTTP header, HTTP method or Cookie header. How to fix CORS error?

  3. 3
    Article
    Avatar of communityCommunity Picks·4y

    Top 10 Microservices Design Patterns and Principles

    Microservice architecture is structured on the business domain and it's a collection of small autonomous services. Transaction management is the fundamental advantage of a shared database versus a per-service database. Event Sourcing is based on the idea that any change in an entity's state should be captured by the system. The persistence of a business item is accomplished by storing a series of state-changing events.

  4. 4
    Article
    Avatar of snykSnyk·3y

    How to build a secure API gateway in Node.js

    API gateways can provide a clear path for your front-end applications (e.g., websites and native apps) to all of your back-end functionality. They can act as aggregators for the microservices and as middleware to handle common concerns, such as authentication and authorization. The most popular choice for Node.

  5. 5
    Article
    Avatar of asayerasayer·3y

    7 Microservice Design Patterns to Use

    Microservice architecture is self-contained and wrap up around one business capability. It also refers to an architectural style for app development. The design is rapidly evolving and is one of the most important aspects of microservices. In the following sections, we’ll discuss seven important patterns.

  6. 6
    Article
    Avatar of quastorQuastor Daily·3y

    How Tinder Built Their Own API Gateway

    Tinder is the most popular dating app in the world with over 75 million monthly active users. The app is owned by the Match Group, a conglomerate that also owns Match.com, OkCupid, Hinge and over 40 other dating apps. Tinder’s backend consists of over 500 microservices, which the components are - Routes.

  7. 7
    Article
    Avatar of communityCommunity Picks·3y

    Introduction to Microservices Architecture

    Introduction to Microservices Architecture is an approach to application development in which a large application is built as a suite of modular services. Each module supports a specific business goal and uses a simple interface to communicate with other sets of services.

  8. 8
    Article
    Avatar of awstipAWS Tip·3y

    Serverless Architecture For Next App

    Serverless architecture for Next App Serverless has been there for a fair amount of time but surely has come to a more mature state than it was there about a few years ago.

  9. 9
    Article
    Avatar of logrocketLogRocket·3y

    Microservices with NestJS, Kafka, and TypeScript

    The microservices architecture is an increasingly popular architecture pattern that follows the SOA (Service Oriented Architecture) concept. This guide will demonstrate how to build microservices using NestJS, Kafka, and TypeScript. You will create an authentication microservice to create and save user details.

  10. 10
    Article
    Avatar of bytebytegoByteByteGo·3y

    EP 38: Where do we cache data?

    This week’s system design refresher: ByteByteGo Facebook page What is OSI Model? What tech stack is commonly used for microservices? We’ve launched a Facebook page and want our content to be more accessible. The diagram illustrates where we cache data in a typical architecture.

  11. 11
    Article
    Avatar of bytebytegoByteByteGo·4y

    EP23: How to choose the right database? Also...

    GraphQL is a query language for APIs developed by Meta. It provides a complete description of the data in the API and gives clients the power to ask for Migrating to a new database in the real world could take years at a high scale. Bloom Filters Algorithms You Should Know For System Design #2.

  12. 12
    Article
    Avatar of communityCommunity Picks·3y

    System Design Basics: What is an API Gateway?

    API gateway is a server that acts as a single point of entry for a set of microservices. It receives client requests, forwards them to the appropriate microservice, and then returns the server’s response to the client. This enables microservices to focus on their individual tasks and improves the overall performance of the system.

  13. 13
    Article
    Avatar of awstipAWS Tip·3y

    Automate everything you can.

    Serverless should be as simple as picking resources and writing logic as possible. In this blog, I’ll work through the basics of going from an architectural diagram to a functional project without worrying about a specific technology. The diagram breaks down into a set of resources and functions which are primitives supported by Nitric.

  14. 14
    Article
    Avatar of freecodecampfreeCodeCamp·4y

    How to Learn Serverless AWS by Building 7 Projects

    The Time-To-Live (TTL) tells dynamo that once the time reaches this date, delete the record from Dynamo. For the front end you can write a simple web app with two sections: create new reminder, and list my reminders. This can be in React, Vue, Angular, or even raw HTML, CSS and JavaScript.

  15. 15
    Article
    Avatar of keycdnkeycdn·4y

    API Security: The Complete Guide

    API security is a crucial consideration when developing and designing APIs. As serverless architectures and microservices are getting more popular, most enterprise applications depend on the API. This attack is detected when a malicious attacker changes or tries to change parameters across a series of API calls to request sensitive data that only authorized personnel are allowed to access.

  16. 16
    Article
    Avatar of communityCommunity Picks·3y

    Writing API Design Standards

    API Development Standards are a focused collection of imperatives, conventions and guidance. They are intended to improve consistency, stability, generality, predictability and usability of business resource APIs. They may offer best-practice recommendations and provide a basis for quality assessment.

  17. 17
    Article
    Avatar of bytebytegoByteByteGo·3y

    EP 39: Accounting 101 in Payment Systems

    This week’s system design refresher: Cloud Native Accounting 101 in Payments Evolution of Uber's API Layer Short/Long Polling, SSE, Websocket 17 Equations That Changed the World. What is cloud native? Below is a diagram showing the evolution of architecture and processes since the 1980s.

  18. 18
    Article
    Avatar of quastorQuastor Daily·3y

    A Dive Into Load Balancers

    NetApp is a cloud services company that provides storage infrastructure for data management, protection, analysis and more. The downside of L7 load balancers is that they can be more complex and computationally expensive to run. The performance advantage for L4 load balancer has become pretty negligible in most situations. Most general purpose load balancing balancers operate at layer 7.

  19. 19
    Article
    Avatar of gcgitconnected·3y

    System Design Interview Basics: Difference Between API Gateway and Load Balancer

    API Gateway and Load Balancer are both types of infrastructure that can be used in a computer network to manage incoming requests. API gateway is a server that acts as a single point of entry for a set of microservices. Load balancer is a network device that distributes incoming network traffic across multiple backend servers.

  20. 20
    Article
    Avatar of dzDZone·3y

    A Poor Man’s API

    A poor man's API A Poor Man’s API is an alternative to building an entire REST API. Join the DZone community and get the full member experience. Creating a full-fledged API requires resources, both time and money. The solution works, but it has a lot of room for improvement.

  21. 21
    Article
    Avatar of communityCommunity Picks·3y

    Best Practices For Today’s API Platform Architect

    API platform architects play an enormous role in shaping their organization’s tools, data, and APIs. They don’t always have direct access to the code, though.

  22. 22
    Article
    Avatar of hackernoonHacker Noon·3y

    API Gateway vs Backend for Frontend (BFF): Use Cases, Similarities and Divergencies

    API Gateway is a server that handles many functionalities in a single place for the clients to interact. It can consolidate and aggregate the data across aggregating multiple microservices using a single endpoint for clients to communicate. The process will get cumbersome fast and it could bloat up the API Gateway service by making it a single Monolith service.

  23. 23
    Article
    Avatar of dzDZone·4y

    Design Patterns for Microservices Architectures

    There are more than eight must-have design patterns for smooth development in a typical micro services architecture. An orchestrator (object) coordinates with all the services to do local transactions, get updates, and execute the next event.

  24. 24
    Article
    Avatar of awstipAWS Tip·3y

    From Monolith to Serverless

    AWS Lambda is the core component of the serverless platform, but there are a number of other services that are part of the broader serverless toolset. The key is to leverage as many of these services as you can to take care of the core primitive application layer concerns.

  25. 25
    Article
    Avatar of foojayioFoojay.io·4y

    Backend-for-Frontend: The Demo

    The monolith offers an endpoint for each data source, and a single aggregating endpoint for all of them. In the previous section, we developed a dedicated backend-for-frontend application. In this case, the gateway can be seen as a container where to deploy BFF plugins. I'll be using Apache APISIX to demo how to do it, but the idea can be replicated on other gateways as well.