Alternatives to StrongLoop logo

Alternatives to StrongLoop

PM2, LoopBack, DreamFactory, GraphQL, and hapi are the most popular alternatives and competitors to StrongLoop.
11
29
+ 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

391
269
17
Ease-to-use Node.js process manager, like forever
391
269
+ 1
17
PROS OF PM2
  • 9
    Reliable
  • 7
    Easy to manage
  • 1
    Easy to use
CONS OF PM2
  • 1
    Memory leak

related PM2 posts

LoopBack logo

LoopBack

251
470
27
Build modern API applications that require complex integrations
251
470
+ 1
27
PROS OF LOOPBACK
  • 9
    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
  • 0
    Typescript
CONS OF LOOPBACK
  • 7
    Community is slow
  • 1
    Backward compatibility

related LoopBack posts

Samuel Olugbemi
Software Engineer at Payzone UK · | 6 upvotes · 116.4K 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
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

37
74
20
Open source REST API backend for mobile, web, and IoT applications.
37
74
+ 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

    GraphQL logo

    GraphQL

    22.4K
    18.2K
    292
    A data query language and runtime
    22.4K
    18.2K
    + 1
    292
    PROS OF GRAPHQL
    • 69
      Schemas defined by the requests made by the user
    • 62
      Will replace RESTful interfaces
    • 59
      The future of API's
    • 47
      The future of databases
    • 12
      Self-documenting
    • 11
      Get many resources in a single request
    • 5
      Ask for what you need, get exactly that
    • 4
      Query Language
    • 3
      Evolve your API without versions
    • 3
      Fetch different resources in one request
    • 3
      Type system
    • 2
      GraphiQL
    • 2
      Ease of client creation
    • 2
      Easy setup
    • 1
      Good for apps that query at build time. (SSR/Gatsby)
    • 1
      Backed by Facebook
    • 1
      Easy to learn
    • 1
      "Open" document
    • 1
      Better versioning
    • 1
      Standard
    • 1
      1. Describe your data
    • 1
      Fast prototyping
    CONS OF GRAPHQL
    • 3
      Hard to migrate from GraphQL to another technology
    • 3
      More code to type.
    • 1
      Works just like any other API at runtime
    • 1
      Takes longer to build compared to schemaless.

    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 · | 44 upvotes · 1.7M 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

    392
    394
    85
    Server Framework for Node.js
    392
    394
    + 1
    85
    PROS OF HAPI
    • 25
      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

      21K
      15.9K
      1.5K
      Sinatra inspired web development framework for node.js -- insanely fast, flexible, and simple
      21K
      15.9K
      + 1
      1.5K
      PROS OF EXPRESSJS
      • 367
        Simple
      • 322
        Node.js
      • 235
        Javascript
      • 185
        High performance
      • 148
        Robust routing
      • 66
        Middlewares
      • 66
        Open source
      • 53
        Great community
      • 34
        Hybrid web applications
      • 10
        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
      • 2
        Xxx
      • 1
        Callbacks
      • 1
        Data stream
      CONS OF EXPRESSJS
      • 23
        Not python
      • 16
        Overrated
      • 14
        No multithreading
      • 6
        Javascript
      • 5
        Not fast
      • 2
        Easily Insecure for Novices
      • 1
        Not a lion
      • 1
        Nnnn

      related ExpressJS posts

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

      14.1K
      11.9K
      1.5K
      A microframework for Python based on Werkzeug, Jinja 2 and good intentions
      14.1K
      11.9K
      + 1
      1.5K
      PROS OF FLASK
      • 313
        Lightweight
      • 269
        Python
      • 214
        Minimal
      • 145
        Open source
      • 98
        Documentation
      • 66
        Easy to use
      • 54
        Easy to setup and get it going
      • 53
        Well designed
      • 48
        Easy to develop and maintain applications
      • 45
        Easy to get started
      • 18
        Beautiful code
      • 16
        Rapid development
      • 14
        Powerful
      • 13
        Expressive
      • 12
        Awesome
      • 11
        Love it
      • 11
        Flexibilty
      • 11
        Speed
      • 10
        Get started quickly
      • 10
        Simple to use
      • 10
        Easy to integrate
      • 9
        Perfect for small to large projects with superb docs.
      • 9
        For it flexibility
      • 9
        Customizable
      • 8
        Productive
      • 8
        Flexibilty and easy to use
      • 7
        Flask
      • 6
        Not JS
      • 6
        User friendly
      • 5
        Secured
      • 4
        Unopinionated
      • 1
        Secure
      • 1
        Orm
      CONS OF FLASK
      • 10
        Not JS
      • 7
        Context
      • 4
        Not fast
      • 1
        Don't has many module as in spring

      related Flask posts

      James Man
      Software Engineer at Pinterest · | 42 upvotes · 846.5K 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.6K
      1.7K
      301
      Web APIs for Django
      1.6K
      1.7K
      + 1
      301
      PROS OF DJANGO REST FRAMEWORK
      • 64
        Browsable api
      • 64
        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