Rethinking ESB

Oh boy, this speaker is not what I’d call engaging. Not good for first class of the day.
I mainly care about ESB for grabbing a single “thing” off the shelf and plugging it into much larger/broader applications we build.

This talk- focus on the API being simple, easy to learn, snap in, snap out. All great ideas, until you really need the bean to do something complex, e.g. plot a complex set of S-Curves for value management of a capital construction project, then a whole set of them. Sorry, I’m being snotty, but that’s the sort of real world stuff we run into and that API cannot be simple.

Here’s a nice point: when doing complex graphical output, give an option to view the data. I may have to run that by the line of business for their graphs. We sort of do this already! Yay.


Don’t wrap your business logic in code. Well, duh. Actually, I need to be careful here, having done that. But no longer! So, lesson to you- don’t wrap your business logic in code.

FACT: There will always be bugs (they said it, not me). So, be careful with your patch management.

FUN FACT (from Doug): Bugs are what happens when life is what happens when you are waiting around for something great to happen.