A few people who have been reading my blog and this column, and listening to
my podcast, as well as reading other SOA blogs and articles, have become a
bit confused pertaining to the notions of:
SOA Reference Model(s) SOA Reference Architecture(s) And how all of this
works and plays with Enterprise Architecture I spent a few hours of my
weekend attempting to research and define these concepts a bit better, in
essence, taking everyone's opinions and normalizing them so they make better
sense. What I found were many of the same notions, defined differently, but
all attempting to solve the same problems. Seems to be a common theme within
the world of SOA, but I digress.
Indeed, there are many definitions for the above concepts (not those terms
specifically) that are now being defined by guys like me, standards
organizations such as OASIS and the Open Group, and vendors ... (more)
As you remember from Part 1 of this article series, there are 17 steps to
Assess the business. Assess the culture. Assess the value. Understand your
data. Understand your services. Understand your processes. Understand the
cloud resources. Identify candidate data. Identify candidate services.
Identify candidate processes. Create a governance strategy. Create a security
strategy. Bind candidate services to data and processes. Relocate services,
processes, and information. Implement security. Implement governance.
We covered the first ... (more)
Fundamentally, Enterprise Application Integration (EAI) is about loosely
coupling applications and data stores together to solve intraenterprise
business problems. Its strength is facilitating the free flow of information
from any system to any other system, one-to-one or many-to-many, with each of
those systems gaining access to perfect external information in real time.
EAI typically integrates ERP packages, such as SAP, PeopleSoft, and Baan, in
addition to customer relationship management (CRM) packages, databases, and
older mainframe systems. EAI also allows organizations to e... (more)
As we discussed last month, performance is often an afterthought when
building new systems, including SOAs. We're finding that services and SOAs
fall victim to this oversight as well. Indeed, there is a right way and a
wrong way to design a service and an SOA. Also, there are things that are out
of your control that you must consider during your design.
This month let's continue our discussion with some important performance
concepts, including how to create a performance model, as well as more
service and SOA design tips when considering performance.
Creation of a Performance Mo... (more)
Truth be told, traditional approaches to integration are really about keeping
persistence at the points, within the source or target systems, and
replicating data as needed. However with the use of true services, there is a
clear advantage in keeping some persistence at a central-tier, for any number
of legitimate reasons. Let's explore this in the context of an SOA.
Indeed, as we become better at building services we need to understand the
infrastructure that the services will leverage, including orchestration,
security, management, and data, and where those functions need to res... (more)