Building an Application Platform: Lessons from
summary
Argument: don’t buy a giant message bus / NoSQL / rules‑engine up front; build the platform from laptop experiments and scripts, push Tomcat behind nginx, copy bits via SSH/SCP and S3, spin EC2 nodes, wrap those scripts with a simple REST API and a curl/CLI, add basic MySQL logging and pingdom alerts. Uses AMQP then 0MQ, Erlang, Python, genapp, New Relic, Papertrail. The next obvious step ethic yields a working incremental platform from one laptop to multiple EC2s and small failures that are easy to fix by minimize size maximize autonomy.
AI-written summary · about
chapters (19)
- 0:00Start
- 2:28Cut Out The Middleman
- 4:26Application Deployment
- 5:56Big Ideas Need Big Plans
- 6:21Message Bus
- 6:37NoSQL Distributed Database
- 7:00Rules Engine
- 7:33Traditional Components
- 11:03Don't Think, Act!
- 15:29What You'll Notice
- 23:45Appserver, Port 80
- 24:28Appserver Cluster
- 25:18One Server
- 25:37More Servers
- 26:28Server Configuration
- 26:47Get Fancy!
- 29:49User Interface
- 33:37Next Step?
- 36:17Are There Any Questions?
related talks
26mThe common fallacies on platform building
47mPlatform Team Structures and Concerns
42mPlatform Engineering in practice — Why and How to start
33mPlatform engineering: Build your own PaaS
39mPlatform Engineering as a (Community) Service
42mPlanning To Fail
22m20+ years of building systems that outlast the chaos
41mPlatform Engineering for Developers, Architects & the Rest of Us