Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Integration patterns and practices for cloud and mobile computing

2.829 visualizaciones

Publicado el

Integration patterns and practices for cloud and mobile computing

Publicado en: Tecnología
  • Very informative presentation! Many organizations struggle with the challenges that cloud integrations can alleviate such as data discrepancies across systems, validation of data processes and cumbersome manual intervention. The benefits cloud integration provides can extend beyond helping automate operations and connecting different applications. Cloud integration can also help businesses understand customers better, cultivate new revenue streams and create operational efficiencies that offer a quantifiable business advantage.http://www.nextphasesystems.com/cloud-and-security/cloud-integration/
       Responder 
    ¿Estás seguro?    No
    Tu mensaje aparecerá aquí

Integration patterns and practices for cloud and mobile computing

  1. 1. Integration Patterns and Practices for Cloud & Mobile Presented By SHAKIL AKHTAR
  2. 2. About Me… v Open Source Technologies Enthusiastic v Independent Architecture &Technology Consultant v TOGAF 9 Certified v TOGAF 9 Foundation Certified v Spring Source Certified Enterprise Integration Specialist v Oracle Certifier Master Java Enterprise Architect (SCEA 5)-All Levels. v SCJDWS. v SCWCD v SCJP v Spring Source Groovy Grails Training Certified. v Gemfire Cloud Training Certified v Liferay Training Certified
  3. 3. Agenda v EIP and their usage v Integration Best Practices for connected world v Patterns in Cloud & Mobile Computing v Use Cases
  4. 4. Never Ending Problem?
  5. 5. What’s so special v If we were to believe Microsoft it would all just be Web Services v Microsoft are not to be believed though, fortunately, integration is complex v XML was suppose to simplify things but you can not retro-fit XML everywhere and in many cases it’s not a good choice § Low Latency v Lets start with defining problem
  6. 6. Introduction v Integrating Enterprise Application can be done in many ways v Each way has its own pros and cons v Best solution depends on requirements v Things to consider § Coupling(logical , temporal) § Synchronous or Asynchronous § Overhead § Data Formats § Reliability
  7. 7. A Quick History of Integration B2B • EAI,B2B Integration • EDI, RosettaNet, Swift • Service based orchestration SOA • BPEL4WS, ESB, CEP SaaS • iPasS platform • SaaS-SaaS, SaaS-On-Premise based integration Mobile • Less service interruptions • Fewer Performance Problems
  8. 8. Integration Types v Information Portals v Data Replication v Shared Business Function v Service-Oriented Architecture v Distributed Business Process v Business to Business Integration
  9. 9. EIT-Information portals v Basic data aggregation v Single source of information
  10. 10. EIT-Data Replication Data Store A Data Store B v Data moves on database tiers v Consistency is dependent on DBMS information
  11. 11. EIT-Shares Business Function v Moves the control to the shared function logic v Tightly couples all clients to the application interfaces
  12. 12. EIT-Service Oriented Architecture v Connects distributed applications and exposes services through a standard contract v Complex to design and implement
  13. 13. EIT-Distributed Business Process v Single point of invocation v Requires other integration solutions to function
  14. 14. EIT- Business to Business Integration v Higher level of integration v Still requires an integration solution
  15. 15. Enterprise Integration Style v File Transfer v Shared Database v Remoting v Messaging
  16. 16. File Transfer v Simple, Interoperable, Fast v Unsafe § Non transactional, Concurrency Issues, Security v Platform dependent v Not event driven
  17. 17. Shared Database Data Store v Simple, Transactional, Triggers(But not portable) v Slower v Impedes Schema evolution § Less with No SQL DBs
  18. 18. Remoting v Convenient, Stick with OO Paradigm, Speed v Cons § Not Interoperable, Hard to version , Not Scalable, Hidden Complexity Func-on Call Reply
  19. 19. Messaging Applica-on A Applica-on A Applica-on A Event Layer Message Bus v Asynchronous, Efficient, Scalable, Extensible v Cons § Complexity, Longer Response Times, Loss of transactional Context, Loss of Security Context
  20. 20. Tightly Coupled Interfaces v Requires minimum n(n-1)/2 interfaces, where n is the number of integrated applications
  21. 21. Loosely Coupled Interfaces v Requires exactly n interfaces, where n is the number of integrated applications
  22. 22. EIP and their usage
  23. 23. Enterprise Integration Usually evolves messaging
  24. 24. Why we need patterns ? v Solutions for the same kind problem v Business Integration v Scaling
  25. 25. Did you hear about GoF?
  26. 26. Enterprise Integration Patterns v Solutions for the same kind problem v Commonly used for Application and Business Integration
  27. 27. Enterprise Integration Pattern
  28. 28. Applying EIP in Internet Banking(IB)
  29. 29. Using EIP Implementation API ABS Client-Bank Oracle procedure Java WS Spring Integration IB POS JDBC Porcessing Card-backoffice
  30. 30. Integration Best Practices for Connected World
  31. 31. Patterns in Cloud & Mobile Computing
  32. 32. System Integration In Cloud Era
  33. 33. Cloud to Cloud Integration v In many ways cloud to cloud integration is no different than other integrations. But they have some unique characteristics Cloud to cloud Other RESTful SOAP/WSDL OAuth authentication Username/Password JSON XML No Middleware Middleware Often Social Data Business/transactional data No Network Infrastructure req Network /Infrastructure req
  34. 34. Cloud communication services v Message Oriented Middleware v Reliable Messaging v Exactly once delivery v At-least once delivery
  35. 35. Cloud to Cloud Integration patterns v Outbound v Inbound v Hybrid v UI Integration
  36. 36. Outbound Integrations Salesforce v Apex Callout § Use Apex to invoke a WSDL/SOAP or REST service v Force.com toolkits § Usually outbound integration v Outbound Messaging v Apex Email(Outbound)
  37. 37. Inbound Integrations Salesforce v Force.com APIs § SOAP, REST, Chatter REST, Bulk v Apex Web Services § SOAP, REST v Force.com toolkits
  38. 38. Hybrid Integrations Salesforce v Integration typically initiated by an outbound call from Force.com v External cloud application then makes a callback to retrieve/update Force.com data
  39. 39. UI Integration LinkedIn widget embedded in Visualforce. A public Force.com Sites page shown in Facebook.
  40. 40. Int e g r a t i on in the Enterprise Mobile World
  41. 41. Mobile Integration
  42. 42. Mobile Integration
  43. 43. Enterprise Mobile Integration Patterns
  44. 44. Enterprise Mobile Integration patterns v Real Time Integration v Queue Based Integration v Event Based Integration v Enterprse Systems APIs
  45. 45. Real-Time Enterprise Systems Integration Enterprise System Var mySAP= App.Services(‘SAP’).Login({credentials}); Var mySF= App.Services(‘SF’).Login({credentials}); mySAP.Invoke(‘invokeRFC’, {parameters}); mySF.Invoke(‘GetLeads’, {parameters}); Service SAP Connector MBaaS Corp Network SF.com Connector
  46. 46. Real Time Integration v Access Content v Server Side Script
  47. 47. Access Content Var mySAP= App.Services(‘SP’).Login({credentials}); mySF.Invoke(‘GetItem’, {parameters}); Enterprise System Service Sharepoint Connector MBaaS Corp Network Content Transformer
  48. 48. Server Side Script Var mySAP= App.Services(‘ORCLDB’).Login({credentials}); mySF.Invoke(‘Query’, {parameters}); Enterprise System Service Oracle DB Connector MBaaS Corp Network Server Side Script
  49. 49. Queue-Based Enterprise Systems Integration
  50. 50. Queue-Based Integration Mobile Queue Service JSONObject msg = new JSONObject(... Queue queue = myApplication.Queue("myQueue"); queue.Enqueue(msg, mOnEnqueueCallback); SAP Application MBaaS Corp Network
  51. 51. Event-Based Enterprise Systems Integration
  52. 52. Event-Based Integration MBaaS Channel Mobile Event Service Channel Corp Network Siebel Application __application.pubSub.Subscribe( “channel name”); _application.pubSub.Publish( “channel name”, {message});
  53. 53. Enterprise Systems APIs Mobile Platform ( ex- KidoZen) SaaS Your Datacenter Kido LOB Agent LOB LOB Link API
  54. 54. Mobile Integration Mobile Middleware MDM-MAM On-Premise Enterprise SaaS Enterprise Mobile Testing Professional Services Telcos Mobile Development
  55. 55. Use Cases
  56. 56. IoT
  57. 57. Smart Cities
  58. 58. Summary v Integration style and patterns v Cloud Integration Patterns v Enterprise Mobile Integration Patterns v Best Practices
  59. 59. Thank You!

×