The document discusses the relationship between APIs and the MVC (Model/View/Controller) architectural pattern, highlighting how APIs facilitate the separation of concerns in web application development. It emphasizes trends in API maturity, including model convergence and the emergence of winning platforms. Ultimately, it posits that an 'internet operating system' may be on the horizon as APIs continue to evolve and integrate across various channels and data models.

1. APIs power MVC for the WEbPanel thoughts:Achieving API Maturity @ Gluecon 2011Steven Willmott / 3scale networkssteve@3scale.nethttp://www.3scale.net@njyx

2. All content http://creativecommons.org/licenses/by-sa/3.0/us/

3. MVC (Model / View / Controller)Wildly Successful Architectural Pattern for Application Development

4. APIs are spreading across the webSeem 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)

6. Maybe they Do…

7. MVC is Model / View / ControllerMODEL = DATAModel VIEW = FORMViewControllerCONTROLLER = BUSINESS LOGIC

8. Lots of FrameworksOriginally 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 ApplicationsModel Separate at Design TimeViewBaked together at Run TimeController

12. Then : MVC SAASModel Separate at Design TimeViewSeparate at Deploy TimeBaked together at Run TimeController

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 ViewControllerData Anywhere in any formThird parties operating on dataMany Delivery Channels

18. ExampleModelsModel Data Anywhere in any form(copyrights / respectiveowners)

19. Example: ViewsViewMany Delivery Channels(copyrights / respectiveowners)

20. Example: ControllersControllerMany Delivery Channels(copyrights / respectiveowners)

21. APIsEnableSeparation & FocusModel ViewControllerData Anywhere in any formThird parties operating on dataMany Delivery ChannelsAPIs / Integration / Ecosystems

22. ImpactValueMore value from existing assetsFocusonCoreBusinessSpeedTime to MarketLeverageEcosystems are strength

23. ArchitecturalPatternsMODELS: Push / Pull DataCONTROLLERS: TransformorOrchestrateVIEWS: Integrate and Visualise

24. API Maturity

25. Trends: ConvergenceMODELS: Consolidation (e.g. TwitterModelforblogging)CONTROLLERS: Similarities in CommunicationsAPIsVIEWS: EmergingWinningPlatformsWithEyeballs

26. Trends: Internet Operating System (Tim O’Reilly)AdvertisingLocationActivity StreamsIdentity & Social GraphImage & Speech RecognitionGovernment DataSearchPaymentTimeMedia Access(Auth / Caching / Analytics) Communications (Email, IM, …) StorageCompute PowerConnectivity

27. Trends: Enabling componentsSearchAdvertisingLocationMedia AccessTime Identify & Social GraphCommunicationsC.f. Tim O’Reilly

28. The Internet Operating System EmergingAdvertisingLocationActivity StreamsIdentity & Social GraphImage & Speech RecognitionGovernment DataSearchPaymentTimeMedia Access(Auth / Caching / Analytics) Communications (Email, IM, …) StorageCompute PowerConnectivity(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 networksFind 3scale at http://www.3scale.netFind me at steve@3scale.net & @njyx

33. Out of the box management infrastructure to power your API & App Strategyhttp://www.3scale.net/

34. /End