Introduction

Coral enables automation to help engineering organizations improve velocity by moving common engineering infrastructure and process to a central location that application teams can leverage.

The Application Development and Platform Role Abstraction

Coral is based on an abstraction around application development and platform roles; a model that has been highly effective within Microsoft and in organizations we work with. In this model, an engineering organization sorts itself into two roles: Application Development and Platform.

Application Development role engineers build and manage a service. They are the experts on a particular domain within their organization and their core value derives from the business value of that service. Therefore, the goal is that they remain focused on expending engineering effort on a backlog that accrues directly to that business value.

Platform role engineers build internal workflows and tooling to help Application Development Teams build and manage services with the highest velocity and lowest cost possible. They are the experts in everything else that is necessary: operating deployment infrastructure, curating application seeds for new applications, making App Devs productive with great day to day development environments, and making it easy for App Devs to build, deploy, monitor, and operate their applications from concept to production.

In some smaller organizations, engineers may play both of these roles, while in larger organizations, they might decide to create a central Platform Team that focuses on this role.

Regardless of how this model is employed, Coral brings automation and patterns to help make these roles highly effective.

Getting Started

• Coral Platform Setup
• Kubernetes Cluster Registration
• Developing Apps from Application Seeds
• Application Deployment
• Configure Coral with Azure Monitor

Learn More

• Coral Documentation Hub
• Architecture
• CLI