Not all web geeks may know, but one way to understand a prominent website is to look for a URL like engineering.blogs.domain.tld or variations of that like /blogs/engineering. The architects and tech leads share their thoughts on why they chose certain technologies or migrated to superior alternatives, and addressed the showstoppers.
Hundreds of options are available now to mix and match. Single Sign On, SSO, search, caching, real-time interaction, security, backup, resiliency, Role based access control, UI, UX, memory footprint, responsiveness, Internationalization (i18n), Localization, Hacking prevention, Transport Layer Security TLS, Encryption at Rest and transport, RDBMS, Columnar databases, In-memory databases, ORMs, global decentralization, GDPR, UTF, Mobile and desktop formats, commenting systems, emails, newsletters, notifications, 2FA, ACID principles, Payments integration, Transactional integrity, logging, streaming, Downstream change streaming,(Like Kafka), analytics and so many.
I know I'm bringing too many things to the table, but these are what I observe as I think of building a web application for my ideal needs. I was a solution architect for business applications and lived with commercial solutions from Oracle, SAP, IBM, SFDC, etc.
Furthermore, I have studied multiple high-traffic sites and multiple platforms. Like matrix.org, discourse, forem.dev, ghost and many more.
forem.dev is the place where I can ask this kind of question. What are forem's thoughts on all these? How to know when to act even before a crisis appears or maintenance issues cause a pain? I