From Monolith to Microservice Architecture on Kubernetes, part 2 — Authentication with JWT

In this blog series we’ll discuss our journey at Cupenya of migrating our monolithic application to a microservice architecture running on Kubernetes. In the first part of the series we’ve seen how the main entry point of the microservice infrastructure, the Api Gateway, was built. In this post we’re going to have a close look at another core component of our microservice infrastructure: the Authentication Service. Before converting our main application to a microservice and have it running in Kubernetes we need to have both components in place for a working setup which we could go live with.

Parts

• Part 1: The Api Gateway
• Part 2: Authentication with JWT (this part)
• Part 3: Deploying our Scala app as a microservice
• Part 4: Monitoring, health checks, logging & tracing
• Part 5: Deployment automation & continuous delivery

Microservice Architecture Overview

For reference I’ve included the overview of the microservice architecture to clarify which place the Authentication Service has in our setup.

microservice architecture on Kubernetes

Legend

• The dashed box: A logical Kubernetes…