The Circuit Breaker pattern is used to check the availability of an external service, detect failures and prevent them from happening constantly. For example, if an application needs to retrieve data from an external service
There are some consideration when using retry pattern: When there is an indication that the fault is not transient or unlikely for service request to be successful if repeated (for example, an authentication failure caused by invalid user credentials or bad request send to service , e.g., HTTP status code 4xx received from the service), the application should not try to retry , but abort the operation invocation and report a suitable exception. If the specific fault is unusual or rare, it may have been caused by extraordinary circumstances such as a network packet lost in transit. In this case, the application could immediately retry the same request again because the same failure is unlikely to happen again and the request will probably be successful. If the fault is caused by issues such as service being not fully responsive (e.g., “service busy “) the service consumer should wait for a suitable time before retrying the request.
The first installment of modern patterns with basic descriptions. A part of the collection of modern architecture patterns for the ITABoK.
Technical debt is a critical issue for all architects and developers of software intensive systems. Learn techniques for dealing with it.
The architecture lifecycle, or Architecture Development Life Cycle (ADLC), are the stages that an architecture goes through from its inception to its decommissioning. The ADLC provides a guiding process for developing architecture, and helps the architect understand and communicate the state of the architecture.
Overview of services and integration principles.
Service blueprints are a design tool for services and service flow used often with customer journeys.
Services are the backbone of the technical implementation of business capabilities and modern agile methods.
Understanding how to caclulate value in architecture is a critical skill. This learning shot will get you started on basic value management and calculation techniques.
Visual descriptions of a plan against time for achieving one or more goals or objectives
Understand the business model, the building blocks and how to model using a business model canvas
Using the BDN you can describe and explore the impacts of technology enablers to business outcomes.
I have been building software for many years and at the same time building a non-profit business to help people build better systems of people, process and technology. Because of this I am deeply
We are happy to share this interview we did with Cormac Keogh. Thank you sir for making time for us and sharing your vision with us and our viewers!
Less technical than our usual interviews, but most definitely worth watching. Thank you for sharing your vision with us Marco, it is always interesting to understand more of our profession from a non-technical prospective
A while ago we did this amazing and thoughtful interview with Roger Stoffers, who is an enterprise architect at the Volksbank, and we can finally share now. We are grateful that you sat down
Watch our latest interview with Alex Giamas, who is a technical architect at Department for International Trade. We had a blast doing an interview with you!
It was an absolute honor to do an interview with Jim Weaver, the CIO for the State of Washington. Thank you for your valuable thoughts and exciting insights!
Thank you Phil Williams for your good view on our profession and valuable knowledge
Click edit button to change this text.