PNW SOA Commons
Last week I submitted a new project request to be hosted at SourceForge.net - which I have named: PNW SOA Commons.
[I had to abbreviate the PNW (Pacific Northwest) due to a field limitation for the name of the project]
The project is also known by pnwsoacommons
I chose the Apache License V2.0 - but that's with no particular strong feeling one way or the other. The purpose of the project is to provide a repository for collecting and organizing artifacts that will help other development teams implement SOA adoption for easily / rapidly into their organizations.
Peter Schooff and I have recently had a short exchange via comments on his blog Twenty-Four Seven Security (see Why is SOA Security So Difficult?) - and I am looking forward to his future blog entry that might provide some very interesting experiential data points for other SOA Architects to ponder...
Peter,
An interesting post.
On a related topic, would you mind sharing with your readers some specific details of technology / vendor products that have allowed you to successfully implement SOA Governance - and what level of automation was provided by the selected tools? Or what you were left to implement via manual procedures?
Thanks,
Kelvin Meeks
Posted by: Kelvin Meeks at January 17, 2008 04:19 PM
Excellent idea, Kelvin...stay tuned and I'll try to get to it next week.
Posted by: Peter at January 18, 2008 01:12 PM
No comments:
Post a Comment