190 likes | 205 Views
This article discusses the techniques and strategies for integrating XML-based systems using web services. It covers the benefits of Service-Oriented Architecture (SOA) and the challenges involved in implementing and managing shared services. The article also provides resources for finding publicly available web services.
E N D
Right – Web services techniques for XML-based integrated systems. From http://www.emeraldinsight.com/journals.htm?articleid=862014&show=html. CSSE 477 – SOA Architectures Steve Chenoweth Thursday, 11/3/11 Week 9, Day 3
Today • SOA - Designing architectures and services. • Turn-in the in-class SOA intro programming exercise from Tuesday. • Tomorrow – • A day to work on your presentations for week 10. • Steve may be out of town – I’ll let you know.
Typical SOA app in action You • The two circled apps – we want to make use of SOA for • Accessing outside services shown at right, and • Allowing customer organization’s apps to access us.
What about the customer? • If we also could get their order placement app within our own shop, that would be even better! • How likely? • So,
How to make it all work!? • Requires a strategy to integrate our systems with everyone else’s. • Even though they are created elsewhere. • SOA is a key to making this happen, because of growing acceptance and suitability toward this end. • Architects and management need to make “governance” decisions with systems developments.
Where we are a service consumer • We worry about available services’ functionality. • They could disappear on us! • May not be “semantically correct” for us. • No standard data models. • E.g., What’s in a “customer order”? • Those offered by competing organizations could be different, so hard to switch. • And there’s that pesky end-to-end testing!
Where we are a service developer • If we don’t understand customer requirements, we could flop as a provider! • And, we’re in a classic, perfect open market… • Where everyone knows about every competitor, their prices, etc. • Translating legacy systems to SOA always has issues. • Like converting to web-looking data types. • Need to be able to live up to SLA’s – Service Level Agreements.
For the infrastructure developer • “Responsible” for end-to-end performance. • How do you handle changes in standards and products you support? • The level of training (e.g., for the other organizations using your tools) can be underestimated! • Granularity decisions to make!
Summary – SOA architectures • Affect three different development groups: • Service consumers (programmers) • Service developers • Infrastructure developers • The more distributed these are, the greater the global consequences.
Additional resources • http://servicerepository.com/ service providers • http://webservicex.net web services by category • http://soapatterns.org/ patterns for web service development • http://ws-i.org/ OASIS, the web services interoperability org • http://xmethods.com publicly available services • http://webservices.seekda.com ditto • http://free-web-services.com/ free ones