PyWeb-IL #113 - February 2025

What happens if an event comes more than once? Have you ever heard the phrase "at least once"?

In the evolving world of cloud computing and event-driven architectures, we must adapt and master a new world of challenges.

Idempotency, the ability of handling duplicate events and processing them only once, is a challenging yet crucial art to master when building distributed services. The ability to perform retries and avoid unexpected side-effects and corrupted data is essential if you want to master supporting services at scale. Since those issues may occur in any event-driven system, it is fundamental to come prepared and know how to handle them.

In this session, we will explain what idempotency is, why it’s essential, and what the issues are when not handled correctly. We discuss also common scenarios to be aware of idempotency hazards, how to identify, handle, and avoid them. Finally, we will present the tools and common practices to create an idempotent system.

By the end of this talk, the audience will be familiar with the idempotency hazards and how to overcome them, highly improving their relability and resilience.

In this lecture, we will explore the evolution of Python monitoring over the years, covering tools and techniques from sys.monitoring to import hooks, highlighting advancements and best practices in keeping your Python code in check.

Join us and time-travel across the evolution of Python monitoring mechanisms. We'll delve into history from dedicated tools like sys.monitoring to more advanced techniques such as ceval and import hooks. This session will provide a comprehensive overview of how monitoring practices have developed over the years, offering insights into the best practices for maintaining and debugging your Python code and the pros and cons of each approach. Whether you're a seasoned developer or new to Python, you'll gain valuable knowledge on how to keep your code running smoothly and efficiently without hurting performance or your dev velocity with tedious maintenance.

It's Thursday afternoon, and you've got plans for this evening. You've just finished the feature. You push to main, and click deploy. OR DO YOU? let's talk about Thursday deployments and what they can teach us.