Client/Server Architecture: Past, Present, & Future
summary
Claims that the web moves from monoliths toward separated clients and APIs, with a production example of migrating a large Weedmaps Rails app toward microservices. Specific tools and choices include Rails 5 API, Grape, ES6 via Babel, CoffeeScript, React + Redux, Ember, Angular, React Native (used to build PocketConf successfully), and deployment options S3, gh-pages, Surge.sh. Architecture notes cover read replicas, sharding, Elasticsearch/Neo4J for denormalized composition, and the caution that microservices add latency, DevOps burden, and harder refactors.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:45Fundraiser
- 2:07Monolith
- 4:36System Scalability
- 8:50Transpiling
- 12:08Deployment
- 15:37face flop pictures
- 15:49Kansas City BBQ
- 16:02Server Architecture
- 20:44The Future
related talks
28mBuilding in Rails, Backbone, and CoffeeScript
38mEmbrace the frontend revolution
19mHarnessing Microfrontends: Platforms for Web Apps
38mThe Front-End Future
47mFrontend Architectures: The Next Generations
32mRefactoring Legacy Apps with APIs and Messages
18mSoftware Architecture Building Better Applications with Architecture Best Practices
32mFrom Monolith to Micro Frontend