Top 10 SOA Pitfalls: #4 – Incorrectly applied Canonical Data Model
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...)
Top 10 SOA Pitfalls: #5 – Big Design Up Front
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.
Top 10 SOA Pitfalls: #6 – SOA does not solve complexity automatically
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...)
Top 10 SOA Pitfalls: #7 – Incorrect granularity of services
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...)
JavaOne 2008 Day Four: That’s a wrap!
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
JavaOne 2008 Day Three
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
JavaOne 2008 Day Two
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
JavaOne 2008 Day One
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
Top 10 SOA Pitfalls: #8 – Security
Posted by Viktor Grgic in the early evening: May 5th, 2008
Last week Rik de Groot published the #9: Versioning. This week it's time for #8.
SOA security is like having a well-protected Middle Ages city, but at the same time asking citizens to permit many more people from inside and outside the city into their homes. They would really have hard time properly securing their belongings.
Introduction of SOA should be accompanied by at least SPRINT business impact assessment of security vulnerabilities (confidentiality, data integrity and availability) and definition of required measures. Introduction of SOA also requires rethinking your security architecture.
(more...)
Top 10 SOA Pitfalls: #9 – Versioning
Posted by Rik de Groot just before lunchtime: April 29th, 2008
Last week we started the Top 10 SOA Pitfalls countdown with #10: NIH syndrome. This week it's time for #9.
Version mismatch is one of the growing pains of a SOA. A SOA starts simple, but after a while new versions of services will appear and the complexity will grow. Good life cycle management and supporting tools will help you to control the complexity.
(more...)
Archives
Xebia Sites
Categories
- Java (282)
- Agile (109)
- General (50)
- Testing (42)
- Performance (42)
- Hibernate (36)
- Scrum (33)
- Podcast (31)
- Architecture (31)
- Spring (28)
- SOA (24)
- Maven (22)
- Project Management (22)
- Middleware (23)
- Deployment (14)
- Flex (17)
- JPA (17)
- Eclipse (15)
- Xebia Labs (15)
- Quality Assurance (14)