登录查看更多内容

How do you handle software failures and recovery in the cloud?

由人工智能和领英社区提供技术支持

Cloud computing has revolutionized the way software is developed, deployed, and scaled. But it also comes with new challenges and risks for software reliability, such as network failures, service outages, and security breaches. How do you handle software failures and recovery in the cloud? In this article, we'll explore some of the key concepts and best practices for designing reliable software for the cloud.

此文章中的业界达人

由社区从 3 条内容中精选。了解更多

Simon Hibbard

Technology Lead at NHS Blood and Transplant

1 Fault tolerance

Fault tolerance is the ability of a system to continue functioning despite the presence or occurrence of faults, errors, or failures. Faults can be either internal (such as bugs, memory leaks, or hardware malfunctions) or external (such as power outages, network disruptions, or malicious attacks). Fault tolerance can be achieved by various techniques, such as redundancy, replication, load balancing, failover, and backup. Fault tolerant systems aim to minimize the impact of faults on the system's performance, availability, and functionality.

添加您的观点

Simon Hibbard

Technology Lead at NHS Blood and Transplant
举报内容
Of course you can always go to the nth degree to avoid faults, and we would always engineer our systems to be as tolerant as possible. It really comes down to the business needs and what faults and recovery time are acceptable. The standards need to be well defined and the time/effort allocated to implement the systems as required. Where risk cannot be fully mitigated it should be agreed as an accepted risk of the business.

已翻译

赞

2 Fault recovery

Fault recovery is the process of restoring a system to a normal or acceptable state after a fault has occurred. Fault recovery can be either manual (such as human intervention, debugging, or troubleshooting) or automatic (such as self-healing, rollback, or retry). Fault recovery can be either proactive (such as preventive maintenance, monitoring, or testing) or reactive (such as error handling, logging, or alerting). Fault recovery can be either local (such as within a component, a node, or a service) or global (such as across a cluster, a region, or a cloud).

添加您的观点

Simon Hibbard

Technology Lead at NHS Blood and Transplant
举报内容
We recently transformed our monolithic software stack to a microservice based architecture. It comes with is benefits, but also complexity. One recently realised benefit was when a live deployment failed causing an outage. The total release was quite large in terms of blast radius, but due to the microservices we were able to roll back just a single function, leaving the majority of the release components intact. We were then able to run effectively with the rolled back function allowing time to fix the issue with the single function and deploy at a later stage with minimal risk.

已翻译

赞

3 Fault prevention

Fault prevention is the effort of avoiding or eliminating faults before they happen or affect the system. Fault prevention can be done at different stages of the software development lifecycle, such as design, implementation, testing, deployment, and operation. Fault prevention can involve various practices, such as quality assurance, code review, static analysis, unit testing, integration testing, performance testing, security testing, configuration management, continuous integration, continuous delivery, and continuous monitoring.

添加您的观点

Sanjay Dua

Senior Engineering Manager
举报内容
Establishing a cross-functional review process such as a Solution Architecture Review Board (SARB) is crucial to ensuring fault tolerance in mission-critical systems. It's important to have architects from different domains involved in the review process to ensure that all aspects of the system are taken into account and that fault tolerance is built into the design from the outset. In addition to involving architects from different domains, it's also essential to consider business SLAs such as availability, recovery point, and recovery time objectives in the review process. These SLAs provide important input for the SARB to ensure that the system is designed to meet the organization's specific requirements for fault tolerance.

已翻译

赞

4 Reliability engineering

Reliability engineering is the discipline of applying engineering principles and methods to ensure the reliability of software systems. Reliability engineering covers the aspects of fault tolerance, fault recovery, and fault prevention, as well as other related topics, such as availability, dependability, scalability, resilience, and robustness. Reliability engineering can use various tools, frameworks, and standards, such as reliability models, metrics, analysis, testing, design patterns, architectures, protocols, and best practices.

添加您的观点

5 Reliability patterns

Reliability patterns are reusable solutions to common problems or challenges related to software reliability. Reliability patterns can be applied at different levels of abstraction and granularity, such as architectural, design, or code level. Reliability patterns can address various aspects of reliability, such as communication, coordination, state management, data consistency, concurrency, caching, security, or logging. Some examples of reliability patterns are circuit breaker, retry, fallback, timeout, bulkhead, leader election, saga, event sourcing, and CQRS.

添加您的观点

6 Reliability trade-offs

Reliability trade-offs are the decisions or compromises that have to be made when designing or implementing reliable software systems. Reliability trade-offs can involve balancing or prioritizing different factors or goals, such as performance, cost, complexity, usability, or security. Reliability trade-offs can also involve accepting or tolerating some degree or type of faults, errors, or failures. Reliability trade-offs can depend on various factors, such as the system's requirements, constraints, context, or environment.

添加您的观点

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?

添加您的观点

Software Design

+ 关注

给文章评分

我们借助人工智能创建了此文章。您认为这篇文章怎么样？

很棒不太好

举报此文章

查看全部

How do you handle software failures and recovery in the cloud?

1

2

3

4

5

6

7

1 Fault tolerance

2 Fault recovery

3 Fault prevention

4 Reliability engineering

5 Reliability patterns

6 Reliability trade-offs

7 Here’s what else to consider

Software Design

给文章评分

感谢您的反馈

更多Software Design相关文章

更多相关阅读内容

How do you handle software failures and recovery in the cloud?

1

2

3

4

5

6

7

1 Fault tolerance

2 Fault recovery

3 Fault prevention

4 Reliability engineering

5 Reliability patterns

6 Reliability trade-offs

7 Here’s what else to consider

Software Design

给文章评分

感谢您的反馈

查看其他技能