FAQ - Frequently Asked Questions

When working with our customers we tend to face the same challenges and questions several times. Hence the obvious thing to do is to start assembling a FAQ. In this section we will address the issues common to most implementations of enterprise architecture and SOA throughout the organizations we work with.

Topics to be covered in a very near future are:

• Data redundancy.
  In any organization data redundancy is an issue. The database guys tells us to avoid data redundancy however the SOA-guys tells us to build services as autonomous as possible - hence having data redundancy. Michael Andersen will discuss pro's, con's and hardcore experiences from several different approaches.
• Caching.
  Performance is a huge issue when implementing SOA. On one side we would like only to present updated data to the end users but on the other side we do not want to poll the data services all the time. What strategies do we have to choose from and what are the experiences?
• Autonomacy versus online.
  Some SOA strategies praises a high degree of autonomacy of a service meaning that one single service can survive when fellow services goes offline. Other SOA strategies aims for 24/7 availability of all services thus decreasing the need for implementing autonomacy. Both strategies have pro's and con's. We have experience using both that we would like to share.
• Ownership of processes and data.
  It is always a topic having to decide upon how you identify ownership of data and processes. In our experience only one strategy works here: ownership of data belongs to the IT department and ownership of processes belongs to the Line-of-Business (LOB) managers.

Stay tuned as the articles appears in this section.