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
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…)
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…)
Posted by Vincent Partington in the early morning: April 23rd, 2008
At Xebia we are involved in quite a number of Service Oriented Architecture (SOA) projects, from small to big. In that capacity we see a lot of good stuff happening, but we also encounter quite a number of projects that have stalled or failed.
To share our experiences with these SOA projects, Gero Vermaas, Viktor Grgic, Rik de Groot, and myself have decided to write a series of blogs about the most annoying pitfalls of SOA. Each week we will be publishing one item from the list. This way we hope to spread awareness of these dangers and also provide you with a checklist of what to watch out for. Of course, as is always the case with these kinds of lists, they are not complete and not all the issues are as absolute as the title may imply. YMMV!
The first item we want to discuss is the Not Invented Here Syndrome (NIH). Of course this is something that can be witnessed in more areas of IT, but in a SOA context it actually applies on two different levels.
(more…)
Posted by Viktor Grgic in the early afternoon: January 16th, 2008
It is always about well-defined requirements stupid. 
Building or choosing out-of-the-box software products like an ESB within the company’s SOA strategy can be very well supported by a number of requirements distilled from the QUINT2 ISO model:
Functionality: Suitability, Interoperability, Compliance, Security, Traceability
Usability: Operability, Customisability
Efficiency: Time Behaviour
Maintainability: Testability, Manageability, Reusability
Portability: Adaptability, Replaceability
This is the selection from the complete QUINT2 model. It does not mean that other requirements are not important, but usually less than these. If you fill out these requirements properly, which is still a daunting task, then you will have done pretty good requirements gathering. Besides these aspects, there are also security requirements: availability, integrity and confidentiality which should always be considered.
Posted by Gero Vermaas at around evening time: June 6th, 2007
In the previous episodes in this series we started from a high level Java in the Telecommunications industry, zoomed in on Telemanagement Forum and the basics of OSS/J, described the basics of the Order Management API and now we’ll discuss why the Order Management API fits perfectly in an Service Oriented Architecture (SOA). Why is this a relevant question? Virtually any organization does with order management in one way or another and many organizations are currently evaluating or realizing SOAs. Reason enough to check if the Order Management API fits in an SOA.