This course is about enterprise integration patterns proposed by Apache Camel.

The Camel Enterprise Integration Patterns (EIP) provide the interfaces to communicate with large component-based distributed systems. When designing the best integration solution for message-oriented applications, these patterns help save time and effort.

In this course, you'll learn about all four foundational patterns. You'll be introduced to Error Handling patterns, Deployment patterns, and Configuration patterns. Each pattern is discussed in detail to be used in distinct settings. You'll also gain a deep understanding of how each pattern works under different circumstances, and implement them appropriately when necessary using real-world examples to illustrate the design specifics. Camel EIPs offer advantages over traditional frameworks such as REST or SOAP regarding integration problems within an organization.

By the end of this course, you'll have hands-on practice with valuable interfaces and the simplification processes for integrating applications across an organization's services.

Using Apache Camel with Enterprise Integration Patterns

## Intent

This pattern enforces resource partitioning and damage containment to preserve partial functionality in the case of a failure.The Bulkhead pattern is also known as the **Failure Containment Principle** and the **Damage Control Principle**.

## Context and problem

The Titanic disaster has been well studied over the years, and there are many lessons we can learn from it in the IT industry. Among the many reasons why it sank, a few of them are as follows:

 - Design flaws (watertight compartments did not reach high enough in order to allow more living space in first class).
 - Implementation/construction faults (the three million rivets used to hold different parts of the Titanic together were found to be made from substandard quality iron, and the collision with the iceberg badly impacted them).
- Operational failures (the iceberg notice was given too late, and the ship was traveling too fast to react to any warning). 

We can identify similar issues in software projects today too, but luckily they have not cost so many human lives so far, and as a consequence, we learn more slowly than other industries. However, that does not mean software failures have no consequences. Plenty of examples (such as the Therac-25 machine) caused human death because of software defects.

# Intent

This pattern enforces resource partitioning and damage containment to preserve partial functionality in the case of a failure.The Bulkhead pattern is also known as the **Failure Containment Principle** and the **Damage Control Principle**.

# Context and problem

The Titanic disaster has been well studied over the years, and there are many lessons we can learn from it in the IT industry. Among the many reasons why it sank, a few of them are as follows:

 - Design flaws (watertight compartments did not reach high enough in order to allow more living space in first class).
 - Implementation/construction faults (the three million rivets used to hold different parts of the Titanic together were found to be made from substandard quality iron, and the collision with the iceberg badly impacted them).
- Operational failures (the iceberg notice was given too late, and the ship was traveling too fast to react to any warning). 

We can identify similar issues in software projects today too, but luckily they have not cost so many human lives so far, and as a consequence, we learn more slowly than other industries. However, that does not mean software failures have no consequences. Plenty of examples (such as the Therac-25 machine) caused human death because of software defects.

Learn the Bulkhead design pattern and its usage.

About This Course

Foundational Patterns

Error Handling Patterns

Deployment Patterns

Conclusion

Bulkhead Pattern

Intent

Context and problem