Digital transformation is a key enabler for both existing enterprises transforming themselves to compete in the modern marketplace and for newer startups trying to break into the business domain. Being able to involve internal and external stakeholders by exposing existing internal services as managed APIs whilst carefully governing your data is a core step in this process. Being able to adapt a lean devops process is a bonus. This webinar serves as a primer to your digital transformation journey. It will discuss API management as a coexisting solution within an enterprise How that API management ties into the management and governance of data Concepts of lean devops and containerization

1. Solu%on Architecture Pa1erns for
Digital Transforma%on
Asanka Abeysinghe
Vice President, Solu8ons Architecture
1

2. Digital Experience
2

3. real-time
personalized
geo sensitive
predictive
CX

4. Digital Enterprise
4

5. person
applications
platforms
network

6. web apps mobile apps two-side
platforms
multi-side
platforms
value
networkssocialnetworks
games
geo-apps
financialservices
citizenservices
healthcare
citizenservices
smartcity
connectedcar
smarthotel

7. Recap
• API Management as a co-exis8ng solu8on
• Moving towards a leaner deployment in your
enterprise
7

8. { apis }
8

9. 9

10. API Management as a co-exis8ng solu8on!
• API Management itself is not a new paradigm
• It is not an aJerthought any more
• API Management to complement exis8ng services
• API Management completes the enterprise IT landscape
• API Design a key factor in defining the scope of APIs

11. {apis} are the DIGITAL connectors
11

12. Universal connectors, par0cularly APIs and
Apps, mean that many new markets, in fact
thousands of market niches, can be served
with rapidly created, low fric0on,
lightweight content and services, quickly
building mass market adop0on.
- Dave Gray: The Connected Company

13. API Design
• API Design would determine how a service is exposed to its
consumers
• API Design determines the adaptability of a service
• Two main approaches
• API 1st
• Service 1st

14. Top-down approach.

15. API 1st
• API Centric design approach, design backend services based
on the requirements of API consumers
• Strong linkage between services, APIs and service consumer
expecta8ons
• BeSer adaptability and reusability of API
• Can be done when designing new services or re-architec8ng
exis8ng services

16. Service 1st
• APIs are designed based on service requirements
• Greater role played by a service integra8on layer to
orchestrate and aggregate services
• More applicable for rigid organiza8ons that cannot re-design
their exis8ng services

17. Which approach is beSer?
• Depends on which approach is most applicable
• Use API 1st whenever possible
• If services are rigid, build the API Management around
exis8ng services
• Objec8ve is to achieve an API centric organiza8on

18. API Management plaZorm
18

19. Microservices & containers
19

20. "Micro" is a concept of scope rather
than size.
Source : Gartner

21. A microservice must have a single
purpose and be loosely coupled in
design and deployed independently
of other microservices.
Source : Gartner

22. MSA
22

23. container-na8ve
23
§ Rapid start (<1-2 seconds)
§ Low memory footprint
§ Single func8on
§ Immutable – no deployment
§ Not long running
§ No request dispatching Sanjiva Weerawarana , CEO – WSO2,Inc
http://eu16.wso2con.com/videos/

24. Summary
24

25. person
applications
platforms
network
API API API

26. person
applications
platforms
network
API API
social
consumer
provider
partners
API

27. person
applications
platforms
network
API API
social
consumer
provider
partners
API
external/internal APIs
internal APIs
external APIs

28. 28
Automated tes%ng
Con%nuous integra%on
Support for containeriza%on (container-na%ve)
Support for devops automa%on
Support for (rapid) distributed deployment
Lean, independent run%me
Build *-microservices

29. Filling the gaps: technologies for digital transforma8on
29

30. 30

31. technology
partner of your
digital journey.
http://wso2.com

32. CONTACT US !