To be able to do anything useful, an ESB must be configured with all sorts of
parameters, from endpoint connection URIs to message transformation scripts
to content-based routing definitions. Moreover, ESBs like Mule can host
custom components, which will process messages and perform user-specific
actions on them.
Deploying a new version of an ESB configuration raises the question of
whether it will break anything. How can we build confidence that everything
will be just fine? If unit testing did it for standard software development,
what can it do in the realm of the ESB? Since ESBs are becoming increasingly
familiar in corporate IT, getting concrete answers is of interest to more and
more people.
This article details the testing strategies I employ for Mule ESB-driven... (more)
As software manifestos have started to proliferate these past months, I have
started to wonder what could be the root cause for their creation. Why would
thought leaders gather, assert a small set of values and shrink-wrap them as
a manifesto, calling for others to sign it? My feeling is that these
manifestos are the expression of a pushback on a particular aspect of
software development... (more)
If you wonder why is the Software Craftsmanship movement valuable, Calvin and
Hobbes have the answer for you:
© 1996 Bill Watterson
... (more)
I feel a little like George McFly, now...
Trees had to die to get us there by here we are: Mule in Action is now
treeware. And in case you missed it, the making of was here.
Enjoy the reading!
... (more)
You may have recently read two eponymic blog posts about this crucial
subject, so I won't give you ten more ways to suck at programming but just
one.
Here it is:
Don't critique your code.
If you never ever have a critique view of your code, you are on your way to
write software that sucks.
People who pair program may chuckle: they already have a continuous critique
process that helps produ... (more)