API Gateway

• Managing the routing of the request to different microservices having different port is hard to manage on the servers
• Traffic Management. - API Gateways are used to manage request distribution to the multiple microservices.
• Protocol Translation - HTTP to HTTPS. Managing the http connection internally.
• API security and Prevention from DDOS
• Caching and Load Balancing - Balancing the load and managing the multiple instances (Pods) of the microservices. caching the responses.
• NOTE: API gateways can also be scaled for handling more requests.

Read more:

https://medium.com/@serversidedigest/api-gateways-whats-and-hows-with-implementation-563d9f371edb

Dockerizing the User and auth Services with Integration of kong :

(Performed the test in local dev environment).

1. Build the JARs

• Compile your AuthService and UserService into executable JAR files (e.g., with Maven or Gradle).
• Keep these JARs accessible for Dockerfile inclusion.

2. Dockerize Services

• Write Dockerfiles for both services:

  dockerfile
  CopyEdit
  FROM openjdk:17-jdk-alpine
  COPY authservice.jar /app/app.jar
  ENTRYPOINT ["java","-jar","/app/app.jar"]
  

  (And similarly for userservice.)

3. Create Docker Compose Setup

• Combine all services in docker-compose.yml:
  • Zookeeper, Kafka
  • MySQL (with mounted volume)
  • AuthService, UserService
  • Kong (API Gateway) and optional Konga GUI or Kong Manager
• Use depends_on for startup order, though note it doesn't wait for full readiness—consider healthchecks for production-like setups.