![]() ![]() As a design goal, delivered mail messages are always critical, and things like whether a message has been read is non-critical. Critical data (for example, customer data such as email messages) should be protected at extreme cost. Non-critical data (for example, whether a message was read) can be dropped in rare failure scenarios. There is critical and non-critical data.To that end, Microsoft 365 services have been designed around five specific resiliency principles: Data resiliency means that no matter what failures occur within Microsoft 365, critical customer data remains intact and unaffected. Resiliency refers to the ability of a cloud-based service to withstand certain types of failures and yet remain fully functional from the customers' perspective. Today, customers expect continuous innovation from Microsoft without compromising quality, and this is one of the reasons why Microsoft's services and software are built with resiliency and recoverability in mind. Finally, the scale of deployed systems and the level of their interconnectedness was historically much smaller than it is now.Thus, most IT organizations would deploy only major releases to avoid the work to keep up to date. Moreover, the only way to correct a problem was to roll back. Deploying code without owning the source meant waiting for patch releases, and major version releases involved hardware replacement and significant capital outlay. Third, deployment took place at a glacial pace.Operations teams maintained rigorous procedures, change windows were employed, and there was often significant project management overhead. This structure meant having datacenters with 99.99% reliability required significant power and network redundancy, and servers were implemented with hardware-based clustering, dual power supplies, dual network interfaces, and the like. First, hardware and infrastructure protections were significant.While it would be incorrect to say that software developers were not thinking about these things before the cloud, how these issues were handled in a typical IT implementation was different before the cloud: Resiliency and recoverability are built-inīuilding in resiliency and recovery starts with the assumption that the underlying infrastructure and processes will fail at some point: hardware (infrastructure) will fail, humans will make mistakes, and software will have bugs. We use a combination of less complex physical infrastructure and more intelligent software that builds data resiliency into our services and delivers high availability to our customers. ![]() We have moved beyond the traditional strategy of relying on complex physical infrastructure, and we have built redundancy directly into our cloud services. We design our cloud services to maximize reliability and minimize the negative effects on customers when things do go wrong. Given the complex nature of cloud computing, Microsoft is mindful that it's not a case of if things will go wrong, but rather when. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |