Growing the Ambassador API Gateway community
We started working on the Ambassador API Gateway several years ago. When we started working on Ambassador, we saw a unique confluence of trends:
- Cloud-native applications were becoming increasingly distributed, thanks to the microservices trend
- The world was becoming a L7 world, and resilience and observability needed to be built into L7
- Envoy, with its performance, small footprint, and broad feature set, was a core foundational technology with which to manage L7
- Developers could benefit from being able to easily publish and canary different versions of their services to their end users
Our goal when building Ambassador API Gateway was to make it the easiest way to deploy Envoy as an edge proxy. And, given the growing hype around both Kubernetes and Envoy, building Ambassador on Kubernetes just made sense.
Community
In the past months, we’ve seen rapid community growth of the Ambassador Labs community. We have users who are migrating to Ambassador from legacy API Gateways for improved performance and simplified management. We have others who love how Ambassador works with Istio. Not only do we have a growing user base, we’re starting to see broader contributions to Ambassador, including articles about Ambassador as well as new features.
To better support the community, we’re launching this blog. Here, we’ll share product updates and more in-depth articles about different use cases on Ambassador. If there is a particular use case you’re interested in hearing more about, or if you’d like to contribute to the Ambassador blog, you can fill out the Google form below:
As always, if you have questions about using Ambassador, jump in our Gitter Chat. Thanks to all of the community members that have contributed so far, we look forward to another exciting year ahead!
