120 likes | 253 Views
Grids@Work, October 2008, Nice Using ProActive to bridge Grid and SOA The AGOS project Frédéric Linder Program Director, Service Oriented Architecture Oracle Technology Consulting. AGOS Grid Architecture for SOA. Building a Platform for Agile SOA with Grid. Partners and Solutions.
E N D
Grids@Work, October 2008, Nice Using ProActive to bridge Grid and SOA The AGOS project Frédéric Linder Program Director, Service Oriented Architecture Oracle Technology Consulting
AGOS Grid Architecture for SOA Buildinga Platform for Agile SOA with Grid • Partners and Solutions • Use Cases
AGOS: What for ? • Context: • End of Moore law • Data size increase • Processing Time increase even faster (Data size + precision) • AGOS Objectives: • Create an architecture and environment for integration of • SOA business management with • GRID IT management • Well fitted for data intensive and computational intensive applications: • Enact sub-parts of a BPEL workflow on dynamically allocated resource • E.g.: Financial Simulations, Insurance, Revenue Management, BIO… • Full dynamic scheduling of Services on GRIDs in the future • Integrated Management of SLO, SLA, QoS: • Bottom to top: • Dynamic enforcement: Adaptive behavior
Market Hype Cycle Source: Gartner (February 2007)
Service Oriented ArchitectureComposite Applications BPEL Rules Human Task Mediation SCA Composite Pluggable Service Engines SOA Composite Editor Mediation BPEL HumanTask Rules … Policy Management BPEL orchestration Policy Manager Service Infrastructure OptimizedService & Eventing Infrastructure Human Tasks Web servicesand adapters … SDOADF BC B2B ETL JCA SOAP Business Rules Common Connectivity Infrastructure
Why Run SOA on Application Grid? 2nd Page JSF Order Order submit submit 1. Response times for Web users / service consumer for synchronous requests 2. Calls to backend systems for read only data generate load and result in performance hit Packaged Application 3. Using databases as a state repository and temporary store loads DB, incurs I/O cost 7. Sharing data between Web and SOA tiers Databases 4. Building stateful services that are fault tolerance and performant. How? Java / C# Bus Logic 5. Hitting backend systems drives mainframe MIPs and results in performance hit Mainframe / Legacy External Service BPEL 6. What happens if external service is unavailable?
Solution | SOA on Application Grid 2nd Page JSF Order Order submit submit • Cache entire result of service invocation first time and reuse 2. Front-end calls for read-most data with cache to avoid hitting backend systems Packaged Application 3. Read directly from cache to improve response time and batch writes to improve throughput 7. Share data between tiers using cache Databases 4. Stateful business logic that is fault tolerance and performant built on data grid Java / C# Bus Logic 5. Cache data and reduce traffic going to mainframe Mainframe / Legacy ? External Service BPEL 6. Cache result of external service calls giving fault tolerance for read only/ read mostly data Oracle Coherence Data Grid
IDM RAC RAC OFM 11g Maximum Availability ArchitectureActive/Active ActiveData Center 1 Active Data Center 2 Global Router Firewall Firewall Web Tier Web Tier Firewall Firewall Low Latency High Bandwidth WAN Proactive SOA / BPEL J2EE Proactive SOA / BPEL J2EE Coherence Data Grid Service IDM Stbdy DB Firewall Firewall Oracle DataGuard
AGOS Grid Architecture for SOA Buildinga Platform for Agile SOA with Grid • AGOS Solutions • Support for Professional Open Source