Alternatives to LoopBack logo

Alternatives to LoopBack

DreamFactory, StrongLoop, Parse-Server, NestJS, and ExpressJS are the most popular alternatives and competitors to LoopBack.
243
437
+ 1
26

What is LoopBack and what are its top alternatives?

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

Top Alternatives to LoopBack

  • DreamFactory

    DreamFactory

    DreamFactory is an open source REST API backend for mobile, web, and IoT applications. It provides RESTful web services with pre-built connectors to SQL, NoSQL, file storage systems, and web services. It's secure, reusable, and offers live API documentation. ...

  • StrongLoop

    StrongLoop

    It is an American company working with Node.js to create and support StrongLoop Suite, a Mobile API Tier. StrongLoop employs two members of the Node.js Technical Steering Committee. IBM & StrongLoop contribute to and support Open-Source options for the API developer community, such as LoopBack, API Microgateway, and Open API Spec. ...

  • Parse-Server

    Parse-Server

    A Parse.com API compatible router package for Express. Read the announcement blog post here: http://blog.parse.com/announcements/introducing-parse-server-and-the-database-migration-tool/. Read the migration guide here: https://parse.com/docs/server/guide#migrating ...

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

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

LoopBack alternatives & related posts

DreamFactory logo

DreamFactory

37
71
20
Open source REST API backend for mobile, web, and IoT applications.
37
71
+ 1
20
PROS OF DREAMFACTORY
  • 6
    Restful
  • 6
    Easy setup
  • 4
    SQL Rest APIS
  • 2
    Love this to easily build API's
  • 1
    Great customer support
  • 1
    Multi Platform
CONS OF DREAMFACTORY
    Be the first to leave a con

    related DreamFactory posts

    StrongLoop logo

    StrongLoop

    11
    29
    0
    Develop, manage and scale REST APIs with Node.js
    11
    29
    + 1
    0
    PROS OF STRONGLOOP
      Be the first to leave a pro
      CONS OF STRONGLOOP
        Be the first to leave a con

        related StrongLoop posts

        Parse-Server logo

        Parse-Server

        167
        207
        29
        Parse-compatible API server module for Node/Express
        167
        207
        + 1
        29
        PROS OF PARSE-SERVER
        • 12
          Open Source
        • 6
          Well documented
        • 4
          Easy setup, easy api, Fast,more platforms,realtime
        • 2
          JSON
        • 2
          No vendor lock-in
        • 2
          Backed by People
        • 1
          Friendly contributor community
        CONS OF PARSE-SERVER
        • 1
          No guarantee (comes as is)

        related Parse-Server posts

        NestJS logo

        NestJS

        977
        1.4K
        258
        A progressive Node.js framework for building efficient and scalable server-side applications by @kammysliwiec.
        977
        1.4K
        + 1
        258
        PROS OF NESTJS
        • 43
          Powerful but super friendly to work with
        • 36
          Fast development
        • 33
          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.8M 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
        ExpressJS logo

        ExpressJS

        18.2K
        14K
        1.5K
        Sinatra inspired web development framework for node.js -- insanely fast, flexible, and simple
        18.2K
        14K
        + 1
        1.5K
        PROS OF EXPRESSJS
        • 364
          Simple
        • 319
          Node.js
        • 235
          Javascript
        • 184
          High performance
        • 148
          Robust routing
        • 66
          Open source
        • 66
          Middlewares
        • 53
          Great community
        • 33
          Hybrid web applications
        • 9
          Well documented
        • 8
          Sinatra inspired
        • 5
          Isomorphic js.. superfast and easy
        • 4
          Rapid development
        • 2
          Socket connection
        • 2
          Npm
        • 2
          Event loop
        • 2
          Light weight
        • 2
          Resource available for learning
        • 1
          Data stream
        • 1
          Callbacks
        • 1
          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.8M 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

        13.2K
        11K
        1.5K
        A microframework for Python based on Werkzeug, Jinja 2 and good intentions
        13.2K
        11K
        + 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
        • 16
          Beautiful code
        • 14
          Rapid development
        • 12
          Awesome
        • 12
          Expressive
        • 12
          Powerful
        • 11
          Speed
        • 10
          Love it
        • 9
          Flexibilty
        • 9
          Simple to use
        • 8
          Perfect for small to large projects with superb docs.
        • 8
          Easy to integrate
        • 8
          Get started quickly
        • 8
          For it flexibility
        • 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 · 775.8K 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

        581
        451
        212
        Classy web-development dressed in a DSL
        581
        451
        + 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