SOA Doesn't Work In A Disjointed Enterprise

 What with all the to-ing and fro-ing and huffing and puffing and screaming and shouting (and biting and gouging) that goes on in most business IT organisations, it can be all-too-easy to forget that we are ultimately all working on different parts of the same system.

By arbitrarily breaking software into chunks - projects, applications, components, services - and then organising ourselves around those chunks, we can end up losing sight of the bigger picture. And that can lead to situations where the left hand doesn't know what the right hand is doing. Which can, in turn, lead to duplication, disarray and conflicting goals.

This can often be a symptom of a disjointed enterprise, where the silo mentality prevails from department to department and business function to business function. It's no wonder, in those situations, that the team building the order processing web application fails to collaborate and co-operate with the team working on the stock management system, if the business people working in order processing and stock control don't speak much, either.

And the last thing that any IT or business manager should be contemplating when they have a disjointed enterprise is any attempt at service-oriented architecture. If you cannot remove the duplication from your business, then you have little or no hope of removing it from your business IT systems.

Comments

Post a Comment

Popular posts from this blog

83% of Developers Suffer from Burnout

  The Covid-19 pandemic has led to a significant increase in burnout among software developers. According to a study conducted by Haystack Analytics , a firm that focuses on engineer productivity, 83% of software developers experience burnout. The primary causes cited for this exhaustion are excessive workloads (47%), inefficiencies in processes (31%), and ambiguity in objectives and targets (29%). Most areas of human activity have had to rely on technology to remain productive during the coronavirus pandemic, including implementing telework. For the most part, businesses saw significant productivity gains in 2020, directly related to the widespread use of telework. Some are even anticipating a total productivity gain of 17% over the next two to three years. In addition, through telework, 88% have realized savings on real estate expenses over the past year. Similarly, 92% expect further savings in the next two to three years. However, has maintaining or increasing productiv
Read more

Lessons for Young Programmers: What You Need to Know

 In the past 7.5 years I have supervised over a dozen programming interns and have seen hundreds of portfolios of students and graduates. In almost all of those I saw the same things that they needed to learn. One might expect that I think they need to learn specific techniques, algorithms or math, or other forms of specific knowledge. And of course they do, but in my opinion that is never the main thing. The main thing they need to learn is self discipline. The discipline to always write the clearest code you can, the discipline to refactor code if it becomes muddy through changes later in development, the discipline to remove unused code and add comments. Most of the time I spend supervising programming interns is spent on these topics. Not on explaining advanced technologies or the details of our engine, but on making them write better code in general. I always ask applicants what they think is important in being a good programmer and they usually answer that code should be cle
Read more

Hell Is Other Architects

 One of the thornier facets of being a "design authority" is that you are invariably called upon to make a professional assessment of other peoples' designs. (In a process, often compared to pulling fingernails, known as a "design review"). A team of developers might get a little precious about someone like me asking awkward questions about the design of their code, but that's a walk in the park compared to reviewing code that's been architected (by an architect, no less…) Some architects will defend their design decisions to the death, and quite often will use every intellectual and political weapon in their arsenal to repel hostile agressors like myself - godless heathens who have the nerve to saunter nonchalontly into their empires and say things like "should the data access code be in the same classes as the business logic?" and "shouldn't that class that everything else depends on be a bit more abstract?" and other g
Read more