by Jack Vaughan
Sometimes we have to remind ourselves about the obvious things. Business Process Management is about processes. SOA is about architecture. The two have been involved in a tango in recent months, as software architects work with their business-side brethren to make change happen in the organization. On one level, the dance of architecture and process is very familiar. Yet it plays out today in unique ways as you will find in our BPM tutorial.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
The product activity in July was surprisingly active. July was once a ”quiet time.” Not so these days. Some July highlights as culled from SearchSOA.com product news:
Software AG has released webMethods 8.0 and integrated a Business Service Repository to increase business-IT awareness.
Kapow technologies released a new version of its flagship server. In this new version, the “Kapow Mashup Server” becomes the “Kapow Web Data Server.
KANA developed a new platform in conjunction with IBM, using that company’s SOA portfolio to address the specific needs of the customer services industry segment.
Product news sometimes helps to identify technology trends. There are exceptions, but, by and large, vendors add elements to products because customers need the new features. Recent product news on SearchSOA.com includes a look at WebLayers’ governance tool update, which matches centralizing policy management alongside distributed administration and validation, and Layer 7’s latest appliance which now monitors the performance of both services and cloud service providers and provides access controls between cloud-based services and enterprise-based assets.
While we are at it we would point to last month’s big product news out of Oracle. In ”Oracle Fusion Middleware 11g supports SCA, JavaServer Faces development” we see both the culmination of Oracle’s purchase of BEA Systems, and an impressive display of the breadth of middleware complexity today.
In closing, if you have grown accustom to Representational State Transfer [REST] architecture, and are wondering what will be next on the transactional front you may want to check out Eric Newcomer’s Ask The Expert discussion on ACID and BASE. BASE stands for Basically Available, Soft state, Eventually consistent. ACID stands for Atomicity, Consistency, Isolation, and Durability. To find out more, read “Is BASE a more scalable alternative to ACID transactions?“