Architecting the Digital Enterprise with APIs and Marketplaces
•
3 likes•722 views
How important is it for your enterprise to be a digital one? How do you build a culture of innovation?
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (17)
Similar to Architecting the Digital Enterprise with APIs and Marketplaces
Similar to Architecting the Digital Enterprise with APIs and Marketplaces (20)
More from WSO2
More from WSO2 (20)
Recently uploaded
Recently uploaded (20)
Architecting the Digital Enterprise with APIs and Marketplaces
- 1. ARCHITECTING THE DIGITAL ENTERPRISE Mifan Careem Senior Director -Solutions Architecture, WSO2 Inc.
- 3. Digital Enterprise • New business designs that blur the physical and digital world • “Digital Business is expected to create a new $309B market for technology products and services by 2020” - Source – Gartner, 2015 -
- 4. The Journey to Digital Business
- 5. Business Architecture of Digital Enterprise
- 6. Requirement • Dialog Axiata, an Axiata group company, needed to unify the multiple development teams and unify internal app and service development and reuse • Needed a digital strategy to compete with newer over the air providers and to launch newer digital products • Provide the basis of the telco wide digital transformation Solution • Dialog built an internal and external enterprise API marketplace using WSO2 API manager and related technologies • A number of evangelism events are organized around the APIs including hackathons, workshops, seminars, conference talks etc and incentives including investment programs, prizes, leaderboards etc that promote application development • The API marketplace is coupled with full ecosystem management for end to end API and app development • https://www.ideabiz.lk/store/
- 7. Enterprise API marketplaces and Platform Business Models drive (internal and external) innovation
- 8. Digital Enterprise • An API Marketplace goes above and beyond the API Developer Portal and connects API Producers and API Consumers via Activities and Technology • Activities and Evangelism such as Hackathons (Hackathon-in-a-box) promote creation and reuse of APIs
- 9. Enterprise API Marketplaces and Platforms
- 10. 1.Customers and Vendors are Partners People are in it for the long haul
- 11. Cloud First or Start On-Prem • Multi-tenanted, shared everything • WSO2 Hosted and managed • Pay as you go • Multi-region availability • VPN tunnel to private DC • Guaranteed uptime • Limited options in customizing API Cloud WSO2 Manage Cloud Private On-Prem • Privately hosted • WSO2 managed • Upgrades, patches installation • Guaranteed uptime • Full flexibility in customization • Better control • Self hosted • Self managed • Full flexibility • Dev-ops learning curve • Self managed upgrades
- 13. 2. Businesses demand iterative, incremental architectures 3. Fail fast, react faster 4. Minimal Viable Product/Architecture
- 16. 5.Analytics and IoT drives new disruptive business models
- 17. Enterprise Publisher - Supports all Environments
- 18. Technology Platforms enable Business Platforms
- 22. Present Day Enterprise Architecture
- 23. Open Technology for Agile Digital Business
Editor's Notes
- Digital Business Enterprise Architecrure Use cases – ¾ Reference Architecture
- ; a distruptive world of People, Business and Things
- Stakeholders of a business here can vary from employees of the company to supply chain partners to producers and consumers of goods and services to the general community that a business exists in to even competitors (remember coopetition from business school?) as well
- Link to Hackathon in a box Link to API Marketplace whitepaper - WIP
- WSO2Telco, TFL, SaaS
- This is where we talk about microservices architecture a bit and also where it fits and where it does not. A good article is - http://wso2.com/whitepapers/microservices-in-practice-key-architectural-concepts-of-an-msa/
- “these are the only stuff required to build a digital enterprise” - Asanka changes: change the arrows sequence change - swap integration and api bubbles [Hasmin - This is the correct sequence, as per the stories we’ve been telling so far, first you create or expose services via API, then integrate them all……. gartner predicts (60% of digital transformation projects start with integration) integrating many systems, exposing api’s, need to have identity / security , then to have a way to understand what’s happening we use smart analytics (internal or external consumers) , get the feedback by identify usage and to improve the products you use analytics. the advantage is that it’s real time suggestion: ask the audience what they’re most interested in learning more about and spend more time on that area (reasoning is that they aren’t interested in all 5 products)