In previous article I discussed how to decompose an application into an architectural design using volatility based decomposition. I now want to show how the architecture can help you with your project planning.
In previous articles I discussed the different ways a use case can be broken down into services. In the following article I will extend on that and show how the back-end should drive your front-end.
Volatility based decomposition is way to break a system up into components that can absorb change and result in a stable system. It builds on SOLID principles and can be viewed as the opposite of functional decomposition.
Functional decomposition is a way to decompose \ break down a system into its most simplistic components and functions for rapid application development.
The hidden monolith I decided to start an article based on the “Hidden monolith”. Micro-services are the latest architecture style that everyone is employing. Often companies hear the new buzz word “Micro services” and say – “We must do that” … and when you start to analyze their system you realize… they got it a… Read More »
What is this buzz word, Agile? When we think agile we think of software processes and being able to change the direction of R & D or a project at a rapid pace to allow for the customization of software or the development cycle to provide rapid software features to a client through the act of… Read More »
In the following post I will show why you need a dedicated software architect by drawing some parallels to actual architects from the building industry to show why you need a software architect.
The word ‘COOL’ will be used to describe the latest tech hype item in the article below. Often I see the ‘COOL’ – coding features / models, components, technology or applications being used simply cause its the latest ‘COOL’ thing around.
Architecture vs Design Often people look at these two topics – architecture and design and think the two look similar and so they can be done by the same individual. As a result the role of technical lead and architect gets merged.
As developers we are taught that the lack of process and coding standards are the reason for project failures. The majority of us blindly believe it without really examining if this is the truth. Let me take you on a trip down the rabbit hole and let’s explore the truth of the matter.