Design Patterns
Design patterns is a software engineering concept where abstract solutions to abstract but common problems are described, and used so that solutions to problems are consistent and dead ends are avoided.
Basically, there is an approach to solving a problem that is successful. Following the pattern creates a solution that works and is stable.
There has been “much ado” about this relatively new tool in software development, but its practical applications are result driven and show that this is a tool that is here to stay. As integration Engineers we have a slightly different bent on software development, but we need to know how application developers think and more importantly, how they talk.
I recently came across a book on design patterns written by Steve Holzner. Its called “Design Patterns – Simply” and can be found here. His site is also pretty good and explaining the very basics of what design patterns are and what they mean.
Now, if we just had a design patterns for integration engineers. Maybe a book called “Integration Patterns” or something…..
Wednesday, May 12th, 2010
To paraphrase a quote from Frank Herbert’s Dune, “The Data must flow.” And in the same sense that spice was the life blood of Arakis, the flow of data is the life blood of any e-commerce integration. In the past I have talked about how
In the news,
Looking for innovation in Supply Chains isn’t hard to do, and it can have a great impact on the efficiency and therefore profitability of a business and market. One place that greatly impacts the success of an integration is the desire to build something new and sexy. I rant sometimes about companies or development teams I have seen go down this path to their own detriment.