Developer Conference 2.2 - (Mobile) Embracing SOA

208 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
208
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Developer Conference 2.2 - (Mobile) Embracing SOA

  1. 1. Embracing Service Oriented ArchitectureTom MorrisonMicro Focus
  2. 2. • Why do I want to consider SOA?• A definition of SOA.• SOA in the large enterprise, the small and medium enterprise,and for the ISV.• Principals of SOA.• What role does SOA play in bringing legacy applications toweb and mobile?• A small demonstration of a legacy application in mobile.2Overview
  3. 3. • Business drivers.– Better business decision making.– Improved employee productivity.– Integration of supply chain and demand chain.• IT drivers.– Productivity improvements.– Agile/flexible development enablement.– Application deployment that is more manageable andsecure.3Why do I want to consider SOA?
  4. 4. • A software organizing concept and methodology.• “… a paradigm for organizing and utilizing distributed capabilitiesthat may be under the control of different ownership domains.”• The Problem is ‘The Reality of Control’.• Concept of ‘Service’.– Something (the ‘service’) doing work for, or on behalf of,something else (the ‘client’).– Implementation details unimportant to the client (‘loosecoupling’).• SOA is not web services; SOA very often uses web services.• SOA is something you do, not buy4Definition of SOA
  5. 5. • The key takeaway is that SOA is a methodology to aligninformation technology (IT) with business needs.• Executive leadership.• Technology architectural leadership.• Governance.5SOA in the Large Enterprise
  6. 6. • Integration needs are more limited than the large enterprise• Distributed computing legacy tends to focus on a single,industry-specific application.• Integration may be driven by desire or need to embedservices into customers’ processes.• Emphasis tends to be on B2B, starting with web services.• Outward-looking integration raises the complexity of the IToperation beyond previous experience.• SOA architectural fundamentals necessary to managecomplexity, and cope with frequent, unpredictable change.6SOA in the Medium/Small Enterprise
  7. 7. • Loosen the knot.• Enable continuous innovation.• Reduce integration expense.• Product lines better integrated.• Become agile.7SOA in the ISV – Internal Benefit
  8. 8. • “Don’t be an integration headache.”• Products become more attractive as customers’ ITenvironment becomes more complex.• Meet custom requirements more quickly.• Make your products more useful and more valuable whetheror not the customers themselves are even interested in SOA.8SOA in the ISV – Customer Benefit
  9. 9. • Convergence of various types of services is disruptive• Disruptive technologies create opportunity.• Loosely coupled services provided by ISVs using a businessmodel similar to Software-as-a-Service.• Convergence of desktop and RIA: What piece of theapplication is where?• Automated business process flows• What else?9SOA in the ISV – Opportunities
  10. 10. • SOA is no longer the shiny new object.• The problem of service definition.– What is an ‘insured’?– Is an ‘address’ an address?• Alternatives to SOA.10What has become of SOA?
  11. 11. Demonstration
  12. 12. @microfocus or hashtag #devcon2013Follow us on LinkedIn or join the groupConnect with your peers on the Community

×