Services are the heart of a Service Oriented Architecture (SOA), but recently I've noticed a lack of understanding around the definition of service. We all know what a service is, even if we can't articulate it succinctly... (More)
Whether you are a newbie or an experienced java developer, Bostech has free resources and paid support to take you to ChainBuilder ESB Rock Star status in no time.
An economic downturn can quickly transform the dreamy ideology of Service Oriented Architecture into just an expensive IT diversion. With miles of rough economic road still ahead, it seems like some SOA initiatives are grinding to a halt as organizations wait for more bountiful times when they can invest. It's like our SOA strategy ran out of gas.
Reforms are ahead. You may be surprised that there are excellent low cost options to pump more functionality into your service-oriented architecture, including open source solutions, like ChainBuilder ESB. (More)
Host: "Welcome back to the game of Planning our Infrastructure. Last week our reigning champion bought into the pyramid of meta-data confusion and lost his position to play. Let's see how this week's contestant -- plans -- our -- infrastructure!"
Contestant: "Thanks Jack, I'll take 'Justifying to Management' for my career please."
Host: "And the answer is: ROI."
Contestant: "Hmmm, I'd like to improve the answer, Jack. I'd like to buy a vowel please. An E."
Host: "Certainly. And your new answer is: ROEI."
Contestant: "Ah yes, I'd like to solve the puzzle!"
Host: "In the form of a question..."
Contestant: "What is the technique to justify SOA development through the integration of legacy infrastructure?"
Well before Mr. Potato Head's fame in Disney's Toy Story epics, this spud stud was the everyday emodiment for making the dreaded words "some assembly required" a sought after adventure. The trademark potato body was the standard container and the add-on bits of eyes, lips and glasses were the components that plugged-in to creatively form your favorite "composite application".
Fast forward to real-life application development...
Whether considering a commercial license or an open source license, the corparate execuive has two basic business requirements before allowing any product into their production environment:
1. A warranty to guarantee that the product will run as documented, and
2. The obligation to fix issues based on some priority/release schedule.
These requirements are standard operating procedure for commercial licenses with ongoing maintenance, but not so for open source licenses. Open Source licenses are "as is" at best. This makes using open source software (without additional support terms) a risk in an enterprise production-level business environment.
Enter the open source Professional Subscripion add-on...
True, the development time and maintenance cost to manage diverse applications are reduced when business integration components are built on standards like Java Business Integration (JBI), but don't confuse the ease of using the standardized run-time components with the creation of those run-times. (More)
Remember the good old days? Our first connections across vast integration frontiers were on proprietary software. Like the Transcontinental Railroad, these original systems helped us trek the distance between disparate business points in order to share information. (More)
How does the decision to use a standard, like JBI, affect the future development value of the Enterprise Service Bus and its components? Let’s start with a generic ESB.
If I could imagine a three-dimensional model of an Enterprise Service Bus architecture, it might be a Lego building block structure. Components of an ESB are "plugged in” or “connected” so this image works for me. (More)