Member-only story
Data Mesh — REST API Routing
When developing multiple data products and wanting to expose them to the users in a logical and ordered manner, it being either internal users or external users you need to ensure you have a strategy. In this post we “dumb down” data products to REST APIs only which is not a true representation for data products in reality.
To solve the above question and create a unified way of calling the different data products multiple solutions are available. The below two options are examples.
Rev.Proxy based routing
Leverage technologies like reversed proxies and API gateways to route traffic centrally to the different REST APIs of the data products.
Understanding API Gateways and Reverse Proxies
API Gateways: An API gateway is an architectural pattern that sits between the client and backend services, serving as a single entry point for all client requests. It acts as a centralized management layer for APIs, offering functionalities such as authentication, authorization, rate limiting, logging, and routing. API gateways streamline the process of managing multiple APIs and help enforce consistent policies across them.
Reverse Proxies: A reverse proxy is a server that sits between clients and backend servers, intercepting requests from clients and forwarding them to the appropriate backend server. Unlike a forward proxy, which sits between clients and the internet, a reverse proxy is typically deployed in front of web servers or application servers to handle incoming requests and distribute them among multiple backend servers. Reverse proxies are commonly used for load balancing, caching, SSL termination, and security enforcement.
Routing Parts of URLs to Different Backend Systems
Routing parts of URLs to different backend systems is a common requirement in microservices architectures, where different services handle different functionalities or domains. This…
