Making It Sustainable (Part 5)
The article discusses the importance of creating sustainable systems in global applications. It emphasizes that trust in systems, rather than individuals, is crucial for effective incident management. The author argues that predictable system behavior is essential for maintaining performance and reducing ambiguity during incidents.
- ▪The article is part of a five-part series on global serverless architecture.
- ▪It highlights the difference in team responses during incidents and the impact of organizational behavior.
- ▪The author advocates for systems that guarantee consistent responses to incidents, regardless of team changes.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/aws-builders/making-it-sustainable-part-5-4p8g |
| Publication time | Wed, 03 Jun 2026 04:00:00 +0000 |
| Retrieval time | 2026-06-03T04:11:55.408Z |
| Last seen | 2026-06-03T04:11:55.408Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 9gYHsWXxzO_v |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 831622) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Daniele Frasca for AWS Community Builders Posted on Jun 3 Making It Sustainable (Part 5) #aws #serverless #governance Global Serverless at Scale — Trust Is the Architecture (5 Part Series) 1 Trust Is the Architecture (Part 1) 2 Three Responsibilities of a Global Application (Part 2) 3 Metrics, Logs, Traces, and Audit (Part 3) 4 What Happens During an Incident (Part 4) 5 Making It Sustainable (Part 5) In the previous articles, we explored what happens when things go wrong in a global…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
