Getting Started
Welcome to the Eventlet Migration Guide! This comprehensive resource is designed to assist developers, system administrators, and technical decision-makers in transitioning from Eventlet to more modern and supported concurrency libraries in Python.
Why Migrate from Eventlet? 🔗
Eventlet has been a popular choice for concurrent programming in Python, particularly within the OpenStack community. However, as the library has become deprecated, it is crucial to explore alternatives that offer better support, performance, and future-proofing for your applications.
There is plenty of reasons to abandon your Eventlet usages. Keeping Eventlet means exposing your company to major legal risks, harming your team's productivity, compromising user security, and destroying your project's credibility. As Eventlet maintainers, we have witnessed these issues firsthand and believe it is our responsibility to help users move away from it. This guide is here to support you in a necessary and well-managed transition.
Neglecting necessary updates nurtures needless risks.
What Benefits Will You Get From Migrating Your Products? 🔗
Migrating to libraries like AsyncIO or Threading can provide numerous benefits, including:
Improved Performance
Modern libraries often offer better performance and scalability for handling concurrent tasks. Modern libraries like Asyncio introduce new paradigms like real cooperative task handling. Threads, with modern versions of Python can benefits from PEP 703 to introduce real parallelism in your Python software.
Active Maintenance
Actively maintained libraries receive regular updates, bug fixes, and new features, ensuring long-term viability. Active maintenance also mean more resources, tutorials, and peers to learn from and collaborate with.
Future-Proofing
Adopting widely-used and supported libraries helps future-proof your applications against obsolescence. They provides guarantees of sustainability to your customers. AsyncIO and threading are both part of the Python standard library, making them a safe choice.
Objectives of This Guide 🔗
The OpenStack community began to pave the way for a structured migration and pionneered bulk migration. The OpenStack community is now eager to share his experience with other. This guide is the result of the work done by the OpenStack community. The intent of this guide is to help other Eventlet users in their migration journey.
The primary goal of this guide is to provide a structured and informative pathway for migrating from Eventlet. By the end of this guide, you will:
- Understand the key differences between Eventlet and its alternatives.
- Learn how to assess your current Eventlet-based applications for migration readiness.
- Follow step-by-step instructions for migrating to AsyncIO or Threading.
- Access resources, including code examples and best practices, to support your migration efforts.
- Hear from others who have successfully navigated this transition, gaining insights from their experiences.
How to Use This Guide 🔗
This guide is organized into sections that address various aspects of the migration process. You can navigate through the sections sequentially or jump to specific areas of interest. Whether you are just beginning to explore migration options or are ready to dive into code refactoring, this guide aims to support you at every stage.
Join us on this journey to modernize your Python applications and unlock the full potential of contemporary alternatives!
Together let's make our products safer by removing eventlet!
Let's get started!