Alternatives to Nancy logo

Alternatives to Nancy

Orleans, ExpressJS, Flask, Django REST framework, and Sinatra are the most popular alternatives and competitors to Nancy.
44
38
+ 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.1K 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. ...

  • hapi

    hapi

    hapi is a simple to use configuration-centric framework with built-in support for input validation, caching, authentication, and other essential facilities for building web applications and services. ...

  • Lumen

    Lumen

    Laravel Lumen is a stunningly fast PHP micro-framework for building web applications with expressive, elegant syntax. We believe development must be an enjoyable, creative experience to be truly fulfilling. Lumen attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as routing, database abstraction, queueing, and caching. ...

Nancy alternatives & related posts

Orleans logo

Orleans

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

    related Orleans posts

    ExpressJS logo

    ExpressJS

    16.9K
    13.7K
    1.5K
    Sinatra inspired web development framework for node.js -- insanely fast, flexible, and simple
    16.9K
    13.7K
    + 1
    1.5K
    PROS OF EXPRESSJS
    • 362
      Simple
    • 318
      Node.js
    • 235
      Javascript
    • 182
      High performance
    • 147
      Robust routing
    • 66
      Open source
    • 64
      Middlewares
    • 52
      Great community
    • 33
      Hybrid web applications
    • 8
      Well documented
    • 8
      Sinatra inspired
    • 4
      Isomorphic js.. superfast and easy
    • 3
      Rapid development
    • 2
      Socket connection
    • 2
      Npm
    • 2
      Event loop
    • 2
      Light weight
    • 2
      Resource available for learning
    • 1
      Callbacks
    • 1
      Data stream
    • 0
      Xxx
    CONS OF EXPRESSJS
    • 22
      Not python
    • 15
      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 · | 24 upvotes · 1.7M 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

    12.9K
    10.8K
    1.5K
    A microframework for Python based on Werkzeug, Jinja 2 and good intentions
    12.9K
    10.8K
    + 1
    1.5K
    PROS OF FLASK
    • 305
      Lightweight
    • 263
      Python
    • 210
      Minimal
    • 141
      Open source
    • 96
      Documentation
    • 64
      Easy to use
    • 53
      Easy to setup and get it going
    • 52
      Well designed
    • 46
      Easy to develop and maintain applications
    • 44
      Easy to get started
    • 15
      Beautiful code
    • 14
      Rapid development
    • 12
      Expressive
    • 12
      Powerful
    • 12
      Awesome
    • 11
      Speed
    • 10
      Love it
    • 9
      Simple to use
    • 9
      Flexibilty
    • 8
      For it flexibility
    • 8
      Easy to integrate
    • 8
      Get started quickly
    • 8
      Perfect for small to large projects with superb docs.
    • 7
      Productive
    • 7
      Flexibilty and easy to use
    • 7
      Customizable
    • 6
      Flask
    • 6
      Not JS
    • 5
      User friendly
    • 5
      Secured
    • 4
      Unopinionated
    • 0
      Secure
    CONS OF FLASK
    • 10
      Not JS
    • 7
      Context
    • 3
      Not fast

    related Flask posts

    James Man
    Software Engineer at Pinterest · | 40 upvotes · 756.7K views
    Shared insights
    on
    Flask
    React
    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.5K
    1.5K
    300
    Web APIs for Django
    1.5K
    1.5K
    + 1
    300
    PROS OF DJANGO REST FRAMEWORK
    • 64
      Browsable api
    • 63
      Easy to use
    • 53
      Great documentation
    • 49
      Customizable
    • 41
      Fast development
    • 9
      Easy to use, customizable, pluggable, serializer
    • 8
      Python
    • 5
      Django ORM
    • 4
      FastSerialize
    • 2
      Less code
    • 2
      Easy implementation
    • 0
      Dsasda
    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

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

      related Sinatra posts

      Koa logo

      Koa

      420
      380
      11
      Next generation web framework for node.js
      420
      380
      + 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 · 162.5K 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 · 126.8K views
        Shared insights
        on
        Fastify
        Koa
        ExpressJS

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

        See more
        hapi logo

        hapi

        379
        369
        84
        Server Framework for Node.js
        379
        369
        + 1
        84
        PROS OF HAPI
        • 25
          Makes me Hapi making REST APIs
        • 14
          Simpler than other REST libraries
        • 14
          Configuration
        • 13
          Modularization
        • 12
          Quality Driven Ecosystem
        • 5
          Easy testability
        • 1
          Better validation
        • 0
          Restify
        CONS OF HAPI
          Be the first to leave a con

          related hapi posts

          What is the best way to increase your income as a freelancer in 2019? What frameworks should be the best to learn? React Node.js Docker Kubernetes Sequelize Mongoose MongoDB ExpressJS hapi Based on trends I've picked up a JS full stack. If you need to work under startups you may replace React with Vue.js . If you want to work in outsourcing Angular 2+ may be better.

          What is your opinion?

          See more
          Lumen logo

          Lumen

          357
          524
          152
          The stunningly fast PHP micro-framework by Laravel
          357
          524
          + 1
          152
          PROS OF LUMEN
          • 33
            API
          • 25
            Microframework
          • 19
            MVC
          • 16
            PHP
          • 12
            Open source
          • 11
            Eloquent
          • 10
            Restful & fast framework
          • 7
            Illuminate support
          • 7
            Composer
          • 4
            Brother of laravel and fast
          • 4
            Easy to learn
          • 4
            Fast
          CONS OF LUMEN
          • 3
            Not fast
          • 2
            PHP
          • 1
            Not fast with MongoDB

          related Lumen posts

          Tassanai Singprom

          This is my stack in Application & Data

          JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

          My Utilities Tools

          Google Analytics Postman Elasticsearch

          My Devops Tools

          Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

          My Business Tools

          Slack

          See more
          Aimad Quouninich

          Hello everyone,

          I have a final-study project, and I'm responsible for making decisions for what frameworks to use (both front-end and back-end) and the software architecture to adapt.

          The project is a web application for a concrete company. The main goal is to calculate what is called OEE (Overall Equipment Effectiveness), meaning simply the efficiency of the machine. The calculation and display of OEE will be in real-time, meaning that this rate will be updated every two minutes, and it will appear in a graph. Also, we have the state of the machines to display whether the machines are working just fine or there is some problem.

          This will be done using IoT, meaning that important data will be sent from the machine to the web application that I will create via the API (someone else will be responsible for this matter). Of course, the application will include employees, factories, as well as machines, ... etc.

          The most important thing in the application is real-time performance monitoring of machines and the OEE.

          A real example of what we want to do => https://evocon.com/

          I choose to use Laravel because : - This type of applications could be implemented by Laravel - Me and my colleague have some knowledge and practice with this framework (choosing other technologies like Node.js means a huge learning curve) - Easy documentation and abandon tutorials

          The only reason why I choose Vue.js because It goes well with Laravel (from what I have learned).

          The second important question, which software architecture should I adapt ? should I use Microservice Architecture or the normal and well-known Monolithic Architecture? I know the benefits and disadvantages of the first and second methods, but I do not want to make a wrong decision.

          If I choose microservice for this project, I will use Lumen (PHP Micro-Framework By Laravel).

          Should I use micro-frontend as well? Like VuMS, or it's not necessary for this project?

          I don't think that the reasons to choose Laravel are enough, so I want to understand the obstacles that I may face during the development.

          In the end, I decided to ask and take expert opinions.

          NOTE: this web application will be used by other companies, like in the case of evocon.

          If there are tips and things that I must know to accomplish this project, please mention them.

          Thank you very much.

          See more