Tag: Architecture

Guidance and tips
Where To Start With Microservices
How to avoid a Frankenstein's monster!
Microservices, monoliths and modernization
Importance of scalable software architecture
The Impact Of Software Architecture On Enterprise Agility
Software Intelligence Can Help
Containers And Microservices At Scale - How To Operate Them
Architecture Insights Can Help Modernization
How Software Architecture Helps Modernization?
Technical debt and DevOps are two topics on every organizations mind.  Yet, no one tackles the topic better than this article
Technical Debt & DevOps: 5 factors fueling automation in IT
In the development cycle there are many places where technical debt can rear its head and cause problems down the line for the product you’re developing. In order to tackle the problem of technical debt first teams need to know what it’s comprised of, how to identify it, and, then, how to address it’s presence in a system.
The Symptoms and Causes of Technical Debt
As business leaders become more involved with IT investment decisions many CIOs have found it more difficult to receive funding for maintenance of applications and infrastructure. The result of this is that technical debt has become an even more useful term to explain to business stakeholders the importance of IT maintenance investments. This post goes into detail on how to calculate technical debt.
How To Calculate Technical Debt: A Top-Down Approach
Paying off technical debt, according to this post, can be made easier with microservices architecture. When building a code base, eventually, trade-offs between quality and delivering on time will arise. The benefit of trade-offs in software is that the option to later go back and fix these shortcuts is available. Quick and dirty shortcuts and expedient design decisions build up over time and create technical debt, which needs to be paid pack before it reaches unmanageable levels. This entails refactoring bad code and reviewing questionable design decisions before defaulting on the debt created. Once the debt has been defaulted on, things start breaking all over the code base and makes working almost impossible.
Microservices Architecture & Reducing Technical Debt
This article gives us an in depth look at another type of IT debt: architectural debt. It starts off with the jarring statistic that 72% of IT budgets are usually spent “keeping the lights on” or in other words day-to-day maintenance. The only way to reduce this proportion of the budget dedicated to maintenance is to address its cause.
Architectural Debt and Moving to Software Defined Architectures
This interview will focus on the ground-level steps that should be taken in order to help IT teams deal with their Technical Debt in a pragmatic and efficient way, while working in a fast-paced Agile environment.
Pragmatic Ways for Your IT Team to Deal with Technical Debt