More enterprises are recognizing the opportunity to extend the reach and cost-efficiency of their applications by delivering them as software-as-a-service (SaaS). However, the approach to deploying in the cloud and the choice of either cloud middleware software or a platform-as-a-service (PaaS) can significantly affect the success of a SaaS implementation. WSO2 Stratos is a complete enterprise-ready cloud middleware platform designed to extend SOAs to the cloud, and it is the software that powers the WSO2 StratosLive PaaS. By providing WSO2 Carbon products as services over public, private, and hybrid cloud infrastructure, WSO2 Stratos offers an ideal platform for SaaS developers to create, manage and run enterprise-class applications and services with all the inherent benefits of a true cloud-native environment.In this session, we will be looking at the WSO2 Stratos cloud middleware platform and the benefits it offers in developing, testing, deploying and managing cloud-native applications.

1. Open Source Middleware for the Cloud: WSO2 Stratos by AfkhamAzeez Director of Architecture WSO2 Inc.

2. … the completeopen sourcePaaS & CMP

4. What are the differentiations?

5. What to look for in a PaaS?

7. What is a middleware Platform?

8. What is Platform as a Service?

9. The Key Players 7

11. All the on-premise benefits are magnified in a cloud

12. Efficiency that is valuable in fixed deployments is invaluable in large dynamic deployments!

13. Available on private, public, on-premise

14. Getting locked into a specific public PaaS will have long term repercussions

15. Open Source is a huge protection against this

16. The correct set of core “services”

18. Self-service, multi-tenancy, elasticity, metering, incremental deployment and testing

19. Offers a basis for both single-tenant and multi-tenant models

20. Lots of tenants each with their own stuff, and/or

23. Cloud Middleware Platform (CMP), or

24. Cloud Enabled Application Platform (CEAP – Gartner)

25. Not all PaaS have redistributable CMPs

26. The benefit of having a CMP is choice:

27. Run your own PaaS in a private cloud

28. More than one PaaS provider

29. Open PaaS / Open CMP fights lock-in

30. WSO2’s CMP = Stratos

31. WSO2’s PaaS = StratosLive11

33. Fast provisioning

34. Based on OSGi

35. Modular, componentized, standard

36. Multi-tenant, Elastic, Metered and Billed

37. Effective and powerful

38. Available under the Apache License

41. We believe Stratos & StratosLiveis that today!14

42. Services available in Stratoslive

44. Completely modular based on OSGi

45. Complete Enterprise SOA Architecture:

46. AppServer, ESB, Governance, Portal, BPMS, BAM, Identity and more

48. User Experience of Stratos

49. Multi-tenancy

51. Machine per tenant

52. VM per tenant

53. Share machine/VM across tenants

54. Challenges

55. Data isolation

56. Logic isolation

58. Each domain may have its own User Store and Permissions, thus have a set of users and permissions enabling users to access resources

60. Different contexts are created for each tenant

62. Otherwise tenants can write malicious code

63. Tenants can't write to file system, can't open port

64. Java Security Manager can be used to prevent it

65. Sandbox environment, similar to applets

67. Every tenant has access to an Identity Service

69. Each tenant admin can choose to manage their tenants user store either within the Stratos-internal LDAP store or using an external LDAP

70. Bulk import

71. Each tenant user has a OpenId/Infocard as well as SAML2 tokens

72. Single-signon& Single-Signoff

73. SAML2 is used across the Stratos deployment to ensure a smooth transition (single sign-on) between Stratos services

76. For successful sign in using Google Apps,

80. Carbonized Cassandra Cluster

81. Database cluster

82. Carbonized HDFS Cluster

83. <Data> PaaS Offerings

84. Apache Cassandra as a Service

85. Relational Database as a Service

86. HDFS as a Service

89. A DB will be allocated from an Amazon RDS cluster

94. will be allocated from a Cassandra clusters

95. they are isolated from other tenants in Stratos

96. it is integrated with WSO2 Security model.

97. Users can manage and share his key spaces through Stratos Web Console and use those key spaces through Hector Client (Java Client for Cassandra)

98. In essence we provide

99. Cassandra as a part of Stratos as a Service

100. Multi-tenancy support

102. will be allocated from a HDFS cluster

103. they are isolated from other tenants in Stratos

104. it is integrated with WSO2 Security model.

106. Elasticity

108. Traditional solution: Buying safety-net capacity

109. Better Solution: Scale up and down

110. Pay for the actual use

113. Number of service calls

114. Request/response bandwidth

115. Registry bandwidth (upload, download)

116. Total registry space usage

117. Send above to BAM publishers, which sends the data to the BAM Service

118. BAM summarizes periodically

120. Number of users per tenant

121. Storage space

123. Number of users

124. Appserver Service Bandwidths/Request Response count

126. Registry Resource Volume

127. Number of Request and Response counts

129. Ability to view past invoices and the current(interim) invoice

130. Securely pay the invoice via Paypal

131. Notifies the customer via email on received payments

132. Notifies the super-admin on customers exceeding the credit limit

134. Logging

136. Logs are partitioned & stored by tenant

137. Logs are sent to the Manager service via syslog

139. Log Viewer – Stratos Manager {Super-Tenant}

140. Log Viewer – Stratos Data Services Server {Tenant User}

142. Pub/Sub and Queuing

143. Queues and Topics are partitioned by tenant

144. Authorized against the tenant identity store

145. JMS

146. Backed by a multi-tenant JNDI implementation based on our Registry

147. Amazon SQS API

149. Questions

150. Thank You!