The document discusses the WSO2 Enterprise 3.0 Platform, which provides tools for mobile, social, big data, cloud, APIs and open source development. It offers over 190 components across 20+ products for security, integration, mobile, big data, governance and other functions. All products are fully integrated through a common OSGi component model and multi-tenancy. The platform allows customers like Cisco, Boeing and eBay to build applications across legacy systems, APIs, middleware and big data using a variety of development tools in a hybrid PaaS environment.

1. Enterprise 3.0 Platform
Platform for Mobile, Social, Big Data, Cloud, APIs, Open Source
By John Mathon
June 6, 2014

2. About the Author
o 10 patents, publish / subscribe, multipath low
latency high reliability messaging, Content
management in file systems, peer to peer
messaging over WAN… others
o founder and CTO of TIBCO
o Twitter: @john_mathon
o Blog: CloudRamblings
johnmathon.wordpress.com

3. Quick WSO2 Commercial
8 years Apache and Open Source Contributor
o … from the past – Axis2, Synapse and contributors on 20
other Apache Projects
o All wso2 software is 100% open source not enterprise
licensed in any way (Apache licensed)
o Contributed Stratos as Cloud PaaS layer
o True polyglot, hybrid PaaS
o Contributors WSO2, Indiana University, Citrix, EngineYard, Cisco,
NASA, SunGaurd, Georgia Tech, …
o Also have an open source cloud Ecosystem PaaS
o App Factory
o WSO2 will also offer Cloud Services based on all our open
source tools in 2014/2015

4. What’s different about WSO2?
WSO2 Carbon consists of
190+ individual bundles (components)
20+ individual products (ESB, CEP, BAM, …)
8+ platforms (Bigdata, APIM, PaaS, …)
Use as little or as much as you want: Security,
Integration, Mobile, Bigdata, Governance,
PaaS, API Management Products

5. Why?
Every Product Built by WSO2 Fully Integrated:
1. OSGi Component Model
2. Multi-tenancy model the same
3. Scalable distributed Cloud Native
4. Admin, Logging, Governance
5. HA/DR, APIs, Configuration,
6. Run time management, Runbooks
7. Deployment across all components
8. Everything uses everything else

6. WWSOS2O S2oftware
Legacy Integration Stack
ESB, C/As, Adapters, DSS, MB, AS
API Management
APIM, ELB, ESB, BAM, IM, DSS, SS, ES
Middleware / SOA
ESB, C/As, MB, BPS, DSS, AS
BigData NSA for you
BAM, DSS, SS, Cassandra, C/As, CEP, UES
Advanced Governance and
Security
IM, gReg, BRS, BAM, CEP, MDM, MAM, ES
Mobile
MDM, MAM, ES, gReg, AS
POLYGLOT HYBRID PAAS
CC, CS, CA, ELB, CEP
Connected Business
APIM, App Factory, ES, Integration, NSA4U
Ecosystem PaaS
Private PaaS, BPS, DSS, SS, ES, Git, Maven,
Jenkins, Redmine,
Development Tools
Developer Studio, CodeEnvy, UES

7. Over 200 Customers: Ebay, Boeing, Banks…

8. Some Key customers for WSO2
o Cisco – 7 instances with telecom providers
o Boeing – App Factory and Stratos
o State of Arizona
o State of South Carolina
o Ebay
o + 200 more
END OF COMMERCIAL

9. 60 years ago the first computer
40 years ago the first microcomputer
20 years ago the internet
Today Cloud, IOT, PaaS, Mobile…

10. These technologies iterating faster than
any technology before
o The Cloud
o Mobile
o Open Source
o BigData
o Social
o APIs / Services
o Reuse
o PaaS
o iPaaS
o The Store
o SaaS

11. A huge amount of software over the
years – wasted effort
o Every major company in the world has in
general spent billions on software in silos
repeating over and over the software of its
competitors and others
o Low productivity tools in general
o High cost to put something in production
o Time to delivery measured in year time-frames

12. Software development has changed
o New languages – Ruby, Php, Scala, Clojure, …
o New Open source components – Bigdata, IaaS, PaaS,
Languages, WSO2, Storm, Git, Maven, Jenkins,…
o New APIs – Google, Netflix, Twitter, Salesforce, Twilio, Square,
Kinvey, Splunk, Kumulos, RDS, Cloudant, …
o New Development Frameworks and cloud approaches
o DevOps / PaaS
o Chaos Monkey – develop resilient not reliable
o Cloud Native – build to start small and scale
o Application Frameworks - Wicket, Lift, Spring, Rails, Grails…

13. Cloud Companies changed the model
o Twitter, Google, Yahoo, Facebook, Netflix, all built without
Proprietary software using a shared model of open source
development: high speed iterations
o Linux, mysql, hdfs, hadoop, Java, Ruby, Tomcat, PHP, Apache …
o These projects would go back and forth from company to company
collaborating even as they competed.
o Unprecedented scale : Google 3+ billion users, Facebook 1+Billion
users, Yahoo 2+billion users, Twitter – billion messages/day, Ebay 5
billion transactions/day, Amazon cloud division growing at 136%
annually
o New Generation of open source:
o Cassandra, Mongodb, OpenStack, Wso2, Cloud Foundry, Scala, Spring,
Rails, Docker, KVS, Phonegap, html5, firefox, chrome

14. What is the cloud? Many things
o IaaS and Infrastructure Services (compute, data)
o *6B 2013, 136% annual YOY growth
o SaaS (Web Services and applications)
o APIs (at least 20,000 today doubling annually)
o PaaS and Platform Services (iPaaS, DaaS,
APIMaaS, BPMaaS…)
o *14B by 2016
o Mobile Apps, Web and BaaS
o Personal Cloud
o Internet of Things
*Gartner, 2013

15. Why is the Cloud overwhelming?
o Most companies are not/should not be managing
technology at the level they are
o They are not competent at security, cost management, optimization or technology in general
o vastly underutilization of what they acquire
o unnecessary duplicative work of many people doing the same technology over and over
o technology that is being used way beyond it’s productive life.
o Universal Connectivity - People, Things, Applications
o Network Effect - Spurring massive cascading unpredictable
innovation
o Possibly not all positive
o Overall huge cost savings and improved efficiency
o Due to the first and second points the US/World economy
will see massive gains in productivity and improvements in
services and technology usage

16. IoT, Mobile

17. Let’s Look at the Platform in Parts
o Development
o Open Source / APIs / Store key to reuse
o Big Data, Languages, Frameworks, Tooling, Test
o Deployment/Production
o PaaS, InnerSource, The Store, Mobile
o Topics Not being Covered
o Security, Perf Mgmt, SLA management

18. Software Development has Changed
o The Cloud
o Mobile
o Open Source
o BigData
o Social
o APIs / Services
o Reuse
o PaaS
o iPaaS
o Enterprise Store

19. Open Source
o Black Duck Survey
o 2014 80% of respondents say code quality vs
proprietary why they chose OSS software
o In 2007 80% rank cost as primary driver
o 2014 80% said access to source code important
o 2014 OSS Attracts and retains talent

20. Key Technologies available in Open
Source Components
*Just the tip of the iceberg
o Infrastructure: Linux, Ubuntu, Suse, KVM,
Docker, OpenStack
o Agile Development: Eclipse, CodeEnvy, Java
o Build: Maven, Jenkins
o Data: Hadoop, Cassandra, Pentaho, MySql
o Integration: WSO2, Redhat, Mule
o Deployment: Apache Stratos, Apache Cloud
Foundry, Chef, Puppet

21. Cloud Services / APIs (20,000+ 2x/year)
* just the tip of the iceberg
o Geo-location, places, mapping, directions, search, ratings …
o Calenders, events, People, organizations, relationships,
interests, history
o IoT find my car or anything, UAVs, robots, sensors, actuators
o Financial … you name it
o Esoteric Stuff … find patterns in data, recognize people, real-time
triggers for anything, calculate almost anything,
visualizations tools
o Mobile Apps back end services
o Development technologies (writing code, deploying, testing,
sharing, …)
o Collaboration tools, productivity and storage
o Buying, selling anything, advertising

22. Network Effect
o We learned in early messaging days that once a messaging
“bus” was in place enterprises wanted to leverage the
services
o So we invented mediation, enterprise integration patterns, brokers,
histdb, calc engines, enhanced routing, …
o The same will happen to the cloud but on a much larger scale
o Services
o Information
o IoTs
o The Future is going to see massive growth from the network
effect of these services

23. Network Effect
Exponentially Increasing Value
Drone
Tesla Glucose
Waze Uber Yelp
Smartphone1
In a car
Smartphone2
In a restaurant
Medical
Monitor
Service
Smartphone4
On the street
Smartphone3
In a taxi
Monitor
GPS
Emergency
Vehicle
Search

24. New IT Delivery => Responsive IT
http://wso2.com/whitepapers/the-path-to-responsive-it/

25. API Manager Components

26. Publish and Socialize to facilitate Reuse

27. BigData Lambda Architecture
http://srinathsview.blogspot.co.uk/2014/03/i
mplementing-bigdata-lambda.html

28. BigData - big part of the new Platform
o Information is knowledge (Google proves that)
o You can create automation after the fact
o Put automation in later instead of burdening real-time
processing
o More agile, less affected components
o Discover things anytime and add functionality
o Big Data Makes you look smart
o Big Data gives you agility

29. WSO2’s integration vision
o Lean, high-performance approach that can scale from routing
and mediation to full transformation and integration
o Modular components are essential: integration is an ongoing
process not a one-off deployment
o Seamless transition from on-premise to private cloud to public
cloud
o Same codebase runs everywhere, inherently cloud-native
o Ongoing simplification of the developer experience as cloud
changes the game
o Real-time event processing and time-based event
architectures are going to have a significant impact on
integration

30. Increase Business Innovation By
Enabling the Long Tail

31. Governance Note that App Factory includes the other capabilities
API Manager
o Governance of APIs
including lifecycle as well
as runtime
o Subscription model
o Themable portal
o Usable for both
internal and external
APIs
o REST and Web
interface
o Modular and
extensible with full
Identity and Governance
Governance Registry
o Governance of APIs,
Services, Projects, etc
o Extensible Metamodel
o Versioning, deep
dependencies,
notifications
o Lifecycles integrated
from Services to APIs
o Multiple standard
interfaces: REST, JAXR,
UDDI, WebDAV, S-RAMP,
AtomPub
App Factory
o Integrates Governance
into the actual build, test,
deploy via automation
o Integrates project
setup, issue tracker,
continuous build, test,
code quality metrics
o Manages roles and
permissions
o Manages datasources,
APIs and resources
o Automated and human
workflows for dev, test,
staging and production
o Automated DevOps
into PaaS using Puppet
and Apache Stratos

32. Connected Business Attributes

33. Connected Business Reference Architecture

34. PaaS is “aaS” for Services and Applications
Development (see blog below)
o Low Initial Cost to Deploy
o Incremental Cost as you use or develop more
o Automated Deployment
o Management Built-In
o Best Practices baked in
o Self-Service
o Lifecycle Managed
o Reuse
o Resource Sharing
johnmathon.wordpress.com CloudRamblings – A simple guide to Cloud Computing

35. Public IaaS Vendors – large variability
High Risk – not all PaaS’s run on all IaaS
10:1 price / performance or more
Dell*, Azure**
o Microsoft (Free)
o Dell - On-premise like
Joyent**, SoftLayer*
o High Performance
o Joyent special virtualization,
© WSO2 2014
SmartOS
o Softlayer – bare metal
o MongoDB, Hadoop
Rackspace*, HP*
o MySQL
o OpenStack Pioneer
Google**
o Google Compute Cloud
o Google App Cloud
Amazon AWS**
o Wide variety of choices
o Lots of extra value
services
o Poorest performance
o Highest cost
*OpenStack ** Proprietary

36. Why so many PaaS?
Bottom Line: Faster Time to Market
Cost
$$$$$$$$$$$$$$$$$$$$$$$ SAVED!
Before - software development is
costly, risky and slow process
o Do tests on early versions of software to determine loads
© WSO2 2014
from customers
o Plan demand expectation and hardware required
o Acquire hardware and networking equipment for a time
period including additional hardware for failures and
expected peak periods
Time
o Find space for hardware, plan network integration plan, rule
changes in switches, routers, update configuration
management, outages for upgrades and changes
o Test hardware and network with software to insure it works
o Understand failure modes, when to scale, runbooks for
different scenarios, train people in operation and what to do
in different scenarios. Write scripts to detect scenarios and
provide needed information in failures.
Cost
o Write or acquire management tools, put in instrumentation in
hardware.
o Plan for upgrade strategies, outages and SLA measurements,
backup policies.
o Beta customers
o Go Live
Now – cheaper, faster, less risky
o Choose IaaS vendor
o Choose PaaS platform
o Write some runbooks for different scenarios,
train people in PaaS operation
o Deploy software
o Beta customers
o Go live
SAVED!
0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100%
Time
Development
Test/Deployment
Operations

37. Polyglot – pluggable componentized

38. Hybrid Capability Has been deemed
Important which is why we see some
possibly misusing the term
o Change cloud vendors based on:
o Security
o Cost
o Zone Coverage
o Performance Problems
o Vendor instability
o Or any reason that may occur
o Use Multiple Clouds
o Have on premise hardware as well as public
o Burst on demand
o Run certain services in some clouds that perform better
o Run some tenants in some regions on different clouds
o Run production, test, demo, staging … in different clouds
Some Vendors claim Hybrid meaning: not different types of clouds. Seriously
restricts choices

39. You die and go to Heaven in the Cloud
Heaven is a PaaS
You ask at the gates:
Is Heaven PaaS a Hybrid PaaS?
Saint Peter Responds: No, there is
Only one Heaven and you will find it perfect
You’re a little skeptical but you nod
and ask: Is Heaven a Polyglot PaaS
Saint Peter responds: No, everybody in
Heaven speaks the same language
You ask: Does Heaven have multi-level
multi-tenant isolation?
Saint Peter is clearly getting annoyed and
Disturbed at the direction of your questions:
We have no secrets here in Heaven.
Finally you ask: Does Heaven have multi-tenant
component sharing?
Saint Peter: Look boy, you are looking for hell.
There they have many different hells, they all
Speak in tongues and everybody is a whore.

40. Ecosystem PaaS

41. o Data Services
o Analytics
o Stateful
o Stateless
o Rules
o Governance
o Business Processes
o Messaging and Translation

42. Boeing Digital Airline

43. Solution Architecture

44. App Factory screenshot
4
/

45. CXO Dashboard
(C) WSO2 2014

46. Summary

47. Where are we today?
o Open Source has emerged as equal / better
o Massive innovation causing a tsunami of reuse
o Massive innovation burst
o Cloud massive and growing fast
o API Movement driven initially by mobile now
becoming the new paradigm
o Social Emerged as a key factor in success of
reuse
o Continuous Integration / DevOps evolving to
PaaS, iPaaS and new PaaS flavors

48. The New Paradigm for Productivity
has emerged
1. Leverage Open Source as much as possible
1. Off the shelf or contribute if you can
2. Consider everything an API (think about user deeply)
1. All new services as APIs
2. Refactor existing services as APIs with Proxies
3. Socialize your APIs
3. Leverage PaaS to build and deploy fast frequently
4. Develop an internal Open Source – Inner Source Collaborative capability
and API Centric reuse
5. Connect everything you can internally
6. Leverage BigData to provide intelligent mediation
7. Provide the services: Mobile Apps, APIs, Web Apps, PaaS, iPaaS your
customers or partners want : Become a Connected Enterprise to lead
your market

49. Cut time to market by 80%
1. 20+ products
2. No Integration to leverage multiple
products unlike other vendors
3. DevOps PaaS deployment
4. no license negotiation license cost
5. Graphical Development Tools / Less coding
6. Innovative Quick Start Program
7. Open Standards Support Throughout
8. Lean Components use anywhere

50. More Information
o John Mathon john@wso2.com
o Twitter Feed: @john_mathon
o Blog: johnmathon.wordpress.com
o Cloud: wso2.com/cloud
o Download: wso2.com
o App Factory Signon:
https://cloudpreview.wso2.com/