A cloud service company for oil and gas
Formerly:
API Gateways replace tight coupling with loose coupling
An API Gateway is a Reverse Proxy
We will not cover the commercial features
main
http
server
upstream
location
mail
nginx.conf
worker_processes 1;
events {
worker_connections 1024;
}
http {
include mime.types;
default_type application/octet-stream;
sendfile on;
keepalive_timeout 65;
server {
listen 8080;
server_name localhost;
location / {
root html;
index index.html index.htm;
}
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root html;
}
}
}
server {
listen 8080;
server_name localhost;
location /server-a/ {
proxy_pass http://127.0.0.1:3002;
}
location /server-b/ {
proxy_pass http://127.0.0.1:3004;
}
}
7:15 - 8:15pm - Microservice API Gateways with NGINX - Geoffrey Filippi
(NGINX is pronounced "engine x".)
Microservices are a popular architectural solution. Clients of microservices may experience some difficulty keeping track of the various instances and endpoints they have to call. An API gateway can help manage large numbers of microservices and hide the infrastructure complexity from your clients. We will review a microservice architecture before and after the addition of an API gateway.
An API gateway is a reverse proxy. A reverse proxy handles incoming requests from clients and calls a service to get the data to satisfy that request. The reverse proxy returns that data to the client. Many developers write these proxies by hand in custom code, not realizing the are better solutions available. We will mention a number of popular solutions, some open source and some cloud-based services. For this talk, we will focus on NGINX, a popular open source reverse proxy and API Gateway. (NGINX also sells an enterprise offering, NGINX Plus, but this talk will only cover the features available in the open-source version.)
We will show how to set up NGINX as an API Gateway. We will dive into the configuration and operation of NGINX.