Social media platforms are hosted services where accounts publish content, connect to other accounts, and receive an assembled stream of what those connections and the platform's ranking system surface. They matter to a technical audience mainly as distribution channels with their own constraints and their own APIs.
01The common architecture
Despite very different surfaces, most platforms share the same building blocks.
An identity layer holds accounts, authentication and profile data, and increasingly distinguishes personal accounts from business or creator accounts with separate capabilities. A social graph records the relationships between accounts, which may be reciprocal (mutual connections) or directional (followers). A content store holds posts and the media attached to them, usually with the media served from a separate delivery network. A ranking system decides what any given account sees, which is generally not simple reverse chronology. A moderation system applies policy to content, combining automated classification with human review and an appeals path.
For anyone publishing, the ranking system is the operative constraint: reaching an audience is a function of what the platform chooses to distribute, not merely of who has subscribed.
02Publishing and integration constraints
Every platform imposes technical limits that shape production work upstream. Aspect ratios and resolutions differ per surface. Maximum durations and file sizes differ per format. Media is re-encoded on upload, so the file a viewer receives is not the file that was delivered, and quality decisions are best made with that second encode in mind. Captions, alt text and metadata requirements vary, and some are load-bearing for accessibility rather than optional.
Programmatic access is available on most platforms, but with real caveats. APIs are versioned and deprecated on the platform's schedule. Access is usually gated behind an application review that asks what the integration does and what data it retains. Rate limits apply, and terms of service typically restrict bulk collection and re-publication of user data. Any integration built on these should be treated as a dependency that will require maintenance, not a one-time build.
03Operational and governance considerations
An account on a platform is not owned property. It exists under terms that can change, and access can be suspended, so the durable version of anything published there should also exist somewhere under direct control. Archiving posted content and exporting the audience relationships a platform permits exporting are both worth doing before they are needed.
Account security deserves the same treatment as production infrastructure, because a compromised business account is a public incident. Multi-factor authentication, unique credentials, named individual logins rather than a shared password, and an explicit list of who currently holds access are the basics. Access removal should be part of offboarding rather than an afterthought.
Data protection obligations follow the data, not the platform. Content that includes identifiable people, customer information, or material licensed for limited use carries the same obligations when posted as it does anywhere else.