Design Patterns and Best Practices in Java

Failure-handling pattern

Another important aspect for maintaining resilience in a system is asking the question, If one or more components or services go down, will my system still be able to function properly? For example, take an e-commerce site. There are many services and functionalities working together to keep the site up, such as product searches, product catalogs, recommendation engines, review components, the shopping cart, payment gateways, and so on. If one of the services, such as the search component, goes down due to load or hardware failure, will that impact end users' ability to place an order? Ideally, these two services should be created and maintained independently. So, if a search service is not available, the user can ...