The provided document outlines the responsibilities, incident handling procedures, and Service Level Objectives (SLOs) for Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). Here's a summary of each section:
Responsibilities by Model
IaaS:
- Responsibilities: Full control over the infrastructure. You define service levels, manage availability, and handle all aspects of monitoring.
- Metrics & Monitoring: Custom metrics from your application and infrastructure.
- Error Budgets: Fully owned and managed.
PaaS:
- Responsibilities: Platform provides some built-in services, but you still need to manage application-specific issues. You must understand the platform's limitations.
- Metrics & Monitoring: A mix of platform-provided metrics and custom application metrics.
- Error Budgets: Limited by the platform’s Service Level Agreement (SLA), meaning any downtime or performance issues from the platform affect your error budget.
SaaS:
- Responsibilities: Mainly observe and react to service outages. You rely heavily on the vendor's uptime guarantees.
- Metrics & Monitoring: Typically API response times, login success rates, etc., provided by the vendor.
Read the full article at DEV Community
Want to create content about this topic? Use Nemati AI tools to generate articles, social posts, and more.

![[AINews] The Unreasonable Effectiveness of Closing the Loop](/_next/image?url=https%3A%2F%2Fmedia.nemati.ai%2Fmedia%2Fblog%2Fimages%2Farticles%2F600e22851bc7453b.webp&w=3840&q=75)



