Modern Software Architectures
summary
Overview of modern software architecture trends (microservices, SOA, Erlang, Go, message passing, queues) contrasted with traditional LAMP/PHP approaches. Explains which new technologies address problems like real-time interactivity and large-scale data storage/analysis, and questions whether PHP-based monoliths still have a place or need replacing.
AI-written summary · about
chapters (36)
- 0:00Intro
- 0:31HELLO WORLD
- 1:22WE WILL TALK ABOUT
- 2:09WHY THIS TALK?
- 3:00LOTS OF PROJECTS START...
- 3:50TRAFFIC STARTS TO GROW...
- 5:39BUT SOMETIMES...
- 7:09LIVING IN THE CLOUD
- 8:52DEVOPS PHILOSOPHY
- 10:19FULL-STACK DEVELOPERS
- 11:12ARCHITECTS / PLATFORM TEAMS
- 12:42DEFINITION AND MOTIVATIONS
- 15:12CHOOSE YOUR STORAGE: CHAOS!
- 16:43CAP THEOREM
- 21:56SOA PRINCIPLES
- 22:57WHY DOES SOA USUALLY FAIL?
- 25:39HOW MICRO SHOULD THEY BE?
- 27:22ORCHESTRATION
- 28:18SERVICE DISCOVERY
- 30:11TESTING MICROSERVICES
- 31:42COMMUNICATION BETWEEN SERVICES
- 35:46TIMEOUTS AND RETRIES: MADNESS!
- 37:05OTHER PROBLEMS
- 38:33QUERY VS PROCESSING
- 39:12MAP-REDUCE
- 39:50HADOOPVS SPARK
- 40:25REAL TIME?
- 41:11FIREHOSE
- 42:14MODERN STREAM PROCESSING
- 45:47DON'T USE PHP!
- 46:47ERLANG
- 48:18GOLANG
- 50:08SCALA
- 51:51THE FUTURE
- 52:40DON'T BLINDLY FOLLOW THE TRENDS
- 53:14QUESTIONS?
related talks
45mRediscovering PHP: Modern Practices Beyond Legacy
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
51mMicroProcess Architectures: Planning for Change, & Retaining Flexibility
18mSoftware Architectures Gone Wild
54mMicroservice architecture: approaches and technologies
54mThe Long Sad History of Microservices
36mWe're gunna program like it's 1999
34mLevel up with a Microservices architecture