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

AIOHTTP

126
141
+ 1
0
GraphQL

33.8K
27.1K
+ 1
310
Add tool

AIOHTTP vs GraphQL: What are the differences?

Developers describe AIOHTTP as "Asynchronous HTTP Client/Server for asyncio and Python". 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.. On the other hand, GraphQL is detailed as "A data query language and runtime". GraphQL is a data query language and runtime designed and used at Facebook to request and deliver data to mobile and web apps since 2012.

AIOHTTP and GraphQL are primarily classified as "Microframeworks (Backend)" and "Query Languages" tools respectively.

Some of the features offered by AIOHTTP are:

  • asyncio
  • client
  • server

On the other hand, GraphQL provides the following key features:

  • Hierarchical
  • Product-centric
  • Client-specified queries

GraphQL is an open source tool with 11.7K GitHub stars and 753 GitHub forks. Here's a link to GraphQL's open source repository on GitHub.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of AIOHTTP
Pros of GraphQL
    Be the first to leave a pro
    • 75
      Schemas defined by the requests made by the user
    • 63
      Will replace RESTful interfaces
    • 62
      The future of API's
    • 49
      The future of databases
    • 13
      Self-documenting
    • 12
      Get many resources in a single request
    • 6
      Query Language
    • 6
      Ask for what you need, get exactly that
    • 3
      Fetch different resources in one request
    • 3
      Type system
    • 3
      Evolve your API without versions
    • 2
      Ease of client creation
    • 2
      GraphiQL
    • 2
      Easy setup
    • 1
      "Open" document
    • 1
      Fast prototyping
    • 1
      Supports subscription
    • 1
      Standard
    • 1
      Good for apps that query at build time. (SSR/Gatsby)
    • 1
      1. Describe your data
    • 1
      Better versioning
    • 1
      Backed by Facebook
    • 1
      Easy to learn

    Sign up to add or upvote prosMake informed product decisions

    Cons of AIOHTTP
    Cons of GraphQL
      Be the first to leave a con
      • 4
        Hard to migrate from GraphQL to another technology
      • 4
        More code to type.
      • 2
        Takes longer to build compared to schemaless.
      • 1
        No support for caching
      • 1
        All the pros sound like NFT pitches
      • 1
        No support for streaming
      • 1
        Works just like any other API at runtime
      • 1
        N+1 fetch problem
      • 1
        No built in security

      Sign up to add or upvote consMake informed product decisions

      - No public GitHub repository available -

      What is 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.

      What is GraphQL?

      GraphQL is a data query language and runtime designed and used at Facebook to request and deliver data to mobile and web apps since 2012.

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

      Jobs that mention AIOHTTP and GraphQL as a desired skillset
      What companies use AIOHTTP?
      What companies use GraphQL?
      See which teams inside your own company are using AIOHTTP or GraphQL.
      Sign up for StackShare EnterpriseLearn More

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

      What tools integrate with AIOHTTP?
      What tools integrate with GraphQL?

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

      Blog Posts

      GitHubDockerReact+17
      40
      36156
      GitHubPythonNode.js+47
      54
      72279
      What are some alternatives to AIOHTTP and GraphQL?
      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.
      Sanic
      Sanic is a Flask-like Python 3.5+ web server that's written to go fast. It's based on the work done by the amazing folks at magicstack. On top of being Flask-like, Sanic supports async request handlers.
      Flask
      Flask is intended for getting started very quickly and was developed with best intentions in mind.
      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.
      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.
      See all alternatives