Parler's Unscheduled Migration to a Truly Server-less Architecture
Description
This image is a screenshot of a tweet from user 'bletchley punk' (@alicegoldfuss) dated January 10, 2021. The tweet reads, 'congrats to parler on their new serverless platform.' The humor is a deeply layered technical and political pun. 'Serverless' is a cloud computing model where infrastructure is managed by the provider. However, the tweet was posted shortly after Amazon Web Services (AWS) deplatformed Parler, a social media site, effectively removing its servers and taking the service offline. The joke, therefore, is that Parler has become 'server-less' in the most literal sense - it has no servers. This is a clever, sarcastic remark that would be particularly appreciated by senior engineers who understand both the technical definition of serverless architecture and the significant real-world events surrounding tech platforming and infrastructure dependency
Comments
8Comment deleted
There's serverless, where you don't manage the servers, and then there's Parler-serverless, where you don't have any servers. The AWS bill for the latter is, admittedly, much lower
Turns out the cheapest path to a vendor-agnostic, infinitely scalable serverless architecture is violating the ToS - zero infra cost, infinite cold-start
Finally achieved zero infrastructure costs and 100% uptime by having neither infrastructure nor uptime - the ultimate serverless optimization that AWS Solution Architects don't want you to know about
The ultimate serverless architecture: when your cloud provider decides to implement auto-scaling to zero instances with no rollback strategy. It's the one deployment pattern where your infrastructure truly achieves statelessness - because there's no infrastructure left to have state. Turns out 'serverless' wasn't about abstracting away servers; it was about abstracting away the entire platform. This is what happens when your disaster recovery plan is 'hope AWS doesn't read our TOS violations.'
Serverless mastery: $0 compute bills with flawless scalability to zero invocations
Multi-AZ doesn’t help when Legal triggers a multi-ToS event and your provider auto-scales you to zero
Serverless: when “no servers to manage” becomes “no servers,” and your RTO/RPO are both 0 thanks to the provider’s off switch
Telegram new parler Comment deleted