Background 🔗In most modern distributed architectures, two architectures designs are the most common: SOA (Service–Oriented Architecture) and Microservices (read more about their differences on this post from IBM). It’s normally a hard decision to whether keep adding functionality to a service or to break it into smaller microservices. There’s no clear line on where this division should happen. However, certain service characteristics can be major indicators that you should (or shouldn’t) break your service.

JWT Overview 🔗JWTs (short for JSON Web Tokens) are simply a way of safely transmitting information between two parties in a JSON object, which can be signed, encrypted, and verified. It’s commonly used for Bearer tokens in different authentication services (e.g. if you are the “bearer” of a valid token, it grants you access to something). JWT tokens are broken down into three parts: Header - hashing algorithm and token type Payload - data (contains the Claims) Signature - header + payload + key hashed together The result of each part is separated by a .