Thoughts

10g (1) 11c (1) 11g (5) 12c (4) 3.0 (1) ApEx (4) Cloud (11) database (10) DBA (1) EBR (1) EC2 (2) education (3) EOUC (1) ExaData (1) F2F (1) Forms (7) java (1) language (2) memorabilia (2) Metalink vs MOS (4) multi-cultural (4) on-line communities (1) oracle (7) performance (5) projects (1) reciproke (1) Reports (2) RUP (1) sales (2) services (5) silence (1) SOA (3) SQL Server (3) standards (6) Sun (1) support (6) W8 (1) WebLogic Server (5)

Wednesday, September 17, 2008

SOA and a conductor

I saw a conductor today on the very good and informative channel mezzo. He just showed the orchestra in short moves how to play a very complex piece.

I started to think about a word in the SOA realm. Orchestration.

Orchestration.

The conducter of a choir or an ensemble only shows the path to what there is to come. It relies on the fact that every single intstrumentalist knows what to do. And the pace is the key to success. The SAME PACE. The value in time of the notes have to be coordinated.

The pitch have to be coordinated, and the instrumentalists tune in before the piece starts. They even tend to tune in their instruments during the concert in some intermission or between parts in a mass, or a symphony.

Compare that situation with a software business installment with different web services, different platforms and different hardware. Trying to interact.

I mean, hey! Come on! It puts demands on the internal affairs of a business. The internal processes have to be defined before you can outsource anything, before you can web-servicify any part of any application.

In order to play the symphony every single part, every single trombone player, every single bass player and the little tiny flute has to be in synch. Has to agree on the tempo, on the pitch.

This is the case in software engineering too. You have to decide upon a standard platform, a common way of working and a culture that encourage knowledge exchange.

Friday, September 12, 2008

SOA and the business

There are voices in our IT world saying that we have to go for low cost countries, we will earn money. Well it is not a matter of subtraction, that is for sure.

Cultural differences in the ways of working is making the profit not as profitable as it seems from the start. Note that there seldom - but it could be as well - lack of knowledgeable people in other parts of the world, it is just that the ways of working differ.
That gap has to be acknowledged and adressed.

If you have a business where you want to outsource some part of your internal business. That decision will put several requirements upon your inner process structure and documentation. It essentially say "you have to define them". That is the first obstacle. Are there heroes out there making the business run and you do not know it? Yes, probably. There is always a "phone Mr FixIt and he will take care of you" or "send a fax to Mrs IgoFigure and the order will be in place when you want it".

So you go document.

Then you go standardise the inner it landscape. That is the next step, of course every single person has to agree upon the technical road taken. Actually, we all sort of just accept the fact that we shall use Word as a word processing tool. Thou shalt use Word. OK, we say, we do not go in our chamber and make up a new word proceessing software. Do we? No, if we do anything we look for open source alternatives. That is a good thing. Or we look for software on the shelf solutions.

A SOA concept for your company could be the soulution and lift everyone. But it is a cumbersome task to achieve tru outsourcing capability. And it starts with Your company, not the outsourcing company.