Apis power-mvc-for-the-web
•Descargar como PPTX, PDF•
2 recomendaciones•1,094 vistas
Slides for the panel on API perspectives & Maturing APIs at Gluecon 2011. Discussion with William Oellermann; Jeff Hoffman, and Ben Kepes
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (15)
Similar a Apis power-mvc-for-the-web
Similar a Apis power-mvc-for-the-web (20)
Último
Último (20)
Apis power-mvc-for-the-web
- 1. APIs power MVC for the WEb Panel thoughts: Achieving API Maturity @ Gluecon 2011 Steven Willmott / 3scale networks steve@3scale.net http://www.3scale.net @njyx
- 3. MVC (Model / View / Controller) Wildly Successful Architectural Pattern for Application Development
- 4. APIs are spreading across the web Seem like random points of data, each with their own rules, features, functions and value
- 5. These two things have nothing do with each other right? (apart from in the obvious way)
- 7. MVC is Model / View / Controller MODEL = DATA Model VIEW = FORM View Controller CONTROLLER = BUSINESS LOGIC
- 8. Lots of Frameworks Originally described for Smalltalk at Xerox Park (copyrights / respectiveowners)
- 9. MVC has Revolutionized Software Web App Development
- 10. Clear separation between Data, Presentation & Business Logic
- 11. First : MVC Applications Model Separate at Design Time View Baked together at Run Time Controller
- 12. Then : MVC SAAS Model Separate at Design Time View Separate at Deploy Time Baked together at Run Time Controller
- 13. So What does this have to do with APIs?
- 14. Actually Yes - APIs Enable Separation of Concerns:
- 15. Across the Web
- 16. Across Companies
- 17. Example… Model View Controller Data Anywhere in any form Third parties operating on data Many Delivery Channels
- 18. ExampleModels Model Data Anywhere in any form (copyrights / respectiveowners)
- 19. Example: Views View Many Delivery Channels (copyrights / respectiveowners)
- 20. Example: Controllers Controller Many Delivery Channels (copyrights / respectiveowners)
- 21. APIsEnableSeparation & Focus Model View Controller Data Anywhere in any form Third parties operating on data Many Delivery Channels APIs / Integration / Ecosystems
- 22. Impact Value More value from existing assets FocusonCore Business Speed Time to Market Leverage Ecosystems are strength
- 23. ArchitecturalPatterns MODELS: Push / Pull Data CONTROLLERS: TransformorOrchestrate VIEWS: Integrate and Visualise
- 24. API Maturity
- 25. Trends: Convergence MODELS: Consolidation (e.g. TwitterModelforblogging) CONTROLLERS: Similarities in CommunicationsAPIs VIEWS: EmergingWinningPlatforms WithEyeballs
- 26. Trends: Internet Operating System (Tim O’Reilly) Advertising Location Activity Streams Identity & Social Graph Image & Speech Recognition Government Data Search Payment Time Media Access (Auth / Caching / Analytics) Communications (Email, IM, …) Storage Compute Power Connectivity
- 27. Trends: Enabling components Search Advertising Location Media Access Time Identify & Social Graph Communications C.f. Tim O’Reilly
- 28. The Internet Operating System Emerging Advertising Location Activity Streams Identity & Social Graph Image & Speech Recognition Government Data Search Payment Time Media Access (Auth / Caching / Analytics) Communications (Email, IM, …) Storage Compute Power Connectivity (copyrights / respectiveowners)
- 29. Conclusions
- 30. APIs enable separation of concern – MVC patterns are emerging across the Web
- 31. An “Internet Operating System” may not be that far away
- 32. Thank You to Gluecon! Steven Willmott / 3scale networks Find 3scale at http://www.3scale.net Find me at steve@3scale.net & @njyx
- 33. Out of the box management infrastructure to power your API & App Strategy http://www.3scale.net/
- 34. /End
Notas del editor
- - Model is your data- Controller is the business logic- View is how you experience it
- - Model is your data- Controller is the business logic- View is how you experience it
- http://radar.oreilly.com/2010/03/state-of-internet-operating-system.html (this isn’t necessarilly a layer diagram – but there is a rough ordering of features)