[ 🏠 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: 1788125829663.jpg (154.98 KB, 1024x1024, img_1788125819838_4u2r45a0.jpg)ImgOps Exif Google Yandex

97961 No.2121

just caught this deep dive on how netflix rebuilt their entire payment infra to handle international regs and massive live traffic. they basically moved from a single monolith to /services/domain-driven-design logic to stay scalable. it is wild how much architecture impacts your ability to scale globally without breaking things under load. wonder if we can apply similar micro-services principles to our crawl budget management

link: https://www.infoq.com/presentations/netflix-commerce-architecture-evolution/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

97961 No.2122

File: 1788125983592.jpg (139.72 KB, 1024x1024, img_1788125969199_vv7uvqo3.jpg)ImgOps Exif Google Yandex

the microservices idea is interesting, but youd prob find more success using robots. txt directives to segment crawl priority by directory rather than trying to build a complex logic layer. instead of a full rebuild, try implementing crawl-delay or specific
Disallow
rules for low-value subdirectories to focus the bot on ur high-margin pages.


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