ColinPaice Published on 26/07/2017 / Updated on 28/07/2017
Warning long append, but full of good information…
I was helping a customer with “an MQ performance problem” where application queues were filling up. I asked for an architecture diagram and other information. They did not have this documented and Joe spent many minutes drawing a complex picture on the white board: blue boxes for virtual machines, green boxes for MQ, red lines for data flow etc. I took a photo my mobile phone for reference. I was disappointed that Joe who was responsible for the business application, knew so little about it. I felt like tying him into a chair, like in the old movies, shining a light in his face and saying “tell me all you know”… but I took the easier solution of expressing my expectations of a business architect over lunch.
I expected each major business application to have a document (a presentation is fine) containing enough information for people who are outside the application to be able to understand it
And the reason for the “MQ performance problem ” was at peak time each database requests to the remote data base took over half a second – and there were 12 requests per transaction – so 6 seconds per transaction!”
The next topic in this theme is What’s the difference between a C programmer and an application programmer?