Posted by Viktor Grgic in the late afternoon: June 16th, 2008
Last week Viktor Grgic explained the Missing skills en this week we’ll continue with #2 – Unclear ownership / Project based funding
In the world of standalone applications, there is typically a clear sponsorship and ownership of an application. There is also a single project with one project manager. The systems could be small or big, but the pattern remains the same. Funding is based on a business case and can be easily defended.
In SOA world, the story is different. There are the usual projects, each having their own objectives and often reluctant to work on generic services or enterprise components. If the ownership and funding for these components and aspects are unclear then chances are high that nothing happens on enterprise level or that it’s not according to enterprise architecture or nobody feels responsible when things on enterprise level go wrong (e.g. security).
Several projects working together is not a bad situation, but there should also be a SOA steering committee and SOA competence center well funded and supported by company board.
(more…)
Posted by Viktor Grgic in the early morning: June 9th, 2008
Last week Gero Vermaas explained the Incorrectly Applied CDM en this week we’ll continue with #3 – Missing skills
Just like any other paradigm, a level of new knowledge and experience is required. Unfortunately, SOA requires lots of new knowledge and experience. It requires a different way of thinking of more or less everyone involved. People are used to closed environments on both organisational and technical level; largely well protected from influences and unwanted dependencies with the outside world. It’s all in their area of influence which makes achieving short term results relatively easy. I’m referring to silo applications where the world is complicated enough. From their view, SOA makes things even more complex. There should be awareness that there is lack of knowledge, experience and attitude and something should be done about this first. There is no real solution, except for the obvious one: educate everyone involved. Also, agile methodologies have proven to be effective in building up knowledge and experience.
(more…)
Posted by Gero Vermaas mid-morning: June 2nd, 2008
Last week Vincent explained the BDUF Pitfall en this week we’ll continue with #4: Incorrectly applied Canonical Data Model (CDM).
CDM is one of the silver bullets often fired in SOA projects. It should address miscommunication, ease integration and reduce integration costs. It surely can facilitate all of this, but attempts to use a CDM can also turn your SOA project into an endless discussion because one attempts to cover too much, because of a lack of alignment with business and because of a lack of design principles.
(more…)
Posted by Vincent Partington in the early evening: May 26th, 2008
Last week we discussed #6 - which means we’ve now passed the halfway point of SOA Pitfall countdown! Let’s quickly move on to #5.
Like the Not Invented Here syndrome we discussed earlier, Big Design Up Front (BDUF) is something not only witnessed within the realm of SOA. However, where the NIH syndrome is generally accepted to be a bad thing, things are not that simple when it comes to BDUF.
Posted by Rik de Groot late at night: May 19th, 2008
After discussing #7: Incorrect granularity of services , let’s move on to #6.
In organizations data and functionality/processes are often fragmented, but are needed centrally. What are the causes of this fragmentation. Does a SOA solve this complexity automatically? Most companies start with a SOA and are confronted with this complexity during the implementation of the SOA.
(more…)
Posted by Gero Vermaas at around evening time: May 12th, 2008
After discussing #8: Security, let’s move on to #7.
Incorrect granularity could mean that a service covers too much functionality or too little functionality. Incorrect granularity of services in your SOA can lead to bad performance, low reuse possibilities, leaky abstractions and services without added business value. . Common causes for this are bottom-up and/or top-down design and taking a too narrow perspective (project instead of company scope). In this blog we’ll first take a closer look at the previously mentioned symptoms and their causes. And then we’ll explain why the solution lies in taking a business perspective when designing services.
(more…)
Posted by Mischa Dasberg in the early evening: May 10th, 2008
Today was the last day of the JavaOne Conference. We came to the point when a lot of OutOfMemoryErrors where thrown. We just managed to squeeze in the last sessions.
Today’s keynote was all about toys. The guys from the Netbeans team showed some new features such as a JavaScript editor (which contains code completion), Sentilla showed there small sensor thingies, which you can program to gather information, such as acceleration, temperature etc.., LiveScribe showed there very cool pen and lots more.
Today’s topic included:
- User Experience
- SOA
- Semantic Web
Posted by Erik Jan de Wit in the early morning: May 9th, 2008
Today was the third day of the conference. Another couple of hours to go and then it is all over again. The fatigue is kicking in, and we’re starting to run on reserve power. The topics of today included:
- Mylyn
- Groovy
- Semantic Web
- SOA
- OSGi
Posted by Jeroen van Erp mid-morning: May 8th, 2008
Today was the second day of the JavaOne 2008. Besides doing a lot of chatting in the JavaOne pavillion, and visiting all the cool parties this night, we also went to a number of sessions. Also today the NLJug had the James Gosling meeting we won for being the biggest JUG out here. After a long day of work, we finally had time to relax at the Adobe party and at the SDN party.
Todays topics included:
- Closures
- JavaFx, Groovy and Google Android
- Swing GUI testing
- Scripting
Posted by Erik Jan de Wit in the early morning: May 7th, 2008
We’re here at the JavaOne Conference in San Francisco. Today the JavaOne conference kicked off. The coming 75 hours are packed with Java, Java and more Java! To give an impression of what we’re seeing here, we will provide you with a daily blog.
Today’s higlights included:
- SCA (service component architecure)
- GlassFish
- JavaFX
- Effective Java and defective Java