tom-mccuch.blogspot.com
Tom's Code: Agile SOA - Part II
http://tom-mccuch.blogspot.com/2008/12/agile-soa-part-ii.html
Thursday, December 18, 2008. Agile SOA - Part II. After establishing the forces behind the paradigm shift of Service Oriented Architecture (SOA) in Part I. So why is Agile the best method to use when approaching the evolutionary characteristic that is the chief concern of SOA? 160; "The first value is communication. Problems with projects can invariably be traced back to somebody not talking to somebody else about something important.". An Agile approach to SOA is all about promoting feedback at both des...
tom-mccuch.blogspot.com
Tom's Code: December 2008
http://tom-mccuch.blogspot.com/2008_12_01_archive.html
Thursday, December 18, 2008. Agile SOA - Part II. After establishing the forces behind the paradigm shift of Service Oriented Architecture (SOA) in Part I. So why is Agile the best method to use when approaching the evolutionary characteristic that is the chief concern of SOA? 160; "The first value is communication. Problems with projects can invariably be traced back to somebody not talking to somebody else about something important.". An Agile approach to SOA is all about promoting feedback at both des...
tom-mccuch.blogspot.com
Tom's Code: Agile SOA - Part III
http://tom-mccuch.blogspot.com/2008/12/agile-soa-part-iii.html
Saturday, June 20, 2009. Agile SOA - Part III. This is the third and final blog in this series. In. I opened with the thought that the real challenge of SOA is changing the way you look at the IT investment of your business to be more from the perspective of software architecture. In. A business' enterprise architecture is a. Think of a football play being viewed from an overhead camera with primary and optional flows for the different players on the field. Episodes should be linked together in a linear-...
tom-mccuch.blogspot.com
Tom's Code: Agile SOA - Part I
http://tom-mccuch.blogspot.com/2008/10/agile-soa-part-i.html
Saturday, October 4, 2008. Agile SOA - Part I. The real challenge of adopting SOA is to change the way you and your organization think about enterprise architecture, not to change your information technology infrastructure yet again to continue the cold war-like arm's race against your competitors the software vendors have sold you on (at a great profit to them, I might add). Why is SOA such a challenge? So if IT departments are no longer managing hardware and networks for the business, what will that le...
tom-mccuch.blogspot.com
Tom's Code: October 2008
http://tom-mccuch.blogspot.com/2008_10_01_archive.html
Saturday, October 4, 2008. Agile SOA - Part I. The real challenge of adopting SOA is to change the way you and your organization think about enterprise architecture, not to change your information technology infrastructure yet again to continue the cold war-like arm's race against your competitors the software vendors have sold you on (at a great profit to them, I might add). Why is SOA such a challenge? So if IT departments are no longer managing hardware and networks for the business, what will that le...
tom-mccuch.blogspot.com
Tom's Code: June 2009
http://tom-mccuch.blogspot.com/2009_06_01_archive.html
Saturday, June 20, 2009. Agile SOA - Part III. This is the third and final blog in this series. In. I opened with the thought that the real challenge of SOA is changing the way you look at the IT investment of your business to be more from the perspective of software architecture. In. A business' enterprise architecture is a. Think of a football play being viewed from an overhead camera with primary and optional flows for the different players on the field. Episodes should be linked together in a linear-...
tom-mccuch.blogspot.com
Tom's Code: June 2008
http://tom-mccuch.blogspot.com/2008_06_01_archive.html
Friday, June 20, 2008. The number one job of the Architect in an IT project is to manage requirements. The Architect is in the only position within the enterprise to look deep enough into the business and deep enough into the technology to understand the translation of the requirements between the two. It is the Architect who is on the front-lines of business-IT alignment, and people should look no further when IT seems "out of touch" with the business. The second half of the requirements analysis proces...
tom-mccuch.blogspot.com
Tom's Code: August 2010
http://tom-mccuch.blogspot.com/2010_08_01_archive.html
Sunday, August 8, 2010. The cloud (whether it be private, public, or hybrid) allows for massively parallel, horizontal scale-out architectures. This is radically different from the centralized, vertical scale-up architectures that have evolved from the original success of big-RDBMS on physical hardware. So it has always been, and will always be . the new cloud integration deployment model must start with the data. High-write applications do not scale well horizontally on today's RDBMS solutions. This...
tom-mccuch.blogspot.com
Tom's Code: Cloud Integration Architecture
http://tom-mccuch.blogspot.com/2009/11/cloud-integration-architecture.html
Sunday, August 8, 2010. The cloud (whether it be private, public, or hybrid) allows for massively parallel, horizontal scale-out architectures. This is radically different from the centralized, vertical scale-up architectures that have evolved from the original success of big-RDBMS on physical hardware. So it has always been, and will always be . the new cloud integration deployment model must start with the data. High-write applications do not scale well horizontally on today's RDBMS solutions. This...
tom-mccuch.blogspot.com
Tom's Code: Revisiting Requirements Management
http://tom-mccuch.blogspot.com/2008/06/revisiting-requirements-management.html
Friday, June 20, 2008. The number one job of the Architect in an IT project is to manage requirements. The Architect is in the only position within the enterprise to look deep enough into the business and deep enough into the technology to understand the translation of the requirements between the two. It is the Architect who is on the front-lines of business-IT alignment, and people should look no further when IT seems "out of touch" with the business. The second half of the requirements analysis proces...
