1 min read
What 60 million users teach you about JWT-based routing
by Toni Pinel
When a single user can be either a cash buyer or a loyalty-program member, and that distinction determines pricing, backend namespace, and what gets rendered on screen, you have two options: replicate the logic across every service, or push it into the API layer.
UltraGroup chose the second. Their KrakenD instances read JWT claims for business model, marketplace and payment mode, then route requests accordingly. No code duplication per variant. Time-to-market for a new product line went from three to five months down to weeks; onboarding a new tenant became a configuration change. As Andrés Ayala, their architecture lead, puts it: “We don’t build API gateways. We build the applications that create value for the business.”
Read the UltraGroup case study for the full architecture and where it’s headed next.