Current Architecture & Future Architecture
Posted: 02 Aug 2022, 09:31
Dear reader,
I have a question that probably serves a wider audience as multiple organizations will have a target architecture besides having a current architecture. In my case, the current architecture is of course the status quo, so all things in Essential and the relation of these 'things' to one another.
Yet we also have a future (or target) architecture which is quite different from the status quo. This meaning that there are different 'things' on top of the existing things and that the relation between these things can be different from what is true for the status quo architecture.
My question to you is: How would you suggest to leverage Essential in order to accommodate for both the current architecture as for the future target architecture?
This because I can imagine that it would become quite messy if it is all in the same repository.
Many thanks and best regards,
Carlo
I have a question that probably serves a wider audience as multiple organizations will have a target architecture besides having a current architecture. In my case, the current architecture is of course the status quo, so all things in Essential and the relation of these 'things' to one another.
Yet we also have a future (or target) architecture which is quite different from the status quo. This meaning that there are different 'things' on top of the existing things and that the relation between these things can be different from what is true for the status quo architecture.
My question to you is: How would you suggest to leverage Essential in order to accommodate for both the current architecture as for the future target architecture?
This because I can imagine that it would become quite messy if it is all in the same repository.
Many thanks and best regards,
Carlo