11436 SSO

Belly Up to the Microservices Bar

Why Belly, a leading rewards plan provider, needs API management
AlanH
Feb 17, 2016

If you’ve ever walked into a store and seen a rewards program displayed on a tablet at the checkout counter, there’s a pretty good chance that it is powered by Belly. The loyalty and rewards plan provider, which was recently featured in TechCrunch for its mobile marketing suite, employs API management to build mobile APIs from legacy services and newer microservices.

We recently spoke with Belly’s director of platform Darby Frey to learn about the technology that lets Belly “Move fast and not break things.”

In the first part of this series of short videos, Darby explains why Belly needed an API management platform.

Belly faced several challenges in building mobile APIs from legacy services:

  • Its architecture consists of one legacy monolith and many new smaller microservices.
  • Moving to microservices introduced lots of operational complexity.
  • Mobile apps need to consume microservices efficiently.

Belly’s architecture had a single Rails app in front of microservices, and it didn’t scale or perform particularly well. All of this set the company on the path to find a robust, scalable API management platform.

In the next post, Darby will discuss why Belly needed an API management platform for its microservices.

Microservices Done Right

Next Steps

 
 

Resources Gallery

News