This is the third of a three-part article looking at the area of interoperability and health information exchange (HIE) in the healthcare industry. In the first part, I intended to clearly articulate the key challenges and barriers to adoption faced by those looking to engage in HIE.
SOA
Vertical Applications of a SOA "soft appliance"
So far I have been posting the last week or so about how to apply a SOA "soft appliance" to overall scenarios like Federated SOA, SaaS, and Mainframe deployments. XML performance acceleration, in-line / on-the-wire security processing, and
Mainframe SOA
In many conversations I participate in regarding Service Oriented Architecture (SOA), part of the conversation oftens leads to "....how best can I incorporate my mainframe in the SOA architecture...". There are a number of mainframe SOA-enabling options, and in this post I will share my opinion on the application of a short-list of tried and true approaches.
Integrating SaaS to the Enterprise with SOA
Integrating the hot, new SaaS application into a company can often be a challenging undertaking. The SaaS application was acquired for a pressing departmental need, yet manually re-inputting and syncing key data like employee, vendor or supplier master directories is not practical. Manually coordinating a sale by the customer saying "yes" with a win recorded in the sales force automation tool yet hand crafting delivery instructions in the order module of the ERP is not really a sustainable business proces
SOA and SaaS ... What's the Difference?
This might sound odd to some of you reading this, but I am regularly asked the following question ... "What is the difference between SOA and SaaS?".
Given the acronym soup of the IT industry I am not surprised to get that question and expect to for some time to come. The simple answer is that:
Given the acronym soup of the IT industry I am not surprised to get that question and expect to for some time to come. The simple answer is that:
- Service Oriented Architecture (SOA) is a means of designing and building software. It is a manufacturing model.
Usage of a SOA "soft appliance" for Federated SOA
In my last several posts I have been sharing the concepts of a new product category I have been referring to as a SOA "soft appliance". Those posts have covered the origin of the idea, features, benefits and how is it similar to and different from other types of service-enabling infrastructure.
Going forward for a while, I plan on posting on the deployment architectures and usages of a SOA "soft appliance" platform like Intel SOA Expressway.
Going forward for a while, I plan on posting on the deployment architectures and usages of a SOA "soft appliance" platform like Intel SOA Expressway.
The differences between a hard and soft SOA appliance
In the last blog I wrote about the similarities and differences between a SOA "soft appliance" like Intel SOA Expressway and an ESB-based product. Two key questions often arise out of that discussion: (1) Why do I need a SOA appliance if I already have an ESB, and (2) Why is a "soft appliance" better than an easy-to-deploy, secure and high-performance hardware appliance?
Does a SOA “soft appliance” = an ESB
In my last post I covered some of the key features of a Service Oriented Architecture (SOA) “soft appliance” and how we have manifested those capabilities into a new platform called Intel SOA Expressway.
The capabilities of a SOA "soft appliance"
In my last blog post I wrote about the origin of the idea behind a new category of enterprise infrastructure which I referred to as a SOA "soft appliance". This post is about the key features and characteristics of a SOA "soft appliance" and how we have manifested those features in the Intel SOA Expressway platform.
The birth of a SOA “soft appliance”
A few years ago, we were facing some challenging scalability and costs issues with a key aspect of our enterprise infrastructure. Like many companies we dove head first in the use of XML and web services as a means to refresh a major enterprise application using the latest design patterns of n-tier distributed systems and SOA. Diligent development resulted in an architecture that worked as advertised; it was flexible, far easier to re-configure and re-purpose than its predecessor. That’s the good news and the usage followed.
Páginas
