Need advice about which tool to choose?Ask the StackShare community!

asyncio

81
114
+ 1
13
Nameko

14
61
+ 1
0
Add tool

asyncio vs Nameko: What are the differences?

What is asyncio? Asynchronous I/O, event loop, coroutines and tasks. 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.

What is Nameko? Python microservices framework. Python microservices framework that leverages AMQP for RPC. It supports asynchronous and synchronous events.

asyncio and Nameko can be categorized as "Microframeworks (Backend)" tools.

Nameko is an open source tool with 2.98K GitHub stars and 290 GitHub forks. Here's a link to Nameko's open source repository on GitHub.

Advice on asyncio and Nameko
Girish Sharma
Software Engineer at FireVisor Systems · | 6 upvotes · 106.8K views
Needs advice
on
Nameko
Flask
and
Bottle

Which is the best Python framework for microservices?

We are using Nameko for building microservices in Python. The things we really like are dependency injection and the ease with which one can expose endpoints via RPC over RabbitMQ. We are planning to try a tool that helps us write polyglot microservices and nameko is not super compatible with it. Also, we are a bit worried about the not so good community support from nameko and looking for a python alternate to write microservices.

See more
Replies (1)
Recommends
Bottle

Bottle is much less bloated and fast. Its built-in templating system is one of the fastest as it compiles the templates in bytecode. Also Bottle has no depenencies, preventing dependency bloat.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of asyncio
Pros of Nameko
  • 4
    Cooperative Multitasking
  • 4
    I/O Wait
  • 3
    Network Call
  • 2
    I/O bound computation
    Be the first to leave a pro

    Sign up to add or upvote prosMake informed product decisions

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    What is asyncio?

    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.

    What is Nameko?

    Python microservices framework that leverages AMQP for RPC. It supports asynchronous and synchronous events.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use asyncio?
    What companies use Nameko?
    See which teams inside your own company are using asyncio or Nameko.
    Sign up for Private StackShareLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with asyncio?
    What tools integrate with Nameko?
      No integrations found

      Sign up to get full access to all the tool integrationsMake informed product decisions

      Blog Posts

      +4
      7
      954
      What are some alternatives to asyncio and Nameko?
      Flask
      Flask is intended for getting started very quickly and was developed with best intentions in mind.
      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
      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 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
      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.
      See all alternatives