In a previous article titled A Methodology for a Transparent and Traceable Solution Architecture, I outlined a methodology an architect can use to create a transparent and traceable solution architecture. This article will expand on that and will use a […]
Architecture
A Methodology for a Transparent and Traceable Solution Architecture
As a Solution Architect, you intersect with all entities that have a vested interest in the solution, including, business sponsors and associated business team, business managers, and business analysts to different degrees. As being responsible and accountable to get the […]
From Assumptions to Hypothesis to Decision. Better Decisions Through Methodology.
The decisions made by Solution Architects have significant impacts and consequences for the organization and their people. They can have broad impacts on their customers, suppliers, and partners. Significant decisions are not to be taken lightly, so architects need to […]
Six Key Traits of Successful Solution Architect Consultants
I have been thinking about some of the qualities that make up good solution architects. I believe I’ve come up with a short list of the best qualities to expect from a solution architect. This list is not exhaustive, but […]
Beginning and Evolving a Microservices Architecture
Domain driven design and microservices belong together and they go hand in hand, so as part of an overall architecture strategy, it’s important to consider how you are structuring your components, or in the case of a monolith or existing […]
Refining and Applying Methodology and Rules of Engagement at the Onset of New IT Consulting (B2B) Projects
As a consultant and the director and controller of a software consulting company, I’m often regularly engaged as a consultant on new projects with new clients as part of a contract for services business relationship. As a consultant it’s important […]
Ensuring Your Tactical State Architecture is Practical
When building out architecture (solution/software/integration/digital/etc architecture), it’s important to consider if the context of the architecture fits into tactical or not. What’s a tactical architecture? I define tactical architecture as “temporary” architecture that gets the business to a reasonable target […]
The Importance of Contracts as Part of API Architecture and Effective API Solution Delivery
Contracts have been part of software development and architecture forever. In the SOAP days we had WSDL, but we’ve always had the concepts around ensuring backwards compatibility with 3rd party and internally built components (dll, jar packages, etc). In consideration […]
The Strangle Pattern Approach to Enterprise Legacy System Modernization
As architects help enterprises modernize their core capabilities and transition to modern systems as part of digital transformations, the strangle pattern is a useful pattern in the architect’s repertoire. The idea is to slowly drain the life out of a […]
Architecting Your Enterprise APIs Into a Set of API Experiences and the Demise of the Monolithic API
As organizations move to API-lead approaches to architecture and design new API target states for the organization, the concept of a set of publishing a set of experience based API services no doubt come into play. API Management application vendors […]