wood burning stoves 2.0*
The moose likes Web Services and the fly likes SOA Governance in Action: Project Suitability Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "SOA Governance in Action: Project Suitability" Watch "SOA Governance in Action: Project Suitability" New topic
Author

SOA Governance in Action: Project Suitability

Kevin Florish
Ranch Hand

Joined: Jan 06, 2009
Posts: 176
I noticed whilst reading through the first chapter that SOA Governance can be applied to projects of any size. I for one thought SOA Governance was for large corporations.

If we could take a hypothetical scenario where I am a web developer using my own server. The server holds several projects involving say Java back ends, some persistence and several front end websites.

And I may want to integrate some of the services so they can be used within several of the applications.

Would this be a candidate for SOA Governance, or as a one man band am I making a huge workload for myself?

Thanks Kevin.


Java5 Tutorials | Java6 Tutorials | HTML/CSS Tutorials | JavaScript and jQuery Tutorials
J Dirksen
Author
Greenhorn

Joined: Sep 04, 2012
Posts: 13
SOA Governance suffers from a serious PR problem. Most people when they hear the words governance or SOA immediately relate it to large enterprise projects and environments. While that is an important situation and environment to use SOA Governance, it isn't just meant for that domain.

The goal of SOA Governance should be to make sure that your services are build consistently, following the standards and principles set out by your organization/department/team. Having SOA Governance allows you to easily reuse services, and see how is using your service and how. This is as important for a single department as it is for a complete enterprise.

As a 'one man band' you're probably stretching it a bit when you go full blown SOA Governance. However, if you have a centralized set of services you reuse over applications and projects it might still be a good idea to use a standard way you define your service contract (WSDL, JSON plain text description), and handle authentication and authorization.

Using service registries and introducing service and policy lifecycles might be a bit much
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: SOA Governance in Action: Project Suitability