As Keplars continues to evolve from a simple MVP into a production-grade email infrastructure platform, we've been making steady improvements to our internal architecture.
One of the most important recent changes was introducing an API Gateway into our stack.
After evaluating several options, we integrated Apache APISIX, the cloud-native API gateway maintained by the Apache Software Foundation.
Why an API Gateway?
As we move toward a more modular, semi-microservice architecture, we needed a clean and reliable routing layer that could sit between external requests and our internal services. Without this, responsibilities like routing, authentication, rate limiting, and observability tend to leak into individual services, making the system harder to reason about and scale.
APISIX gives us a clear separation of concerns. It allows Keplars to handle:
- Centralized request routing
- Consistent security policies
- Better traffic control and rate limiting
- Cleaner service-to-service boundaries
This change significantly simplifies our internal services and makes future iterations safer and more predictable.
Why Apache APISIX?
APISIX stood out for a few reasons:
- Strong performance characteristics at scale
- A flexible, plugin-based architecture
- First-class support for modern cloud-native patterns
- Transparent, well-maintained open-source development
We rely heavily on open-source software, and having infrastructure components we can trust and understand deeply is critical for a platform that handles product-critical communication.
Huge respect to the Apache Software Foundation and the contributors behind APISIX for maintaining such a high-quality project.
What this means for Keplars users:
While this change happens entirely behind the scenes, it directly supports our core goals:
- More predictable behavior in production
- Better reliability as traffic grows
- A foundation that allows us to add features without increasing complexity
It's another step toward making Keplars boring in the best way: reliable, predictable, and focused on solving real problems without introducing unnecessary friction.
Conclusion:
Introducing Apache APISIX as our API Gateway marks a significant milestone in Keplars' architectural evolution. While the change itself may seem invisible to end users, it represents our commitment to building infrastructure that scales thoughtfully and maintains reliability as we grow.
This is the kind of infrastructure work that doesn't make headlines, but it's what allows us to ship features faster, maintain system stability, and keep our promises to developers who depend on Keplars for critical communication.
As we continue building, expect more of these "boring" improvements: solid, well-tested changes that make the platform more dependable, not more complex.
If you're using Keplars or considering it for your email infrastructure, know that every architectural decision we make is guided by one principle: make it work reliably, then get out of the way.