Alternatives to hapi logo

Alternatives to hapi

Koa, NestJS, Restify, Fastify, and LoopBack are the most popular alternatives and competitors to hapi.
381
369
+ 1
84

What is hapi and what are its top alternatives?

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.
hapi is a tool in the Microframeworks (Backend) category of a tech stack.
hapi is an open source tool with 13.3K GitHub stars and 1.3K GitHub forks. Here’s a link to hapi's open source repository on GitHub

Top Alternatives to hapi

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

  • NestJS

    NestJS

    Nest is a framework for building efficient, scalable Node.js server-side applications. It uses progressive JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming). Under the hood, Nest makes use of Express, but also, provides compatibility with a wide range of other libraries, like e.g. Fastify, allowing for easy use of the myriad third-party plugins which are available. ...

  • Restify

    Restify

    A Node.js web service framework optimized for building semantically correct RESTful web services ready for production use at scale. it optimizes for introspection and performance. ...

  • Fastify

    Fastify

    Fastify is a web framework highly focused on speed and low overhead. It is inspired from Hapi and Express and as far as we know, it is one of the fastest web frameworks in town. Use Fastify can increase your throughput up to 100%. ...

  • LoopBack

    LoopBack

    A highly-extensible, open-source Node.js framework that enables you to create dynamic end-to-end REST APIs with little or no coding. Connect to multiple data sources, write business logic in Node.js, glue on top of your existing services and data, connect using JS, iOS & Android SDKs. ...

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

hapi alternatives & related posts

Koa logo

Koa

443
380
11
Next generation web framework for node.js
443
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.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 · 127K 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
    NestJS logo

    NestJS

    938
    1.3K
    256
    A progressive Node.js framework for building efficient and scalable server-side applications by @kammysliwiec.
    938
    1.3K
    + 1
    256
    PROS OF NESTJS
    • 43
      Powerful but super friendly to work with
    • 35
      Fast development
    • 32
      Easy to understand documentation
    • 29
      Angular style syntax for the backend
    • 28
      NodeJS ecosystem
    • 23
      Its easy to understand since it follows angular syntax
    • 18
      Typescript
    • 12
      Good architecture
    • 11
      Integrates with Narwhal Extensions
    • 9
      Typescript makes it well integrated in vscode
    • 7
      Graphql support easy
    • 5
      Agnosticism
    • 4
      Easily integrate with others external extensions
    CONS OF NESTJS
    • 4
      Difficult to debug
    • 4
      User base is small. Less help on Stackoverflow
    • 3
      Angular-like architecture
    • 2
      Updates with breaking changes
    • 1
      Unstable
    • 1
      Frontend in backend
    • 1
      Javascript

    related NestJS 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
    Slimane Deb

    I am currently planning to build a project from scratch. I will be using Angular as front-end framework, but for the back-end I am not sure which framework to use between Spring Boot and NestJS. I have worked with Spring Boot before, but my new project contains a lot of I/O operations, in fact it will show a daily report. I thought about the new Spring Web Reactive Framework but given the idea that Node.js is the most popular on handling non blocking I/O I am planning to start learning NestJS since it is based on Angular philosophy and TypeScript which I am familiar with. Looking forward to hear from you dear Community.

    See more
    Restify logo

    Restify

    65
    102
    1
    node.js REST framework specifically meant for web service APIs
    65
    102
    + 1
    1
    PROS OF RESTIFY
    • 1
      Semantically REST correctness
    CONS OF RESTIFY
      Be the first to leave a con

      related Restify posts

      Fastify logo

      Fastify

      162
      267
      70
      Fast and low overhead web framework, for Node.js
      162
      267
      + 1
      70
      PROS OF FASTIFY
      • 15
        Performance
      • 9
        Easy to use
      • 8
        Lightweight
      • 8
        Middleware
      • 6
        Open source
      • 4
        Highly customizable
      • 3
        Built-in Typescript support
      • 3
        Mature
      • 3
        Schema based
      • 3
        Decorators
      • 3
        Developer friendly
      • 3
        Plugins
      • 2
        Low overhead
      CONS OF FASTIFY
        Be the first to leave a con

        related Fastify posts

        Paul Whittemore
        Developer and Owner at Appurist Software · | 15 upvotes · 664.3K views

        I'm building most projects using: Server: either Fastify (all projects going forward) or ExpressJS on Node.js (existing, previously) on the server side, and Client app: either Vuetify (currently) or Quasar Framework (going forward) on Vue.js with vuex on Electron for the UI to deliver both web-based and desktop applications for multiple platforms.

        The direct support for Android and iOS in Quasar Framework will make it my go-to client UI platform for any new client-side or web work. On the server, I'll probably use Fastly for all my server work, unless I get into Go more in the future.

        Update: The mobile support in Quasar is not a sufficiently compelling reason to move me from Vuetify. I have decided to stick with Vuetify for a UI for Vue, as it is richer in components and enables a really great-looking professional result. For mobile platforms, I will just use Cordova to wrap the Vue+Vuetify app for mobile, and Electron to wrap it for desktop platforms.

        See more
        Paul Whittemore
        Developer and Owner at Appurist Software · | 1 upvote · 127K 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
        LoopBack logo

        LoopBack

        242
        435
        21
        Build modern API applications that require complex integrations
        242
        435
        + 1
        21
        PROS OF LOOPBACK
        • 8
          Need a nodejs ReST-API, DB, AAA, Swagger? Then loopback
        • 8
          Easy Database Migration
        • 5
          Code generator
        • 3
          The future of API's
        • 2
          GraphQL
        CONS OF LOOPBACK
        • 7
          Community is slow
        • 1
          Backward compatibility

        related LoopBack posts

        Samuel Olugbemi
        Software Engineer at Payzone UK · | 6 upvotes · 100.5K views
        Shared insights
        on
        LoopBack
        ExpressJS
        at

        I use LoopBack because it is: * It is truly and Unbelievably Extensible * it is default integrated with OpenAPI (Swagger) Spec Driven REST API * I write lesser codes, because most of the user stories have been covered using the code generation * It's documentation is more compact and well detailed than ExpressJS * It is very easy to learn, hence you can build a basic Rest API App in minutes * It has built in NPM packages required to build my Rest API which saves me time on installation and configuration * The Datasource/Service/Controller concept is just Brilliant (that's mostly all you need to get your app speaking with an External API services) * The support for SOAP and Rest API services is amazing!

        See more
        Shared insights
        on
        NestJS
        Jest
        LoopBack

        We inherited this project and the backend is using LoopBack v3. I haven't taken a look at Loopback.io v4, but I'm planning to replace it. The reason being is that Loopback v3 documentation is a bit confusing and we are having trouble packaging the build using Webpack. Not to mention, integrating unit tests (latest Jest).

        I still think Loopback is a great tool, but their documentation is really "messy" and hard to navigate through. There's also a constraint of time from our side. So what's the best option out there?

        Should I try upgrading to Loopback v4, or trying other stuff? (i.e. NestJS)

        Thanks!

        See more
        ExpressJS logo

        ExpressJS

        17.8K
        13.7K
        1.5K
        Sinatra inspired web development framework for node.js -- insanely fast, flexible, and simple
        17.8K
        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

        13K
        10.8K
        1.5K
        A microframework for Python based on Werkzeug, Jinja 2 and good intentions
        13K
        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 · 757.5K 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