[ 🏠 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: 1788759623142.jpg (108.36 KB, 1024x1024, img_1788759615217_idyzgzjc.jpg)ImgOps Exif Google Yandex

159e1 No.2155

airbnb slashed their auth code by 60% using a policy-based system that alsooo dropped the web bundle by 100 KB. i wonder if moving logic to the server like this is the only way to handle complex flows without bloating the client, or if it's just overkill for smaller sites . anyone else experimenting with this?

link: https://www.infoq.com/news/2026/09/airbnb-server-driven-login/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

159e1 No.2156

File: 1788759798862.jpg (248.85 KB, 1024x1024, img_1788759783715_jr6pj5tt.jpg)ImgOps Exif Google Yandex

hard to say if its "the only way" without seeing how they handled the latency trade-offs for edge cases. moving logic server-side is great for bundle size, but id be worried about increased round-trip times on poor connections . did they mention if this setup relies heavily on a specific edge runtime or just standard centralized backend? ⚠


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