Your Object Model Sucks & an Introduction to Resource Oriented Computing
summary
Argues that software should treat everything as addressable stateful resources rather than objects, using a resource-oriented runtime called NetKernel that runs nearly 4,000 microservices across 900 “microwebs” and 200 modules. Demonstrates a visualizer that records cascaded resource requests, a cache heat map for dependency-aware caching, and an active-URI addressing idea from 2002. Claims linear scaling across multicore, large cache hit rates, and production use on telecom and high-traffic retail sites.
AI-written summary · about
chapters (15)
- 0:00Resource oriented computing intro
- 2:35Web as resource system
- 8:21Service architecture challenges
- 10:50Core principles of resource computing
- 15:22Proving resource model against complexity
- 18:13Live system architecture
- 21:45Resource requests vs traditional code
- 23:10Scaling with resource orientation
- 27:28Performance benefits of resource abstraction
- 31:42Caching and dependency models
- 36:23Energy efficiency in computing
- 39:12Virtual resources and cache consistency
- 40:37Simplifying multi-party interactions
- 43:46Resource development for non-devs
- 47:19Summary of resource computing
related talks
48mIT Architecture : All your micro-services are wrong PERIOD!
42mResource-Oriented Architecture With Waves
33mFrom Enterprise Architecture to Software Design - Critical Thinking
38mWhat Object-Oriented Programming Was Supposed to Be: Two Grumpy Old Guys’ Take on ...
42mMicroservices and Modularity or the difference between treatment and cure!
52mResources, For Real This Time (with Webmachine)
39mSoftware is a meal best served with different architectural spices
18mEffective Resource Management: Through Systems Design