2. Christophe Hamerling
@EBM WebSourcing
SOA Research Engineer
Cloud Activity Leader
Open Source Developper
Petals ESB Core Developper
OW2 TC Member
JUG Montpellier Leader
2
3. EBM WebSourcing / PetalsLink
Open Source Software Company
Develop & Provide standards-based SOA solutions for
industrial use
Long-term member of the Middleware Open Source
Community
33 employees
Middleware Architects and highly skilled Java Developpers
Active Research Team
Headquarters in Toulouse, office in Grenoble, Paris in the
pipeline…
3
4. An Open Source SOA Platform
JBI compliant
Distributed broker
ESB
LGPL
Design tool
BPEL designer
SCA designer
Studio
SOA Governance
UDDI Repository
Service Life-
Cycle
SLA
Master
LGPL
Console - Alarm
Process
Monitoring
View
LGPL
Collaborative
Process
BPMN editor
BPMN
AGPL
4
6. Project Goal
To setup a semantic service
infrastructure that scales at the
Internet level; providing large
enterprises, SMEs and end-users the
possibility to engage as peers within a
network of equals
6
7. Service & Infrastructure Level Goals
Initial Goal: Address potential billions of services
available/connected on the Web
Number of public Web services is not growing
so much…
Final Goal: Address X services and Y domains in
an intelligent way by using federation
mechanisms
Internet-Friendly SOA Infrastructure
Ease the use and the access of/to the Service
Bus…
7
12. DSB and fDSB Node Architecture
Messaging ManagementConfiguration
Delivery Channel
Router
Deployment
Installation
JMX API
LifeCycle
Distribution
Network
Registry
Topology
Local Config
WS APIMessaging API
Protocols Binding
Transporters
Node APIs Federation API
12
13. Channel Routing Transport Transport Routing Channel
Federation Service Invocation
Node B on Domain Y
Federation
Node A on Domain X
14. First Results
14
20 nodes, 4 instances/node = 80
146 nodes, 4 instances/node = 584
2 nodes, 2 instances/node = 4
INRIA G5K EC2
INRIA 45 55 106
G5K 57 28 108
EC2 113 104 55
Average Service Invocation Response Time in ms
15. The Cloud, your SOA, our solution…
http://flickr.com/hamerling
«Cloud services will not be used
in isolation from service oriented infrastructure»
Jeff Schullman, analyst at Gartner
15
16. From the Distributed to the Cloud Service Bus
Use and extend the SOA4All Federation
communication layer
Add Cloud Features
Elasticity
Nodes & Services Migration/Clustering
Multitenancy
Billing, Metering
…
16
17. Hybrid Service Cloud
Private Service
Cloud
Public Service Cloud
Public Web Service
Cloud Service Bus
Internet Node
17
18. The Cloud Service Bus Architecture
Messaging ManagementConfiguration
Delivery Channel
Router
Deployment
Installation
JMX API
LifeCycle
Distribution
Network
Registry
Topology
Local Config
WS APIMessaging API
Protocols Binding
Transporters
Node APIs Cloud API
Elasticity
Service Migration
18
19. A Cloud Service Bus is not enough!
http://www.flickr.com/photos/splorp/4640934950/in/photostream19
20. The PetalsLink SOA Cloud Stack
Cloud Infrastructure
Cloud Service Bus
SAAS
PAAS
IAAS
Authorization, Authentication, SSO, Communication, Context…
BPMN Editor MASTER VIEW MGMT
20
21. Summary
We/You deploy the Cloud Service Bus
You Deploy/Bind your services
You define services visibility with Petals Master
You create you business processes with BPMN
Editor
Process is automatically deployed to the Petals
Cloud
You monitor services, process & platform activity
You optimize, tune, …
21
Dynamicité, tout le monde peut joindre : 4All
Elasticité « humaine »
Recuperer la source du diagram
As easy as’…
Relying on a Cloud Infrastructure Framework providing the Elastic feature
Adding an Elastic Module into the DSB which will start/stop Elastic nodes based on rules (messages load, hardware load, …)
Move/replicate services on new nodes