One of the most important things you can do as an engineering organization is to define a process around what service excellence means for each service in production. A lot of the time, engineering teams will create static production readiness checklists to make sure a set of criteria are met and can apply across their entire fleet of services.
The checklist looks something along the lines of this:
- Services have ownership defined
- Services have an on-call rotation
- Services have a runbook
- Service have a dashboard
This typically falls short, and there’s a couple issues with only sticking to this approach.
- These checklists are usually stored and tracked somewhere in a spreadsheet, wiki, basic microservice catalog, or git repository where it’ll quickly go out of date and make it extremely difficult to standardize across different teams in the organization. It’s like herding cats where ultimately nothing gets done and services are left vulnerable.
- Every role within the organization may have a different perspective on what criteria is required in order to meet production readiness standards.
At effx, we want to provide all your teams the flexibility to weigh in and provide their perspectives on what it means to leave each service at its peak operability.
This is why we’re excited to announce Service Standards 360°.
Build and track not one, but multiple standard perspectives, angles, and views
As we highlighted above, every role within your organization may look at the same exact service or set of services through a different lens when it comes to setting standards. These lenses could ultimately be driven by varying needs of security, governance, compliance and/or operational readiness.
With the effx platform, you have the flexibility to set specific criteria for multiple perspectives outside of what you may define as a general or default standard. For example, services assigned to the ‘default’ standard may overlap with services assigned to a “Tier 0” readiness” standard set by Site Reliability Engineering (who may require a completely different set of criteria of their own).
Ultimately, by gathering multiple perspectives on your services in a 360° view helps your teams increase the bar for service quality.
Maintain and measure service quality across your entire fleet
As an engineering leader, keeping track of health across a fleet of services can be extremely difficult to manage -- especially when there’s so much change happening across your infrastructure. Now we give you the ability to view service quality directly from the service page, or at higher level aggregate view by standards.
These views on service quality will help engineering teams find gaps in their infrastructure where they could have some missing criteria that may have been required or recommended by any set standard. Engineering teams can then take action on the work they need to do to make sure their services maintain production readiness.
Get focused and target a specific set of services to maintain quality
At the minimum, in order to take any service into production you want to make sure you have at least a general or default set of criteria required. This could be more or less criteria like ownership, on-call, runbooks, communication channels, etc.
Although, there may be the case that certain parts of your infrastructure are more vulnerable or critical than others where the broader standard alone won’t cut it. The effx platform allows you to create more targeted standards where you can define criteria for the services that are the highest priority for the business. In the example below, we’ve set a more targeted standard that applies to any critical services that expose grpc. This same focus could also be applied to your serverless functions running in AWS Lambda or container workloads running in Kubernetes by adhering to their own respective set of criteria.
Service standards 360° is available for all users of the effx platform today! You can also see a short demo video of Service Standards 360° here.