Data to Consumer : end to end middleware capabilities

5. Nov 2015

Más contenido relacionado

Presentaciones para ti(20)


Data to Consumer : end to end middleware capabilities

  1. Data to Consumer end to end middleware capabilities Asanka Abeysinghe Vice President, Solutions Architecture WSO2, Inc.
  2. Picture credit : http://flicker .com
  3. Evolution of the platform Platform 1.0 - Mainframe and before : centralized computing Platform 2.0 - Messaging, object orientation, SOA, EDA : distributed computing and internet Platform 3.0 - Platform 2.0 + next-generation middleware : the cloud
  4. Platform 3.0 Mobile, social, store Event driven, IoT Bigdata, analytics DevOps Iterative Cloud native Open source API driven { } Polyglot programming QoS
  5. Compliant with Microservice architecture (MSA). We will discuss MSA in detail during Pattern Driven Enterprise Architecture. architecture patterns track | tomorrow | 9AM
  6. Modern applications are System of Systems (SoS)
  7. System of systems System of systems is a collection of task-oriented or dedicated systems that pool their resources and capabilities together to create a new, more complex system which offers more functionality and performance than simply the sum of the constituent systems. - Wikipedia
  8. Systems of record are technologies that manage and store transactions, content, and processes. Systems of engagement are technologies that directly support customer interactions through software. Systems of automation are technologies that intelligently manage physical products, networks, and infrastructure. Source: Forrester Research
  9. SystemofSystems middlewarefunctional capabilities
  10. Productmapping middlewarefunctional capabilities
  11. Enterprise middleware platform : simplified
  12. Platforms are systems that support a community. A platform is an investment, often a long-term investment that will only pay for itself over a long period of time. A platform supports a network — a shared resource — and in order to thrive, it must attract and retain members. - Gray, Dave; The Connected Company.
  13. Platform of platforms
  14. Why we need a platform - Demand from the business stakeholders - Rapidly changing business requirements - Quick release cycles - Continues integration and testing - Rapid technology changes - Provide Middleware-as-a-Service (platform)
  15. Do I need the entire platform ?
  16. - Iterative architecture - Iterative implementation Picture credit : http://flicker .com
  17. Picture credit : http://flicker .com
  18. Give a code name for the platform. e.g. Digital Platform Don’t use product/vendor names.
  19. Introduce an onboarding program. Including samples, documents, patterns and training.
  20. Evangelize the platform (internally).
  21. Build foundation services and expose as APIs. Increase the developer productivity and reusability.
  22. Seamlessly integrated.
  23. Have a common enterprise architecture practices across the organization. Include architects from different BUs and architecture groups.
  24. “It was like Christmas “ Jin Chun, VP-Architecture PWI : Fidelity
  25. Thank You! @asankama asankaa AT