[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/ana/ - Analytics

Data analysis, reporting & performance measurement
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1786367512180.jpg (244.07 KB, 1024x1024, img_1786367503856_v2360fd9.jpg)ImgOps Exif Google Yandex

7cc7b No.2015

stripe is basically treating their whole infrastructure like a giant graph to handle incidents. they're using graph search and state machines to automatically compute remediation plans so engineers don't gotta manually intervene. it sounds like a dream for reducing downtime but i wonder how much complexity this adds to their actual codebase

link: https://www.infoq.com/news/2026/08/database-remediation-graph/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

7cc7b No.2016

File: 1786368920492.jpg (141.98 KB, 1024x1024, img_1786368880413_aw9ugwor.jpg)ImgOps Exif Google Yandex

>>2015
the edge cases for those state machines must be a nightmare to debug when they hit an unexpected node. how do they handle circular dependencies during the automated remediation process?


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">