Part 2/2: Quick start to resilient software design

Microservices. APIs. Cloud native. Always on. Near-realtime. And so on. Today's IT landscapes are highly interconnected, massively distributed and need to be responsive 24x7. Downtimes are not an option. Long response times are not an option, either.

Oct 22
Alfândega Porto Congress Centre
2 hours
14:00 - 16:00 UTC
Uwe Friedrichsen
-

In the past, software developers did not care. Availability was an operations problem. So, let the admins configure the Service Mesh properly and we are done! Sorry, not that easy (anymore). The imponderabilities of distributed systems hit us at the application level. Thus, time to learn resilient software design.

In this workshop, we will first discuss why we need resilient software design. Then we will build a little essential patterns toolbox for handling timeouts, failures, overload situations and data consistency. Finally, we will discuss how to implement them in practice and which parts we can (still) delegate to our infrastructure.

You will leave this workshop with a toolbox to create more robust systems and practical advice how to implement them.

Uwe Friedrichsen

Trying to make the (IT) world a little bit better

Uwe Friedrichsen. Longtime traveler in the world of IT. Dot Connector. Cartographer of uncharted territory. Keeper of timeless wisdom. Translator between floors. System design. Resilience. Sustainability. Dislikes long bios. Tries to make IT a (bit) better place. CTO @ codecentric.