No features have been listed yet.
No Google Site Reliability Engineering videos yet. You could help us improve this page by suggesting one.
Amazon API Gateway might be a bit more popular than Google Site Reliability Engineering. We know about 108 links to it since March 2021 and only 86 links to Google Site Reliability Engineering. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
An API Gateway: Routes the Google OAuth redirect to the token exchange Lambda function. - Source: dev.to / 15 days ago
AWS API Gateway is Amazon’s managed gateway service, designed to work seamlessly within the AWS ecosystem. It supports both REST and WebSocket APIs, with HTTP APIs being the lightweight, lower-cost option for simple proxying and routing use cases. - Source: dev.to / about 1 month ago
This opens up a world of customization options for controlling app access. For example, we can embed custom data in the ID token for the front-end client to use, enabling guards to restrict content. Alternatively, we can add custom scopes to the access token and implement fine-grained access control in an API Gateway API. All it takes is some Lambda function code, and Cognito triggers it at the right time. - Source: dev.to / about 2 months ago
When the built-in Amazon API Gateway authorization methods don’t fully meet our needs, we can set up Lambda authorizers to manage the access control process. Even when using Cognito user pools and Cognito access tokens, there may still be a need for custom authorization logic. - Source: dev.to / 2 months ago
The API Gateway includes an endpoint structured like this:. - Source: dev.to / 2 months ago
In 2025, observability is no longer just for SREs or DevOps—it’s a cross-functional necessity. Whether you’re debugging a production outage, tracking performance regressions, or optimizing user experience, your observability tools should provide clarity, not clutter. - Source: dev.to / about 1 month ago
Same difference... Read the book https://sre.google/. - Source: Hacker News / 10 months ago
In my view it is having a dedicated team focusing their full mental bandwidth on pro-actively understanding and managing robustness of the system. In Pure DevOps, it seems to me developers often don't have the full picture of the system, and not enough bandwidth to foresee complex interactions from their changes. These are from my experiences spending one year as a developer in somewhat large a greenfield... - Source: Hacker News / over 1 year ago
Site Reliability Engineering, introduced by Google, extends the principles of software engineering to operations. Unlike DevOps, SRE places a stronger emphasis on reliability, availability, and scalability. SRE teams are tasked with maintaining the health and performance of systems by applying engineering practices to operations. The ultimate objective is to achieve a balance between service reliability and... Source: almost 2 years ago
Define SLOs for availability and latency. Google's SRE book is good reading for this. Source: about 2 years ago
AWS Lambda - Automatic, event-driven compute service
Open Telemetry - An observability framework for cloud-native software.
Postman - The Collaboration Platform for API Development
Ganeti - Ganeti is a cluster management tool built on top of existing virtualization technologies.
Apigee - Intelligent and complete API platform
Apache Helix - A cluster management framework for partitioned and replicated distributed resources