The most important driving force behind any software product is the group of people who build it—and their relationships with one another. Therefore, it’s important to arrange teams in a way that allows them to have as much leverage and impact as possible. Learn how Braze successfully restructured its product organization to drive better outcomes.
We spent the first five or so years building Braze without much in the way of formal project management. But by early 2018, we started seeing new, serious issues with the way our processes worked. To ensure that we could maintain our product velocity and maximize the efficiency of our engineering organization, we decided to embrace a new approach: Agile Software Development.
Our SDKs, code that our customers include directly into their apps to collectively send billions of events per day to our systems, are a crucial part of the Braze platform.That’s why it’s all the more important for the Braze team to make sure that our SDKs are working in top shape for our customers. In this post, we’ll dive in to how we test our Android SDK and keep it bug-free.
Braze processes billions and billions of events per day on behalf of its customers, resulting in billions of hyper-focused, personalized messages—but failing to send one of those messages has consequences. To make sure those key messages are always correct and always on time, Braze takes a strategic approach to how we leverage job queues.
Braze (formerly Appboy) handles a tremendous amount of scale in our systems, dealing with hundreds of thousands of API calls per second and running thousands of databases and application servers. But it hasn't always run this smoothly. Read on to learn how Braze embraced the cloud to better handle massive growth.