The goal of the Service Layer is the ensured state of services needed to run the applications in the App Layer.
The Service Layer enables the DevOps culture within the company. If developers are writing applications and operations are ensuring the state of the cloud, the Service layer is where those two teams meet. If the developers are wrapping their application in a
rkt container, operations are responsible for wiring up the Kubernetes service into the cloud. Wiring up a service consists of ensuring logging, monitoring, observability, redundancy, and of course automation. Once a service is ensured to be available, the developers are then freed to experiment by launching into a service that they know is wired into the cloud. If a developer needs to launch a brand new service, a pull request that is approved by development and operations required. This gives the operations team the opportunity to verify or build into the wiring for that service. A discussion can then happen between development and operations on how to solve that problem with what available service.
Service Layer enabling DevOps:
- compassion for developers by providing already wired in services to then deploy applications into
- compassion for operations by allowing the proper wiring to be completed before releasing the service to the business
- compassion for the business by knowing that services being used have been agreed upon and correctly configured by both operations and development to be redundant and cost optimized
This layers infrastructure state is ensured using Terraform. This project has the strong opinion that Terraform is the best tool to ensure the static immutable state of the infrastructure at the Service Layer. A simple cron run by Ansible Tower, will every 20 minutes execute a
terraform plan to verify the state of the infrastructure matches the Terraform state file. With no reported changes the infrastructure is verified in the correct known state. Any changes reported by Terraform would be an escalated Defcon level, requiring a human to intervene and manually update the state using
terraform apply, ensuring the state is brought up the state expected in code. See the Foundation Layer README for coding standards and naming conventions along with requirements.
Service Layer contents:
- Cloud native services
- Baked Virtual Machines
- Container optimzed VMs with baked cloud-init
- Logging transport layer
- API Gateways
Cloud Native Services
Cloud native services are any service hosted by, managed, and guaranteed by the cloud provider. S3 storage and Google Storage Buckets would be excellent examples of cloud native service layer services, RDS and CloudSQL hosted databases being another. The service layer ensure the cloud native service is configured and ready to be deployed into.
Monitoring is defined as a system that reports when a service, server, or system has failed. Monitoring is reactive and is always indicating something that has already occurred. A correctly configured monitoring platform should only fire alerts to humans when a human needs to make a decision on how to react to the outage.
Observability is defined as using events and tracing to measure the current health of the system. Observability prevents outages by identifying unhealthy infrastructure, enabling the infrastructure to fix itself.
Logging Transport Layer
The logging transport layer is the plumbing of the infrastructure and has the sole responsibility of moving all the logs to the correct ingestion point, be it archival storage or a logging analytics service.
The API Gateway or Cloud Endpoints are the front end of the application which serve the API to the world.
Binary Baked Compute Instances
“Baked” refers to the process of using an automated build system to snapshot the OS after the application binary has been installed and configured on the compute instance. Once the instance is fully configured and ready to run in an environment, it is snapshotted, aka baked, and stored as an immutable object that can be deployed and booted, with a known and expected instance state that cannot, and will not, be changed once deployed to the environment. All baked instances are versioned using SemVer. Any changes necessary to the baked instance would require a bump in version number of the instance object.
Container baked instances
A baked container instance is for running a container that is not yet Kubernetes optimized and ready for orchestration. A container optimized OS like CoreOS, RancherOS, or Google Container Optimized OS is preferred over a full OS distro as they are small, secure and do one thing well, run a container. Since these OS’s are typically read-only file systems, they are baked by default. The only change that occurs is configuring which container to pull and run on the OS boot via
cloud-initconfiguration scripts run on boot.