Section 10.7. Conclusion

10.7. Conclusion

We have discussed several scenarios where an SOA can be beneficial. The requirements for the granularity that a service must provide depend on the usage scenario. The same goes for the security constraints that can be imposed upon a service. Scenarios such as a mobile one might require coarse-grained and rather insecure services, whereas scenarios such as Web-based and fat client ones will usually benefit from a somewhat smalleryet still coarsegranularity and a tighter security infrastructure. Much the same goes for the technology. Although SOAs internal to the enterprise can be based on well-understood and mature technologies, such as transaction monitors or EJBs, others such as B2B need a technology such as SOAP to offer maximum reusability and the possibility for true location transparency. Furthermore, mobile devices need the simplest protocol available to cope with the resource constraints at hand. Although it is tempting to strive for the lowest common denominator in service design, this will most likely lead to failure. It might be better to provide a service with a number of different interfaces and protocols and carefully design the required service in conjunction with the customer.

References

[Erl04] Erl, Thomas . Service-Oriented Architectures. Prentice Hall, 2004.

[Fow02] Fowler, Martin . Patterns of Enterprise Application Architecture. Addison-Wesley, 2002.

[Ha04] Harrison, Richard . Symbian OS C++ for Mobile Phones. John Wiley & Sons, 2004.

[Ri01] Riggs, Roger, Antero Taivalsaari, Jim van Peursem, Jyri Huopaniemi, Mark Patel, and Aleksi Uotila . Programming Wireless Devices with the Java2 Platform. Addison-Wesley Professional, 2001.

[SGG96] Shaw, Mary and David Garland . Software Architecture: Perspectives on an Emerging Discipline. Prentice Hall, 1996.

[BCK03] Bass, Len, Paul Clements, and Rick Kazman . Software Architecture in Practice. Addison-Wesley Professional, 2003.

[Mc03] McGovern, James, Sameer Tyagi, Sunil Mathew, and Michael Stevens . Java Web Service Architecture. Morgan Kaufman, 2003.

URLs

http://www.rosettanet.org

http://www.unece.org/cefact/