Welcome!

Microservices Expo Authors: Liz McMillan, Pat Romanski, Carmen Gonzalez, Elizabeth White, Jason Bloomberg

Related Topics: Microservices Expo, Containers Expo Blog

Microservices Expo: Blog Feed Post

IT Architecture as Taught by Monty Python

Before building your design you need to know what your mission requirements are

One of my friends and mentors, Bill Vass, has consistently advised IT professionals to understand, respect and use the power of well-formed IT architecture.  Bill has often reminded me and others that architecture is design.  If you have poor design, or if you have good design that is ignored, then the architecture is worthless or even counter productive.  If you have good, actionable design that is focused on mission needs and used by enterprise decision-makers then IT is better able to deliver workable solutions.  Bill also emphasizes that well done architecture begins with the end in mind.

That last point means, that before building your design you need to know what your mission requirements are.  And you need a good relationship with your customers and how they serve the mission.

If there was ever any doubt of that, I’d like to point out a great example highlighted by Monty Python in a skit named… “Architect Sketch.” In it John Cleese plays an architect who seems to have created his design without an approved business architecture. The result is a design that does not meet the intended mission needs. (In the same sketch, Eric Idle, seems to have a design that reflects mission needs, but shows signs that it might not be executable).

The sketch is a great way to drive home many lessons in IT architecture, don’t you think?  Here are a few that come to mind:

  • IT customers should very clearly spell out the requirements that need solving (by the way, most are are not very good at this)
  • IT architects must ensure they are designing to mission needs
  • Sometimes poor technical designs are picked because they are the only thing that comes close to meeting the mission
  • Sometimes designs are picked because of relationships

If you are a customer of IT is is your duty to describe requirements in clear, understandable ways so the IT architects have a chance of designing the right solution.

If you are an IT architect you have a duty to ensure you are designing things to meet mission needs.  You don’t design something just because that is what you are good at (John Cleese’s character said “You see I mainly design slaughter houses.”).   And if you design something that customers reject in design review, don’t do a Cleese on them.  Although he does have a way with words when it comes to pushing back on user concerns:

“Well, of course, this is just the sort of blinkered philistine pig-ignorance I’ve come to expect from you non-creative garbage. You sit there on your loathsome spotty behinds squeezing blackheads, not caring a tinker’s cuss for the struggling artist. You excrement, you whining hypocritical toadies with your colour TV sets and your Tony Jacklin golf clubs and your bleeding masonic secret handshakes.”

(That kind of in-your-face interaction with customers is probably not conducive to a productive, healthy, long-term relationship with your customers).

Which raises another point this skit humorously highlights.  In the end, the customer choose the poor technical design over the good one because it was closer to meeting the mission, and because the architect had a relationship with the customer, as evidenced by the well executed masonic secret handshake.

Lesson overall: Good enterprise IT is always about people and the mission.  When enterprise IT is designed without a good understanding of the mission, disaster can result.

Related posts:

  1. Intel’s Next Generation Chip Architecture
  2. A Recap of the 2009 DoDIIS Worldwide Conference
  3. ITIL for CTOs

Read the original blog entry...

More Stories By Bob Gourley

Bob Gourley writes on enterprise IT. He is a founder of Crucial Point and publisher of CTOvision.com

Microservices Articles
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
"NetApp's vision is how we help organizations manage data - delivering the right data in the right place, in the right time, to the people who need it, and doing it agnostic to what the platform is," explained Josh Atwell, Developer Advocate for NetApp, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
The Jevons Paradox suggests that when technological advances increase efficiency of a resource, it results in an overall increase in consumption. Writing on the increased use of coal as a result of technological improvements, 19th-century economist William Stanley Jevons found that these improvements led to the development of new ways to utilize coal. In his session at 19th Cloud Expo, Mark Thiele, Chief Strategy Officer for Apcera, compared the Jevons Paradox to modern-day enterprise IT, examin...
In his session at 20th Cloud Expo, Mike Johnston, an infrastructure engineer at Supergiant.io, discussed how to use Kubernetes to set up a SaaS infrastructure for your business. Mike Johnston is an infrastructure engineer at Supergiant.io with over 12 years of experience designing, deploying, and maintaining server and workstation infrastructure at all scales. He has experience with brick and mortar data centers as well as cloud providers like Digital Ocean, Amazon Web Services, and Rackspace. H...
Skeuomorphism usually means retaining existing design cues in something new that doesn’t actually need them. However, the concept of skeuomorphism can be thought of as relating more broadly to applying existing patterns to new technologies that, in fact, cry out for new approaches. In his session at DevOps Summit, Gordon Haff, Senior Cloud Strategy Marketing and Evangelism Manager at Red Hat, will discuss why containers should be paired with new architectural practices such as microservices ra...
In his session at 20th Cloud Expo, Scott Davis, CTO of Embotics, discussed how automation can provide the dynamic management required to cost-effectively deliver microservices and container solutions at scale. He also discussed how flexible automation is the key to effectively bridging and seamlessly coordinating both IT and developer needs for component orchestration across disparate clouds – an increasingly important requirement at today’s multi-cloud enterprise.
The Software Defined Data Center (SDDC), which enables organizations to seamlessly run in a hybrid cloud model (public + private cloud), is here to stay. IDC estimates that the software-defined networking market will be valued at $3.7 billion by 2016. Security is a key component and benefit of the SDDC, and offers an opportunity to build security 'from the ground up' and weave it into the environment from day one. In his session at 16th Cloud Expo, Reuven Harrison, CTO and Co-Founder of Tufin, ...
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In their Day 3 Keynote at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, and Mark Lav...
Many organizations are now looking to DevOps maturity models to gauge their DevOps adoption and compare their maturity to their peers. However, as enterprise organizations rush to adopt DevOps, moving past experimentation to embrace it at scale, they are in danger of falling into the trap that they have fallen into time and time again. Unfortunately, we've seen this movie before, and we know how it ends: badly.
TCP (Transmission Control Protocol) is a common and reliable transmission protocol on the Internet. TCP was introduced in the 70s by Stanford University for US Defense to establish connectivity between distributed systems to maintain a backup of defense information. At the time, TCP was introduced to communicate amongst a selected set of devices for a smaller dataset over shorter distances. As the Internet evolved, however, the number of applications and users, and the types of data accessed and...