Jump to Navigation

An Easy Path To SOA Modernization

Thu, 10/27/2011 - 09:31 — mbouchard

Problem Overview:
The challenge I see many enterprises facing today can best be described as a balancing act between two competing forces.

CIO Outlook: The Enterprise Management Pattern

Thu, 04/28/2011 - 14:53 — mbouchard
Problem
Many of the enterprises I see today have a collection of stove-pipe systems integrated through a series of point to point integrations using technologies ranging from database replication and materialized views to MQ Series messages and SOAP web service calls.

Why Do We SCRUM?

Sun, 03/13/2011 - 16:10 — mbouchard

The Buzz Words...
These days SCRUM and Agile processes seem to be the new buzz words in the IT Industry. Everyone is talking about daily stand-ups, SCRUM Masters, Product Owners, and iterative development. However - all of this talk reminds me of the buzz around Object Oriented Programming back in the early 1990s.

Back then - I was doing OOP and was constantly involved in the interview process for additional developers. One basic question I would ask: "What is the advantage of OOP? Why do we do Object Oriented Programming?" Only 5% of the interviewees would have any sort of reasonable response. If we ask today's typical developer "Why we do SCRUM?", I think we would find similar responses.

Sequence Number Anti-Pattern

Sat, 03/12/2011 - 22:55 — mbouchard

Realization of a Problem
I recently had not one - but two debates with highly educated and respected veterans of the IT industry on this topic. One is a boutique consulting firm whom I've always respected because of the work they've done over the past 15 years, and the other a co-worker who is very good at their area of expertise. I came to the realization that this topic needed more attention. This is something that I always thought was intuitively obvious to anyone doing distributed systems - and many of us have been doing distributed systems for a long time now - but I've realized that smart people still don't seem to get it.

Designers and Architects that implement sequence numbers into their designs (such as primary keys for database tables) are making decisions that can cause irreparable harm to their systems and their ability to support those systems effectively in the future. It is analogous to a Java programmer calling a GOTO statement, writing their own linked list, or doing a CORBA system fined-grained and wondering why they have performance issues.

Subscribe to Enterprise Software Solutions, Inc. RSS


Main menu 2

by Dr. Radut.