Alternatives to asyncio logo

Alternatives to asyncio

Flask, Celery, gevent, Node.js, and Tornado are the most popular alternatives and competitors to asyncio.
81
117
+ 1
13

What is asyncio and what are its top alternatives?

This module provides infrastructure for writing single-threaded concurrent code using coroutines, multiplexing I/O access over sockets and other resources, running network clients and servers, and other related primitives.
asyncio is a tool in the Microframeworks (Backend) category of a tech stack.

Top Alternatives to asyncio

  • Flask

    Flask

    Flask is intended for getting started very quickly and was developed with best intentions in mind. ...

  • Celery

    Celery

    Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well. ...

  • gevent

    gevent

    It is a coroutine -based Python networking library that uses greenlet to provide a high-level synchronous API on top of the libev or libuv event loop. ...

  • Node.js

    Node.js

    Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices. ...

  • Tornado

    Tornado

    By using non-blocking network I/O, Tornado can scale to tens of thousands of open connections, making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user. ...

  • Twisted

    Twisted

    Twisted is an event-driven networking engine written in Python and licensed under the open source ​MIT license. Twisted runs on Python 2 and an ever growing subset also works with Python 3. Twisted also supports many common network protocols, including SMTP, POP3, IMAP, SSHv2, and DNS. ...

  • AIOHTTP

    AIOHTTP

    It is an Async http client/server framework. It supports both client and server Web-Sockets out-of-the-box and avoids Callback. It provides Web-server with middlewares and pluggable routing. ...

  • ExpressJS

    ExpressJS

    Express is a minimal and flexible node.js web application framework, providing a robust set of features for building single and multi-page, and hybrid web applications. ...

asyncio alternatives & related posts

Flask logo

Flask

14.1K
11.8K
1.5K
A microframework for Python based on Werkzeug, Jinja 2 and good intentions
14.1K
11.8K
+ 1
1.5K
PROS OF FLASK
  • 313
    Lightweight
  • 269
    Python
  • 214
    Minimal
  • 145
    Open source
  • 98
    Documentation
  • 66
    Easy to use
  • 54
    Easy to setup and get it going
  • 53
    Well designed
  • 48
    Easy to develop and maintain applications
  • 45
    Easy to get started
  • 18
    Beautiful code
  • 16
    Rapid development
  • 14
    Powerful
  • 13
    Expressive
  • 12
    Awesome
  • 11
    Love it
  • 11
    Flexibilty
  • 11
    Speed
  • 10
    Get started quickly
  • 10
    Simple to use
  • 10
    Easy to integrate
  • 9
    Perfect for small to large projects with superb docs.
  • 9
    For it flexibility
  • 9
    Customizable
  • 8
    Productive
  • 8
    Flexibilty and easy to use
  • 7
    Flask
  • 6
    Not JS
  • 6
    User friendly
  • 5
    Secured
  • 4
    Unopinionated
  • 1
    Secure
  • 1
    Orm
CONS OF FLASK
  • 10
    Not JS
  • 7
    Context
  • 4
    Not fast
  • 1
    Don't has many module as in spring

related Flask posts

James Man
Software Engineer at Pinterest · | 42 upvotes · 842.2K views
Shared insights
on
FlaskFlaskReactReact
at

One of our top priorities at Pinterest is fostering a safe and trustworthy experience for all Pinners. As Pinterest’s user base and ads business grow, the review volume has been increasing exponentially, and more content types require moderation support. To solve greater engineering and operational challenges at scale, we needed a highly-reliable and performant system to detect, report, evaluate, and act on abusive content and users and so we created Pinqueue.

Pinqueue-3.0 serves as a generic platform for content moderation and human labeling. Under the hood, Pinqueue3.0 is a Flask + React app powered by Pinterest’s very own Gestalt UI framework. On the backend, Pinqueue3.0 heavily relies on PinLater, a Pinterest-built reliable asynchronous job execution system, to handle the requests for enqueueing and action-taking. Using PinLater has significantly strengthened Pinqueue3.0’s overall infra with its capability of processing a massive load of events with configurable retry policies.

Hundreds of millions of people around the world use Pinterest to discover and do what they love, and our job is to protect them from abusive and harmful content. We’re committed to providing an inspirational yet safe experience to all Pinners. Solving trust & safety problems is a joint effort requiring expertise across multiple domains. Pinqueue3.0 not only plays a critical role in responsively taking down unsafe content, it also has become an enabler for future ML/automation initiatives by providing high-quality human labels. Going forward, we will continue to improve the review experience, measure review quality and collaborate with our machine learning teams to solve content moderation beyond manual reviews at an even larger scale.

See more

Hey, so I developed a basic application with Python. But to use it, you need a python interpreter. I want to add a GUI to make it more appealing. What should I choose to develop a GUI? I have very basic skills in front end development (CSS, JavaScript). I am fluent in python. I'm looking for a tool that is easy to use and doesn't require too much code knowledge. I have recently tried out Flask, but it is kinda complicated. Should I stick with it, move to Django, or is there another nice framework to use?

See more
Celery logo

Celery

1.4K
1.3K
265
Distributed task queue
1.4K
1.3K
+ 1
265
PROS OF CELERY
  • 94
    Task queue
  • 61
    Python integration
  • 37
    Django integration
  • 29
    Scheduled Task
  • 18
    Publish/subsribe
  • 6
    Easy to use
  • 6
    Various backend broker
  • 5
    Great community
  • 4
    Workflow
  • 4
    Free
  • 1
    Dynamic
CONS OF CELERY
  • 4
    Sometimes loses tasks
  • 1
    Depends on broker

related Celery posts

James Cunningham
Operations Engineer at Sentry · | 18 upvotes · 1.3M views
Shared insights
on
CeleryCeleryRabbitMQRabbitMQ
at

As Sentry runs throughout the day, there are about 50 different offline tasks that we execute—anything from “process this event, pretty please” to “send all of these cool people some emails.” There are some that we execute once a day and some that execute thousands per second.

Managing this variety requires a reliably high-throughput message-passing technology. We use Celery's RabbitMQ implementation, and we stumbled upon a great feature called Federation that allows us to partition our task queue across any number of RabbitMQ servers and gives us the confidence that, if any single server gets backlogged, others will pitch in and distribute some of the backlogged tasks to their consumers.

#MessageQueue

See more
Pulkit Sapra

Hi! I am creating a scraping system in Django, which involves long running tasks between 1 minute & 1 Day. As I am new to Message Brokers and Task Queues, I need advice on which architecture to use for my system. ( Amazon SQS, RabbitMQ, or Celery). The system should be autoscalable using Kubernetes(K8) based on the number of pending tasks in the queue.

See more
gevent logo

gevent

32
41
0
Coroutine network library for Python
32
41
+ 1
0
PROS OF GEVENT
    Be the first to leave a pro
    CONS OF GEVENT
    • 1
      Not native

    related gevent posts

    Node.js logo

    Node.js

    124.3K
    102.9K
    8.4K
    A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
    124.3K
    102.9K
    + 1
    8.4K
    PROS OF NODE.JS
    • 1.4K
      Npm
    • 1.3K
      Javascript
    • 1.1K
      Great libraries
    • 1K
      High-performance
    • 795
      Open source
    • 484
      Great for apis
    • 474
      Asynchronous
    • 420
      Great community
    • 390
      Great for realtime apps
    • 295
      Great for command line utilities
    • 81
      Node Modules
    • 80
      Websockets
    • 67
      Uber Simple
    • 57
      Great modularity
    • 56
      Allows us to reuse code in the frontend
    • 40
      Easy to start
    • 35
      Great for Data Streaming
    • 31
      Realtime
    • 26
      Awesome
    • 24
      Non blocking IO
    • 17
      Can be used as a proxy
    • 16
      High performance, open source, scalable
    • 15
      Non-blocking and modular
    • 14
      Easy and Fun
    • 12
      Easy and powerful
    • 12
      Same lang as AngularJS
    • 11
      Future of BackEnd
    • 10
      Fast
    • 9
      Fullstack
    • 9
      Scalability
    • 9
      Cross platform
    • 8
      Simple
    • 7
      Mean Stack
    • 6
      Great for webapps
    • 6
      Easy concurrency
    • 5
      Friendly
    • 5
      Fast, simple code and async
    • 5
      React
    • 4
      Great speed
    • 4
      Fast development
    • 4
      Its amazingly fast and scalable
    • 4
      Control everything
    • 4
      Easy to use and fast and goes well with JSONdb's
    • 4
      Typescript
    • 4
      Scalable
    • 3
      It's fast
    • 3
      Easy to use
    • 3
      Isomorphic coolness
    • 2
      Sooper easy for the Backend connectivity
    • 2
      Easy to learn
    • 2
      TypeScript Support
    • 2
      Scales, fast, simple, great community, npm, express
    • 2
      One language, end-to-end
    • 2
      Javascript2
    • 2
      Not Python
    • 2
      Performant and fast prototyping
    • 2
      Blazing fast
    • 2
      Great community
    • 2
      Less boilerplate code
    • 2
      Easy
    • 1
      Lovely
    • 1
      Event Driven
    CONS OF NODE.JS
    • 46
      Bound to a single CPU
    • 42
      New framework every day
    • 35
      Lots of terrible examples on the internet
    • 29
      Asynchronous programming is the worst
    • 23
      Callback
    • 16
      Javascript
    • 11
      Dependency based on GitHub
    • 10
      Dependency hell
    • 10
      Low computational power
    • 7
      Can block whole server easily
    • 6
      Very very Slow
    • 6
      Callback functions may not fire on expected sequence
    • 3
      Unneeded over complication
    • 3
      Unstable
    • 3
      Breaking updates
    • 1
      No standard approach

    related Node.js posts

    Nick Rockwell
    SVP, Engineering at Fastly · | 44 upvotes · 1.7M views

    When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

    So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

    React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

    Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

    See more
    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 39 upvotes · 4.2M views

    How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

    Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

    Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

    https://eng.uber.com/distributed-tracing/

    (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

    Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

    See more
    Tornado logo

    Tornado

    316
    368
    165
    A Python web framework and asynchronous networking library, originally developed at FriendFeed
    316
    368
    + 1
    165
    PROS OF TORNADO
    • 37
      Open source
    • 31
      So fast
    • 27
      Great for microservices architecture
    • 20
      Websockets
    • 17
      Simple
    • 13
      Asynchronous
    • 10
      Python
    • 7
      Lightweight
    • 3
      Handles well persistent connexions
    CONS OF TORNADO
    • 2
      Event loop is complicated

    related Tornado posts

    Around the time of their Series A, Pinterest’s stack included Python and Django, with Tornado and Node.js as web servers. Memcached / Membase and Redis handled caching, with RabbitMQ handling queueing. Nginx, HAproxy and Varnish managed static-delivery and load-balancing, with persistent data storage handled by MySQL.

    See more
    Twisted logo

    Twisted

    48
    76
    10
    Event-driven networking engine written in Python
    48
    76
    + 1
    10
    PROS OF TWISTED
    • 5
      Easy-to-understand concurrency
    • 3
      Twisted prevails
    • 1
      It works
    • 1
      Solid, flexible, powerful
    CONS OF TWISTED
      Be the first to leave a con

      related Twisted posts

      AIOHTTP logo

      AIOHTTP

      109
      117
      0
      Asynchronous HTTP Client/Server for asyncio and Python
      109
      117
      + 1
      0
      PROS OF AIOHTTP
        Be the first to leave a pro
        CONS OF AIOHTTP
          Be the first to leave a con

          related AIOHTTP posts

          Jelena Dedovic

          Investigating Tortoise ORM and GINO ORM...

          I need to introduce some async ORM with the current stack: Tornado with asyncio loop, AIOHTTP, with PostgreSQL and MSSQL. This project revolves heavily around realtime and due to the realtime requirements, blocking during database access is not acceptable.

          Considering that these ORMs are both young projects, I wondered if anybody had some experience with similar stack and these async ORMs?

          See more
          ExpressJS logo

          ExpressJS

          20.9K
          15.8K
          1.5K
          Sinatra inspired web development framework for node.js -- insanely fast, flexible, and simple
          20.9K
          15.8K
          + 1
          1.5K
          PROS OF EXPRESSJS
          • 367
            Simple
          • 322
            Node.js
          • 235
            Javascript
          • 185
            High performance
          • 148
            Robust routing
          • 66
            Middlewares
          • 66
            Open source
          • 53
            Great community
          • 34
            Hybrid web applications
          • 10
            Well documented
          • 8
            Sinatra inspired
          • 5
            Isomorphic js.. superfast and easy
          • 4
            Rapid development
          • 2
            Socket connection
          • 2
            Npm
          • 2
            Event loop
          • 2
            Light weight
          • 2
            Resource available for learning
          • 2
            Xxx
          • 1
            Callbacks
          • 1
            Data stream
          CONS OF EXPRESSJS
          • 23
            Not python
          • 16
            Overrated
          • 14
            No multithreading
          • 6
            Javascript
          • 5
            Not fast
          • 2
            Easily Insecure for Novices
          • 1
            Not a lion

          related ExpressJS posts

          Simon Reymann
          Senior Fullstack Developer at QUANTUSflow Software GmbH · | 25 upvotes · 2.1M views

          Our whole Node.js backend stack consists of the following tools:

          • Lerna as a tool for multi package and multi repository management
          • npm as package manager
          • NestJS as Node.js framework
          • TypeScript as programming language
          • ExpressJS as web server
          • Swagger UI for visualizing and interacting with the API’s resources
          • Postman as a tool for API development
          • TypeORM as object relational mapping layer
          • JSON Web Token for access token management

          The main reason we have chosen Node.js over PHP is related to the following artifacts:

          • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
          • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
          • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
          • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
          See more

          Repost

          Overview: To put it simply, we plan to use the MERN stack to build our web application. MongoDB will be used as our primary database. We will use ExpressJS alongside Node.js to set up our API endpoints. Additionally, we plan to use React to build our SPA on the client side and use Redis on the server side as our primary caching solution. Initially, while working on the project, we plan to deploy our server and client both on Heroku . However, Heroku is very limited and we will need the benefits of an Infrastructure as a Service so we will use Amazon EC2 to later deploy our final version of the application.

          Serverside: nodemon will allow us to automatically restart a running instance of our node app when files changes take place. We decided to use MongoDB because it is a non relational database which uses the Document Object Model. This allows a lot of flexibility as compared to a RDMS like SQL which requires a very structural model of data that does not change too much. Another strength of MongoDB is its ease in scalability. We will use Mongoose along side MongoDB to model our application data. Additionally, we will host our MongoDB cluster remotely on MongoDB Atlas. Bcrypt will be used to encrypt user passwords that will be stored in the DB. This is to avoid the risks of storing plain text passwords. Moreover, we will use Cloudinary to store images uploaded by the user. We will also use the Twilio SendGrid API to enable automated emails sent by our application. To protect private API endpoints, we will use JSON Web Token and Passport. Also, PayPal will be used as a payment gateway to accept payments from users.

          Client Side: As mentioned earlier, we will use React to build our SPA. React uses a virtual DOM which is very efficient in rendering a page. Also React will allow us to reuse components. Furthermore, it is very popular and there is a large community that uses React so it can be helpful if we run into issues. We also plan to make a cross platform mobile application later and using React will allow us to reuse a lot of our code with React Native. Redux will be used to manage state. Redux works great with React and will help us manage a global state in the app and avoid the complications of each component having its own state. Additionally, we will use Bootstrap components and custom CSS to style our app.

          Other: Git will be used for version control. During the later stages of our project, we will use Google Analytics to collect useful data regarding user interactions. Moreover, Slack will be our primary communication tool. Also, we will use Visual Studio Code as our primary code editor because it is very light weight and has a wide variety of extensions that will boost productivity. Postman will be used to interact with and debug our API endpoints.

          See more