The Developer Control Plane
In a cloud native world, software developers are no longer only responsible for writing code. Today’s developers must write and package code, deploy these services into production, and make sure that the corresponding applications continue to run correctly when released into production. To borrow a phrase from the Netflix engineering team, full stack developers are becoming full lifecycle developers.
In addition to coding, cloud native developers are now also responsible for shipping and running applications.
For years, operations teams have addressed operational complexity in software applications by adopting control planes that provide appropriate abstractions and aggregation of control. These control planes provide automated cluster management (e.g., cloud-managed Kubernetes control planes), L7 traffic traffic management (e.g., service mesh), and more. Now is the time for developers to adopt a control plane.
What is a Developer Control Plane?
A developer control plane enables developers to control and configure the entire cloud development loop in order to ship software faster.
3 Pillars of the Developer Control Plane
Cloud native developers are now responsible for 3 components of the cloud native development stack - coding new services, shipping them to production, and running them over time.
Developers need to easily build and ship code:
- Configure and maintain development and testing environments
- Discover APIs available for coding
Developers need to release updates without breaking the application:
- Canary release new versions of a service safely to end users
- Understand which versions of a service are deployed and released
Developers need to keep their services running 24x7:
- Mitigate issues with updates
- Monitor updates for anomalous behavior
Coding services on Kubernetes can be a slog. The container-build-push-deploy loop saps productivity and impedes flow. Setting up a development environment that runs multiple microservices is a bunch of work, and keeping all the services up to date is even more work.
To be productive, developers must maintain configuration for:
- Their development environment
- Source control
- Continuous integration tooling
Code Faster with Telepresence
Telepresence enables Kubernetes application developers to create productive development environments with access to their favorite local tools like debuggers.
Learn how to code faster on Kubernetes
Shipping code changes to production requires a complicated dance between many different pieces of software. Shipping software incrementally is a safer way to release new features to your users. For cloud native applications, many developers are now responsible for progressive delivery.
To ship incrementally, developers must maintain configuration for:
- Continuous deployment
- Manifest management
- Container management
Ship Incrementally with Ambassador Edge Stack + Argo
The Ambassador Edge Stack integrates with Argo to make canary releases on Kubernetes easy.
Learn how to ship updates safely
No matter how careful you are with testing and canary rollouts, things still go awry in production. Advanced L7 traffic management capabilities such as load balancing, rate limiting, and circuit breaking in order are critical to ensure the availability and scalability of your microservices. Being able to respond quickly to production incidents is a critical part of your workflow.
To keep their services running, developers must maintain configuration for:
- API management
- Kubernetes runtime
Route Production Traffic with Ambassador Edge Stack
Built on Envoy Proxy and Emissary-Ingress, the Ambassador Edge Stack gives you sophisticated traffic management capabilities and authentication mechanisms to get your services running in production securely.
Track Critical Service Data with Service Catalog
Respond to incidents faster with a real-time portal for Kubernetes app developers for easy access to critical data about services.
Learn how to keep your services running 24/7
Collaborate at Any Scale with a Developer Control Plane
Share critical information about your service with the Service Catalog. Share previews of your code with Telepresence.
Proven Open Source Foundation
Ambassador is built on battle-tested open source projects: Emissary-Ingress, Argo, Envoy Proxy, and Telepresence.
Enhance your Existing Stack
Use with your preferred Kubernetes distribution or cloud provider. Integrate with your preferred observability, continuous integration, and service mesh.
A single view of your developer control plane.
- Intercept services with Telepresence for fast, local development
- Safely ship new versions of your software with canary releases powered by Argo
- Respond to incidents faster when you store critical service data in the Service Catalog