An enterprise architect has to think about things other than just the technology, and that’s where it can often get confusing. Although they’re sometimes doing non-technical work – trying to figure what are the right sets of tools, technologies, and platforms that are going to this organization's needs – there is an important opportunity to learn through those collective discussions. It's critical for enterprise architects to collaborate with application architects and solution architects to become better informed. However, from a patterns and framework perspective, enterprise architects’ should know where they fit into the larger enterprise design patterns and where they can be used and leveraged. This back and forth collaboration needs to exists and must be centered on what's new to avoid confusion.
Architectural Governance Pendulum
As middle-tier technologies have shifted from monolithic tools and frameworks to more lightweight, containerized, and server-less environments, a similar movement has also occurred in enterprise architecture. Formally centralized enterprise architects have now migrated to be distributed architects working within functional teams to alleviate pain points; however, it is now evident that we have traded one set of problems within the old way for a new set of problems within the new way.
So where does enterprise architecture perform best within an organization? In this podcast, our technical thought leaders discuss the pain points and dysfunction of both approaches in the new and old way and suggest methods for taking a middle pendulum approach to achieve the best results.