Your web browser is out of date. Update your browser for more security, speed and the best experience on this site.

Update your browser
CapTech Home Page

CapTech Trends Podcast Series

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.

View the Transcript

Subscribe to the CapTech Trends Podcast Series

Apple Podcasts

Spotify

Google Podcasts

Pocket Casts

Episode Highlights

COLLABORATION IS ESSENTIAL

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.

REUSE IS ATTAINABLE

Many see reuse as the holy grail. Something that is right in front of us now is the interoperability of services you have - the ability to get information in and out. While interoperability is the next step for many and reuse may still be years down the road, if you’re currently not thinking about reuse, then that timeline will continue to be pushed back. Reuse must be considered and prioritized now. What are those different ways of thinking about reuse that still enables the organization to accomplish its goals, while also allowing reuse to be more attainable in a the near future?

Matt Comer

Matt Comer

Fellow, Systems Integration

Matt is focused on the architecture, design, and construction of distributed, integrated systems in the enterprise and web environments. He has extensive experience in Java development, including advanced experience in multi-threaded design, encryption, Spring, Seam, EJB3, and other frameworks.

LinkedIn Envelope
William Klos

William Klos

Fellow, Systems Integration

Bill has been delivering business and technology solutions as a consultant in Ohio for over 25 years. His focus has traditionally been on working with clients to deliver solid technology solutions rooted in innovative approaches. Approaches that not only address the diverse environments of his clients but also scale and evolve to meet his clients’ changing business needs.

LinkedIn Envelope