Handling Updates and Changes in Records365

Proper handling of updates and change is always a challenge and even more so when running a SaaS offering such as Records365. Careful thought must be paid to each component of the solution, from the infrastructure to the logical architecture, and to each component’s individual strategy regarding updates and changes, as well as an overall holistic approach to change in the system. Resilience and support for change is accomplished by providing architectural options at each layer of the solution and by the avoidance of single points of failure, or more specifically, single points of an update.