Alternatives to hapi logo

Alternatives to hapi

Koa, NestJS, Restify, Fastify, and LoopBack are the most popular alternatives and competitors to hapi.
409
431
+ 1
87

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 GitHub stars and 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

563
457
12
Next generation web framework for node.js
563
457
+ 1
12
PROS OF KOA
  • 6
    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 · 217.9K 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 · 187.9K 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
    NestJS logo

    NestJS

    2K
    2.6K
    295
    A progressive Node.js framework for building efficient and scalable server-side applications by @kammysliwiec.
    2K
    2.6K
    + 1
    295
    PROS OF NESTJS
    • 50
      Powerful but super friendly to work with
    • 38
      Fast development
    • 37
      Easy to understand documentation
    • 33
      Angular style syntax for the backend
    • 30
      NodeJS ecosystem
    • 28
      Typescript
    • 25
      Its easy to understand since it follows angular syntax
    • 15
      Good architecture
    • 11
      Typescript makes it well integrated in vscode
    • 11
      Integrates with Narwhal Extensions
    • 7
      Graphql support easy
    • 6
      Agnosticism
    • 4
      Easily integrate with others external extensions
    CONS OF NESTJS
    • 9
      User base is small. Less help on Stackoverflow
    • 8
      Difficult to debug
    • 4
      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 · | 26 upvotes · 3.3M 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
    Jan Vlnas
    Developer Advocate at Superface · | 12 upvotes · 15.8K views

    Our framework of choice for backend at Superface is NestJS. We also use AppSignal for APM and error tracking. While AppSignal provides some basic integration for Node.js, getting the monitoring to work with Nest was a bit tricky. Check out our blog post on Integrating AppSignal APM with NestJS how we made it work.

    See more
    Restify logo

    Restify

    65
    123
    1
    node.js REST framework specifically meant for web service APIs
    65
    123
    + 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

      300
      457
      90
      Fast and low overhead web framework, for Node.js
      300
      457
      + 1
      90
      PROS OF FASTIFY
      • 20
        Performance
      • 12
        Easy to use
      • 11
        Lightweight
      • 9
        Middleware
      • 8
        Open source
      • 6
        Highly customizable
      • 4
        Decorators
      • 4
        Developer friendly
      • 4
        Built-in Typescript support
      • 3
        Plugins
      • 3
        Mature
      • 3
        Schema based
      • 3
        Low overhead
      CONS OF FASTIFY
      • 1
        Small community

      related Fastify posts

      Paul Whittemore
      Developer and Owner at Appurist Software · | 15 upvotes · 915.2K 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 · 187.9K 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
      LoopBack logo

      LoopBack

      280
      545
      33
      Build modern API applications that require complex integrations
      280
      545
      + 1
      33
      PROS OF LOOPBACK
      • 11
        Need a nodejs ReST-API, DB, AAA, Swagger? Then loopback
      • 9
        Easy Database Migration
      • 6
        Code generator
      • 4
        The future of API's
      • 2
        GraphQL
      • 1
        Typescript
      CONS OF LOOPBACK
      • 7
        Community is slow
      • 1
        Backward compatibility

      related LoopBack posts

      Shared insights
      on
      NestJSNestJSJestJestLoopBackLoopBack

      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
      Samuel Olugbemi
      Software Engineer at Payzone UK · | 6 upvotes · 167.2K views
      Shared insights
      on
      LoopBackLoopBackExpressJSExpressJS
      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
      ExpressJS logo

      ExpressJS

      27.1K
      20.8K
      1.6K
      Sinatra inspired web development framework for node.js -- insanely fast, flexible, and simple
      27.1K
      20.8K
      + 1
      1.6K
      PROS OF EXPRESSJS
      • 378
        Simple
      • 333
        Node.js
      • 242
        Javascript
      • 192
        High performance
      • 150
        Robust routing
      • 71
        Middlewares
      • 70
        Open source
      • 57
        Great community
      • 37
        Hybrid web applications
      • 13
        Well documented
      • 9
        Sinatra inspired
      • 9
        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
      • 27
        Not python
      • 17
        Overrated
      • 14
        No multithreading
      • 9
        Javascript
      • 5
        Not fast
      • 2
        Easily Insecure for Novices

      related ExpressJS posts

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

      17.4K
      14.9K
      1.6K
      A microframework for Python based on Werkzeug, Jinja 2 and good intentions
      17.4K
      14.9K
      + 1
      1.6K
      PROS OF FLASK
      • 319
        Lightweight
      • 275
        Python
      • 217
        Minimal
      • 149
        Open source
      • 100
        Documentation
      • 69
        Easy to use
      • 55
        Well designed
      • 55
        Easy to setup and get it going
      • 51
        Easy to develop and maintain applications
      • 48
        Easy to get started
      • 22
        Beautiful code
      • 19
        Rapid development
      • 16
        Powerful
      • 15
        Expressive
      • 14
        Customizable
      • 14
        Flexibilty
      • 14
        Simple to use
      • 13
        Love it
      • 13
        Get started quickly
      • 13
        Awesome
      • 12
        Speed
      • 11
        Perfect for small to large projects with superb docs.
      • 11
        Easy to integrate
      • 10
        For it flexibility
      • 9
        Productive
      • 9
        Flexibilty and easy to use
      • 8
        Flask
      • 8
        Not JS
      • 7
        User friendly
      • 6
        Secured
      • 5
        Unopinionated
      • 3
        Orm
      • 2
        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 · 1.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.9K
      304
      Web APIs for Django
      1.8K
      1.9K
      + 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

      Arjiv Jivithkumar
      Junior Product Manager at Vozz · | 13 upvotes · 44K views

      Hey everyone! I'm planning on building a personal project - this will be my first full-stack project and will be a web app.

      The way it will work is that users will be able to post groups. This can be, groups for studying or groups for work, etc. They can also set the desired group size (e.g. limit the group to 3 members). Other users can then join said group - once the group is full, it will automatically close.

      What tech stack would you all recommend for this? I have a lot of experience with Django so maybe that will be good for the backend but I'm not sure where to go from there. I've heard using the Django REST framework with a React frontend might be good. Always open to learning new technologies and thanks in advance!

      See more

      I am planning on creating an application using the following tech-stack. Vue.js (TypeScript) for the front-end, Django (specifically Django REST framework) for the server-side work, and using PostgreSQL as the database. Is there any reason NOT to use this tech stack mentioned or are there better options? Without giving away too much info, my app will be logging information from the user, displaying this information, setting goals, displaying visual graphs, a friend system where you can add other people etc...

      See more