Designing for change

The team sits down and discusses what it takes to deliver a data solution that is adaptable and robust. What layers, areas and concepts need to be in place?

Design patterns are introduced, and used to communicate the rationale behind the decisions made to all stakeholders.

Diego Pasion - FastChangeCoBefore designing a data solution, start with the outcomes you seek to deliver in mind.

When we design a data solution, fundamental guidelines should permeate every aspect of the design. This requires that they have been considered upfront, and that we do not forget the direction along the way. This chapter provides a logical overview of the main aspects that are part of the data solution.

The decisions resulting from this work can be captured in a solution architecture, supported by documented decisions in design and implementation aspects.


Go Back

Data Engine Thinking Book Cover

Data Engine Thinking

Register interest

Please register your interest using this form, so that we can send you a notification when Data Engine Thinking is available.

We won't use your email for anything else.

Please type your full name.

Invalid email address.

Please select at least one version!

Please confirm the data protection policy!

This form is protected by Aimy Captcha-Less Form Guard

Input was too fast. Suspicion of BOT.