Mule Architecture - MuleSoft

More documents

Recommendations

Info

ESB Applications * Application logic is implemented via stateless services * The services run in Mule as the application container - no application server necessary * RESTful services are easier to code than SOAP - no schema validation * Suggested data exchange format: JSON for simplicity, XML for faster integration * Stateless services are easier to cluster * Stateless services permit easier upgrades and changes * Stateless services scale better Existing App Server (JBoss) batch processing via queues RESTful Web Service RESTful Web Service http://server_name/service_1 http://server_name/service_3 Mule ESB as Application Container App logic built with aggregated services Service 1 Service 2 Service 3 vm://service_2 vm://service_3
Application Components * Green items = code for the application * Everything else = Mule standard services * App is written in 100% Pure Java, no Mule-specific code for maximum portability * Transformers may have Mule API calls application HTTP2Payload Converts HTTP request to an object http://server.company.com/service_call HTTP request Payload * Transformers can have country-specific logic * Modules can have country-specific logic Bad request Claims System Module Payload HTTP response Payload2HTTP Converts the payload to HTTP response local database Application Bad response = application-specific item
Page 1 and 2: Mule Architecture Eugene Ciurana eu
Page 3 and 4: Mule As Your SOA/ROC Hub
Page 5 and 6: Integration Through Services SOA =
Page 7 and 8: Environment - First Iteration Exter
Page 9 and 10: How Well Did This Work
Page 11 and 12: Millions of Devices
Page 13 and 14: Shift Toward Consuming Resources C
Page 15 and 16: What Is Resource-Oriented Computing
Page 17 and 18: Defining Resources Resources don
Page 19 and 20: Resource Abstractions METHOD GET ht
Page 21 and 22: ROC Architecture The systems are b
Page 23 and 24: ROC Architecture Backbone: Mule ES
Page 25 and 26: ROC Architecture Service Provider (
Page 27 and 28: ROC Implementation Service Object C
Page 29 and 30: ROC Implementation MapReduce contro
Page 31 and 32: Real Life Example Trades analysis
Page 33 and 34: Real Life Example
Page 35 and 36: Real Life Example Internet Load Bal
Page 37: Rolling Out to Production No situat
Page 41 and 42: Clustering * Two or more Mule insta
Page 43 and 44: Uninterrupted Application Updates *
Page 45 and 46: Database Replication Primary Cluste
Page 47 and 48: Real Life Example • System grew
Page 49 and 50: Real Life Example Client Client Cli
Page 51 and 52: Cloud Deployment • Web and other
Page 53 and 54: Cloud Deployment legacyservices01 1
Page 55 and 56: Cloud Deployment Amazon EC2 Configu
Page 57 and 58: Mule Punching
Page 59 and 60: Scripting • Rapid prototyping •
Page 61 and 62: How Does Your Language Rate • TIO
Page 63 and 64: Selection Criteria • Outstanding
Page 65 and 66: Java vs. Python Comparisons • Ori
Page 67 and 68: Java vs. Python Comparisons • Sim
Page 69 and 70: Java vs. Python Comparisons • Cla
Page 71 and 72: Java vs. Python Comparisons 3rd Par
Page 73 and 74: Mule Services and Python • We now
Page 75 and 76: Mule Services and Python Mule libra
Page 77 and 78: Service Definition • This code is
Page 79 and 80: Portable Business Objects #!/usr/bi
Page 81 and 82: Mule Punchint Your Code Mule librar
Page 83 and 84: Mule Punching Your Code import com.
Page 85 and 86: Deployment Topologies
Page 87 and 88: Application Deployment Web Services
Page 89 and 90:
Application Deployment This archite
Page 91 and 92:
Application Deployment Data Center
show all

Mule Architecture - MuleSoft

Create successful ePaper yourself

Delete template?

Save as template?