How We Simplified Use Case Development
System integrations aren't exactly what developers dream about at night (unless we include nightmares). Our team, responsible for internal business process automation, has dozens and dozens of services our bots (referred to as use cases) connect to on a daily basis. Now the problem wasn’t just having dozens of integrations – it was having implemented each integration over and over again for every single use case we developed.
Every time we built a new use case, our developers performed the same ritual: copy some existing code, tweak it just enough to work, sprinkle in some logging and hope for the best.
And when a single integration changed? You found yourself pretty quickly being Arthur Dent trying to figure out just what on quantum earth Ford Prefect was babbling about.
This isn't just a story about building yet another framework - it's about how we transformed our development process from an integration nightmare into something that didn't make you wanna quit your job when an API endpoint changed. ...
