Workflow Orchestration for Building Resilient Software Systems

Building resilient software systems can be difficult especially when they are distributed. Executing a long-running business process or workflow that involves multiple different service boundaries requires a lot of resiliency. Everything needs to be available and functioning because if something fails mid-way through you can be left in an inconsistent state. So a the solution? Removing direct service to service communication and temporal coupling.

🔗 Solace
https://solace.com/codeopinion

🔔 Subscribe: @codeopinion

💥 Join this channel to get access to source code & demos!
@codeopinion

🔥 Don't have the JOIN button? Support me on Patreon!
Patreon: codeopinion

📝 Blog: https://codeopinion.com
👋 Twitter: Twitter: codeopinion
✨ LinkedIn: LinkedIn: dcomartin
📧 Weekly Updates: https://mailchi.mp/63c7a0b3ff38/codeo...

0:00 Intro
1:03 Distributed Monolith
3:53 Temporal Coupling
5:50 Orchestration

#softwarearchitecture #softwaredesign #codeopinion

• #science_technology
• #resilient_software_systems
• #software_architecture
• #software_design
• #software_architect
• #microservices
• #message_queues
• #kafka
• #event_bus
• #event_driven_architecture
• #azure_service_bus
• #rabbitmq
• #distributed_transactions
• #service_bus
• #message_queue
• #message_queuing
• #messaging_patterns
• #service_oriented_architecture
• #microservice_architecture
• #domain_driven_design
• #enterprise_service_bus
• #resilient_sofware_systems
• #resilient_design
• #resilient_system_design
• #resilient_sytem_design