a large scale systems problem

Cheng · Post by **Cheng** » Thu Jun 26, 2008 6:10 pm

Balt:

when we started that sheah (around 2004) we had a look at the big players. business objects dropped out pretty soon, maybe they improved since then. at this time they were not convincing.

simple loading... well.... Smiley

Baltazar · Post by **Baltazar** » Wed Jul 02, 2008 8:50 am

i think by 2000 BO was still big player (or maybe we had a bias since it was a french compagny). After that i stopped looking at this subject much.

What i meant by simple loading is not about volumes/reliability but more about the complexity of the treatement to be done before loading. Informatica allows a lot of sorting/cleaning/aggregating of different source in the loading phase. It might be just cases were this is not necessary.

wolf0564 · Post by **wolf0564** » Wed Jul 02, 2008 1:57 pm

Nonius,

I've had the good fortune to design and build custom enterprise software for a variety of business types and industries. One thing that I have discovered is that there are many common issues and design challenges for this type of software, even in vastly different industries. In this article, I will share an architecture approach that has worked well for most of the projects in which I have participated. In future articles, I will give some practical tutorials for building a complex business system one step at a time.

Defining the Problem

Here are some of the characteristics that these types of business systems seem to have in common.

Many different types of users in disseminated locations: In a business setting, there are many different functions that people perform. For example, an IT professional, researcher, company executive, and customer may all have different tasks and needs, but at some point will all have to work together in a collaborative fashion. To make matters worse (or better), technologies like mobile phones, VPN, Wi-Fi, and video conferencing, offices are spreading these people out geographically.

Changing requirements: Businesses today are all about adapting to changing customer needs and trends. Software systems that do not adapt will die. It does not matter that we, as programmers, would like a nice steady target; it is not going to happen.

Nonius · Post by **Nonius** » Wed Jul 02, 2008 10:28 pm

what's the word for loser in russian, wolf?

wolf0564 · Post by **wolf0564** » Wed Jul 02, 2008 11:48 pm

i think you know it...