Tracking change and innovation in the enterprise software development community
The Intel® SOA Expressway SOA Soft-Appliance ...8x the performance at 1/2 the cost
OVUM Butler Group Technology Audit
451 Group Review of Expressway
PushToTest Performance Review of Expressway
Performance Comparison to IBM* DataPower XI50
An Open Policy Framework for Cross-vendor Integrated Governance
Enabling Integrated Governance for Policy Driven SOA
The XACML Enabled Gateway – The Entrance to a New SOA Ecosystem
Multi-Core Optimized Soft-Appliance
Xpath 2.0 - Application to Gateway Security
Accelerate SOA Processing with Intel SSE4.2 Instruction Sets
SOA Expressway
Visit Site Assets
Webinar Assets
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. Based on their perspective, they would be correct since V2 focused more heavily on operational processes rather than service lifecycle. With ITIL V3, the focus of the framework shifted toward what can only be accurately described as service-orientation.
A new JP Morgenthal’s post “The Busy Executive’s Service Oriented Architecture Reference Guide” is a great starting point for gaining a quick understanding of what SOA is without getting too deep into technology jargon and hype.
The Open Data Protocol (OData) specification opens up possibilities to a lot of interesting collaborative use-cases and scenarios. Some of which are highlighted by Douglas Purdy, Pablo Castro and Jon Udell.
Agile is the hand that works in the glove. SOA is the glove, the scope is enterprise wide. Most principles of SOA and Agile are not in conflict. When they are, they keep each other sane. Agile development without a clear vision of the goals and objectives of the company is futile. SOA without a clear vision how to make it real using agile development principles is a waste of time and money.
In this second article in the Resource-Oriented Architecture series, Brian Sletten discusses the benefits of REST, what constitutes a resource, associating metadata with a resource, the pitfalls of common models of resource metadata, SPARQL, RDF, expressing RDF facts, RDF triples, querying RDF, and sample RDF queries.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity to some basic concepts: enterprise, patterns, frameworks, architecture, SOA, development, architecture lifecycle, best practices, what they are and what the aren’t, emphasizing the role and importance of patterns.
Anne Thomas Manes, who pronounced SOA dead a year ago, talks about the reincarnation of SOA. She believes the old SOA had to die because it was too much focused on technology and products, while the new one, absolutely necessary for the new cloud computing era, will be focused on architecture, principles and practices.
In this interview from QCon San Francisco 2009, Don Box discusses the history of SOAP, XML, XML Schema, RELAX NG, SOAP and WSDL, REPL, opinions on REST, REST at Microsoft, coexistence of REST and WS-*, the M programming language, M and DSLs, M versus XML/XML Schema, Data as XML, and future plans for M and data modeling at Microsoft.
What is Data Grid computing? What makes it different from a database? Is a data grid always scalable? Is the cloud the next step? Cameron Purdy answered these questions and others during an InfoQ interview, and also gave some hints on how to build scalable grids and how to avoid horror stories.
Composite Software offers a new level of granularity when compared to SaaS (Software as a Service). Composite Software is about enabling "right-sourcing", i.e. move (or keep) arbitrary small or large elements of functionality wherever it is the most cost effective to operate them, not just entire systems. Economically, "right-sourcing" is far more efficient than "outsourcing" and SaaS. The goal of this book is start by understanding today’s software construction processes and technologies and explore why and how it should be evolved to support core composition mechanisms.
This book argues that for SOA to succeed we must move our thoughts away from the implementation technologies and towards the "what" of the business. Using a straight-forward, pictorially driven, methodology the book explains who to discover what the business services really are and how to construct an overall business service architecture.
