When starting a new project, you can not possibly forsee all changes that you may need to implement in the future. Eventually a situation will arise that can not be covered with your current website, and you are forced to rebuild your site. Such a rebuild can be costly, and you risk breaking or loosing existing functionality.
However, while a rebuild can not always be avoided, there are ways to reduce the impact, if a little foresight has been employed when designing the architecture of the original site.
If the architecture is divided into a few mostly independent components that only communicate through a narrow API, then it is often possible to limit the rebuild to one such component, while being able to reuse the others. And even if all components need to be replaced, in many cases this can be done one component at a time, and thus ensuring a smoot transition from the original to the rebuilt site. It is even possible to keep old and new components running side by side, until such time that the old components are no longer needed.
Want to know more?
Sign up for a short email-course, where i will explain to you in detail how this strategy works.
In this email-course you will
- learn more about the components of this architecture.
- find out about the benefits of this approach.
- learn about the drawbacks.
- get an opportunity to ask questions.
Server Architecture Diagnostic
Half an hour spent talking to one of your engineers, we will be able to analyse the current state of your web application services.
After these 30 minutes you and your engineers will
- have a better understanding of the current state of your services
- have an idea for the next stages of development of your application