Alternatives to Nancy logo

Alternatives to Nancy

Orleans, ExpressJS, Flask, Django REST framework, and Sinatra are the most popular alternatives and competitors to Nancy.
46
43
+ 1
7

What is Nancy and what are its top alternatives?

Nancy is a lightweight, low-ceremony, framework for building HTTP based services on .NET Framework/Core and Mono. The goal of the framework is to stay out of the way as much as possible and provide a super-duper-happy-path to all interactions.
Nancy is a tool in the Microframeworks (Backend) category of a tech stack.
Nancy is an open source tool with 7.2K GitHub stars and 1.5K GitHub forks. Here’s a link to Nancy's open source repository on GitHub

Top Alternatives to Nancy

  • Orleans
    Orleans

    Orleans is a framework that provides a straightforward approach to building distributed high-scale computing applications, without the need to learn and apply complex concurrency or other scaling patterns. It was created by Microsoft Research and designed for use in the cloud. ...

  • 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. ...

  • Flask
    Flask

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

  • Django REST framework
    Django REST framework

    It is a powerful and flexible toolkit that makes it easy to build Web APIs.

  • Sinatra
    Sinatra

    Sinatra is a DSL for quickly creating web applications in Ruby with minimal effort. ...

  • Koa
    Koa

    Koa aims to be a smaller, more expressive, and more robust foundation for web applications and APIs. Through leveraging generators Koa allows you to ditch callbacks and greatly increase error-handling. Koa does not bundle any middleware. ...

  • FastAPI
    FastAPI

    It is a modern, fast (high-performance), web framework for building APIs with Python 3.6+ based on standard Python type hints. ...

  • TypeORM
    TypeORM

    It supports both Active Record and Data Mapper patterns, unlike all other JavaScript ORMs currently in existence, which means you can write high quality, loosely coupled, scalable, maintainable applications the most productive way. ...

Nancy alternatives & related posts

Orleans logo

Orleans

45
103
26
An approach to building distributed applications in .NET
45
103
+ 1
26
PROS OF ORLEANS
  • 4
    Akka.net alternative
  • 3
    Open source
  • 3
    Distributed high-scale computing applications
  • 2
    Virtual Actor Model
  • 2
    Async/Await
  • 2
    Cross Platform
  • 2
    Scalable
  • 2
    Distributed Locking
  • 2
    Objects
  • 2
    Distributed ACID Transactions
  • 2
    Fast
CONS OF ORLEANS
    Be the first to leave a con

    related Orleans posts

    ExpressJS logo

    ExpressJS

    23.5K
    19.2K
    1.6K
    Sinatra inspired web development framework for node.js -- insanely fast, flexible, and simple
    23.5K
    19.2K
    + 1
    1.6K
    PROS OF EXPRESSJS
    • 375
      Simple
    • 331
      Node.js
    • 241
      Javascript
    • 192
      High performance
    • 150
      Robust routing
    • 71
      Middlewares
    • 70
      Open source
    • 57
      Great community
    • 36
      Hybrid web applications
    • 13
      Well documented
    • 9
      Sinatra inspired
    • 8
      Rapid development
    • 7
      Isomorphic js.. superfast and easy
    • 5
      Socket connection
    • 5
      Light weight
    • 4
      Npm
    • 4
      Resource available for learning
    • 3
      Event loop
    • 3
      Callbacks
    • 2
      Data stream
    CONS OF EXPRESSJS
    • 26
      Not python
    • 17
      Overrated
    • 14
      No multithreading
    • 7
      Javascript
    • 5
      Not fast
    • 2
      Easily Insecure for Novices

    related ExpressJS posts

    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 26 upvotes · 2.9M 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
    Flask logo

    Flask

    16.2K
    13.8K
    1.5K
    A microframework for Python based on Werkzeug, Jinja 2 and good intentions
    16.2K
    13.8K
    + 1
    1.5K
    PROS OF FLASK
    • 315
      Lightweight
    • 272
      Python
    • 214
      Minimal
    • 146
      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
    • 17
      Rapid development
    • 14
      Powerful
    • 13
      Expressive
    • 12
      Awesome
    • 12
      Flexibilty
    • 11
      Customizable
    • 11
      Simple to use
    • 11
      Love it
    • 11
      Speed
    • 11
      Get started quickly
    • 10
      Easy to integrate
    • 9
      Perfect for small to large projects with superb docs.
    • 9
      For it flexibility
    • 8
      Flexibilty and easy to use
    • 8
      Productive
    • 7
      Flask
    • 6
      User friendly
    • 6
      Not JS
    • 5
      Secured
    • 4
      Unopinionated
    • 1
      Orm
    • 1
      Secure
    CONS OF FLASK
    • 10
      Not JS
    • 7
      Context
    • 5
      Not fast
    • 1
      Don't has many module as in spring

    related Flask posts

    James Man
    Software Engineer at Pinterest · | 44 upvotes · 1M 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
    Django REST framework logo

    Django REST framework

    1.8K
    1.8K
    304
    Web APIs for Django
    1.8K
    1.8K
    + 1
    304
    PROS OF DJANGO REST FRAMEWORK
    • 65
      Easy to use
    • 64
      Browsable api
    • 53
      Great documentation
    • 49
      Customizable
    • 41
      Fast development
    • 9
      Easy to use, customizable, pluggable, serializer
    • 8
      Python
    • 6
      Django ORM
    • 5
      FastSerialize
    • 2
      Less code
    • 2
      Easy implementation
    CONS OF DJANGO REST FRAMEWORK
    • 2
      Bad documentation
    • 2
      Reimplements Django functionality
    • 1
      No support for URL Namespaces
    • 0
      Bad CSRF handling

    related Django REST framework posts

    Tim Abbott

    Zulip has been powered by Django since the very early days of its development with Django 1.4, back in 2012. As a reasonably mature web application with significant scale, we're at the stage in many companies' development where one starts to rip out more and more of the web framework to optimize things or just make them work the way we want. (E.g. while I was at Dropbox in early 2016, we discovered we only had about 600 lines of code left from the original Pylons framework that actually ran).

    One of the things that has been really fantastic about Django is that we're still happily using it for the vast majority of code in the project, and every time Django comes out with a new release, I read the changelog and get excited about several improvements that actually make my life better. While Django has made some design decisions that I don't agree with (e.g. I'm not a fan of Django REST framework, and think it makes life more difficult), Django also makes it easy to do your own thing, which we've done to great effect (see the linked article for details on our has_request_variables framework).

    Overall I think we've gotten a ton of value out of Python and Django and would recommend it to anyone starting a new full-featured web application project today.

    See more

    Hi

    I’ve been using Django for the last year on and off to do my backend API. I’m getting a bit frustrated with the Django REST framework with the setup of the serializers and Django for the lack of web sockets. I’m considering either Spring or .NET Core. I’m familiar with Kotlin and C# but I’ve not built any substantial projects with them. I like OOP, building a desktop app, web API, and also the potential to get a job in the future or building a tool at work to manage my documents, dashboard and processes point cloud data.

    I’m familiar with c/cpp, TypeScript.

    I would love your insights on where I should go.

    See more
    Sinatra logo

    Sinatra

    634
    476
    212
    Classy web-development dressed in a DSL
    634
    476
    + 1
    212
    PROS OF SINATRA
    • 65
      Lightweight
    • 50
      Simple
    • 35
      Open source
    • 20
      Ruby
    • 13
      Great ecosystem of tools
    • 10
      Ease of use
    • 8
      If you know http you know sinatra
    • 5
      Large Community
    • 5
      Fast
    • 1
      Flexibilty and easy to use
    CONS OF SINATRA
      Be the first to leave a con

      related Sinatra posts

      Koa logo

      Koa

      490
      442
      11
      Next generation web framework for node.js
      490
      442
      + 1
      11
      PROS OF KOA
      • 5
        Async/Await
      • 5
        JavaScript
      • 1
        REST API
      CONS OF KOA
        Be the first to leave a con

        related Koa posts

        Antonio Kobashikawa
        Web developer | Blogger | Freelancer at Rulo Kobashikawa · | 6 upvotes · 204.7K views

        We are using Node.js and ExpressJS to build a REST services that is middleware of a legacy system. MongoDB as database. Vue.js helps us to make rapid UI to test use cases. Frontend is build for mobile with Ionic . We like using JavaScript and ES6 .

        I think next step could be to use Koa but I am not sure.

        See more
        Paul Whittemore
        Developer and Owner at Appurist Software · | 1 upvote · 173.3K views
        Shared insights
        on
        FastifyFastifyKoaKoaExpressJSExpressJS

        Will base most server-side APIs on Fastify . Smaller, faster, easier. Faster than Koa; and twice as fast as ExpressJS.

        See more
        FastAPI logo

        FastAPI

        455
        312
        20
        A high performance, easy to learn, fast to code, ready for production web framework
        455
        312
        + 1
        20
        PROS OF FASTAPI
        • 5
          Python
        • 5
          Rapid Development
        • 3
          Super Lightweight
        • 3
          Open Source
        • 3
          Documentation
        • 1
          Fast performance
        CONS OF FASTAPI
          Be the first to leave a con

          related FastAPI posts

          TypeORM logo

          TypeORM

          410
          668
          62
          An ORM that can run in NodeJS and others
          410
          668
          + 1
          62
          PROS OF TYPEORM
          • 25
            Typescript
          • 9
            Supports MySQL, PostgreSQL, MariaDB, SQLite, MS SQL Ser
          • 8
            Easy setup
          • 7
            Works in NodeJS, Browser, Ionic, Cordova and Electron p
          • 6
            Support MySQL & MariaDB, PostgreSQL, MSSQL, Sqlite
          • 5
            Promise Based
          • 2
            Cons of TypeORM
          CONS OF TYPEORM
          • 5
            Completely abandoned by its creator
          • 3
            Too complex for what it does
          • 2
            Doesn't really support native javascript
          • 1
            Cannot use query on any relation
          • 1
            Not proper/real type safety

          related TypeORM posts

          Simon Reymann
          Senior Fullstack Developer at QUANTUSflow Software GmbH · | 26 upvotes · 2.9M 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
          Martin Johannesson
          Senior Software Developer at IT Minds · | 14 upvotes · 491.6K views

          At IT Minds we create customized internal or #B2B web and mobile apps. I have a go to stack that I pitch to our customers consisting of 3 core areas. 1) A data core #backend . 2) A micro #serverless #backend. 3) A user client #frontend.

          For the Data Core I create a backend using TypeScript Node.js and with TypeORM connecting to a PostgreSQL Exposing an action based api with Apollo GraphQL

          For the micro serverless backend, which purpose is verification for authentication, autorization, logins and the likes. It is created with Next.js api pages. Using MongoDB to store essential information, caching etc.

          Finally the frontend is built with React using Next.js , TypeScript and @Apollo. We create the frontend as a PWA and have a AMP landing page by default.

          See more