Alternatives to StrongLoop logo

Alternatives to StrongLoop

PM2, LoopBack, DreamFactory, GraphQL, and hapi are the most popular alternatives and competitors to StrongLoop.
14
33
+ 1
0

What is StrongLoop and what are its top alternatives?

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

Top Alternatives to StrongLoop

  • PM2
    PM2

    Production process manager for Node.js apps with a built-in load balancer

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

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

  • GraphQL
    GraphQL

    GraphQL is a data query language and runtime designed and used at Facebook to request and deliver data to mobile and web apps since 2012. ...

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

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

StrongLoop alternatives & related posts

PM2 logo

PM2

571
373
24
Ease-to-use Node.js process manager, like forever
571
373
+ 1
24
PROS OF PM2
  • 12
    Reliable
  • 9
    Easy to manage
  • 3
    Easy to use
CONS OF PM2
  • 7
    Memory leak

related PM2 posts

LoopBack logo

LoopBack

288
556
33
Build modern API applications that require complex integrations
288
556
+ 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

We have an existing (Apis only) Rails backend, that by default follows the MVC pattern, (at peaks of 700 requests a second). I am tasked with making the same (read-heavy) application in any JavaScript framework. I was advised to follow the MVC structure. So I am considering these 3 ( Sails.js, LoopBack, NestJS). I get that sails is closest to rails, but that's not particularly a priority.

See more
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
DreamFactory logo

DreamFactory

40
82
21
Open source REST API backend for mobile, web, and IoT applications.
40
82
+ 1
21
PROS OF DREAMFACTORY
  • 6
    Restful
  • 6
    Easy setup
  • 5
    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

    GraphQL logo

    GraphQL

    33.8K
    27.1K
    310
    A data query language and runtime
    33.8K
    27.1K
    + 1
    310
    PROS OF GRAPHQL
    • 75
      Schemas defined by the requests made by the user
    • 63
      Will replace RESTful interfaces
    • 62
      The future of API's
    • 49
      The future of databases
    • 13
      Self-documenting
    • 12
      Get many resources in a single request
    • 6
      Query Language
    • 6
      Ask for what you need, get exactly that
    • 3
      Fetch different resources in one request
    • 3
      Type system
    • 3
      Evolve your API without versions
    • 2
      Ease of client creation
    • 2
      GraphiQL
    • 2
      Easy setup
    • 1
      "Open" document
    • 1
      Fast prototyping
    • 1
      Supports subscription
    • 1
      Standard
    • 1
      Good for apps that query at build time. (SSR/Gatsby)
    • 1
      1. Describe your data
    • 1
      Better versioning
    • 1
      Backed by Facebook
    • 1
      Easy to learn
    CONS OF GRAPHQL
    • 4
      Hard to migrate from GraphQL to another technology
    • 4
      More code to type.
    • 2
      Takes longer to build compared to schemaless.
    • 1
      No support for caching
    • 1
      All the pros sound like NFT pitches
    • 1
      No support for streaming
    • 1
      Works just like any other API at runtime
    • 1
      N+1 fetch problem
    • 1
      No built in security

    related GraphQL posts

    Shared insights
    on
    Node.jsNode.jsGraphQLGraphQLMongoDBMongoDB

    I just finished the very first version of my new hobby project: #MovieGeeks. It is a minimalist online movie catalog for you to save the movies you want to see and for rating the movies you already saw. This is just the beginning as I am planning to add more features on the lines of sharing and discovery

    For the #BackEnd I decided to use Node.js , GraphQL and MongoDB:

    1. Node.js has a huge community so it will always be a safe choice in terms of libraries and finding solutions to problems you may have

    2. GraphQL because I needed to improve my skills with it and because I was never comfortable with the usual REST approach. I believe GraphQL is a better option as it feels more natural to write apis, it improves the development velocity, by definition it fixes the over-fetching and under-fetching problem that is so common on REST apis, and on top of that, the community is getting bigger and bigger.

    3. MongoDB was my choice for the database as I already have a lot of experience working on it and because, despite of some bad reputation it has acquired in the last months, I still believe it is a powerful database for at least a very long list of use cases such as the one I needed for my website

    See more
    Nick Rockwell
    SVP, Engineering at Fastly · | 46 upvotes · 3.2M views

    When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

    So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

    React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

    Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

    See more
    hapi logo

    hapi

    436
    452
    87
    Server Framework for Node.js
    436
    452
    + 1
    87
    PROS OF HAPI
    • 27
      Makes me Hapi making REST APIs
    • 14
      Simpler than other REST libraries
    • 14
      Configuration
    • 13
      Quality Driven Ecosystem
    • 13
      Modularization
    • 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
      ExpressJS logo

      ExpressJS

      33.9K
      23.2K
      1.6K
      Sinatra inspired web development framework for node.js -- insanely fast, flexible, and simple
      33.9K
      23.2K
      + 1
      1.6K
      PROS OF EXPRESSJS
      • 380
        Simple
      • 336
        Node.js
      • 244
        Javascript
      • 193
        High performance
      • 152
        Robust routing
      • 73
        Middlewares
      • 71
        Open source
      • 59
        Great community
      • 37
        Hybrid web applications
      • 16
        Well documented
      • 9
        Rapid development
      • 9
        Sinatra inspired
      • 7
        Socket connection
      • 7
        Isomorphic js.. superfast and easy
      • 5
        Light weight
      • 4
        Resource available for learning
      • 4
        Npm
      • 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 · | 27 upvotes · 4.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

      18.9K
      15.8K
      82
      A microframework for Python based on Werkzeug, Jinja 2 and good intentions
      18.9K
      15.8K
      + 1
      82
      PROS OF FLASK
      • 14
        Flexibilty
      • 10
        For it flexibility
      • 9
        Flexibilty and easy to use
      • 8
        Flask
      • 7
        User friendly
      • 6
        Secured
      • 5
        Unopinionated
      • 3
        Orm
      • 2
        Secure
      • 1
        Beautiful code
      • 1
        Easy to get started
      • 1
        Easy to develop and maintain applications
      • 1
        Not JS
      • 1
        Easy to use
      • 1
        Documentation
      • 1
        Python
      • 1
        Minimal
      • 1
        Lightweight
      • 1
        Easy to setup and get it going
      • 1
        Perfect for small to large projects with superb docs.
      • 1
        Easy to integrate
      • 1
        Speed
      • 1
        Get started quickly
      • 1
        Customizable
      • 1
        Simple to use
      • 1
        Powerful
      • 1
        Rapid development
      • 0
        Open source
      • 0
        Well designed
      • 0
        Productive
      • 0
        Awesome
      • 0
        Expressive
      • 0
        Love it
      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 · | 45 upvotes · 2.7M 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.9K
      2K
      310
      Web APIs for Django
      1.9K
      2K
      + 1
      310
      PROS OF DJANGO REST FRAMEWORK
      • 66
        Easy to use
      • 65
        Browsable api
      • 53
        Great documentation
      • 50
        Customizable
      • 42
        Fast development
      • 9
        Easy to use, customizable, pluggable, serializer
      • 8
        Python
      • 7
        Django ORM
      • 5
        FastSerialize
      • 3
        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 · 71.9K 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