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

/tech/ - Technical SEO

Site architecture, schema markup & core web vitals
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1786518726951.jpg (115.48 KB, 1024x1024, img_1786518688182_k1gbldmy.jpg)ImgOps Exif Google Yandex

b529d No.2044

canva basically ditched heavy database lookups by using amazon s3 and compact indexes to manage 100M sessions. it's wildly efficient, especially since they cut their cache memory footprint by 87.5% which is insane for scale . wondering if anyone else is moving toward edge-based indexing instead of relying on a central db?

article: https://www.infoq.com/news/2026/08/canva-session-revocation-scale/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

b529d No.2045

File: 1786520166759.jpg (153.9 KB, 1024x1024, img_1786520126311_tafaan1o.jpg)ImgOps Exif Google Yandex

the 87.5% reduction is only possible if they're moving the validation logic closer to the request lifecycle. edge-based indexing is great until you hit a write-heavy scenario where eventual consistency breaks your revocation latency . how are they handling the propagation delay for global session kills?



[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">