r/node • u/TheWobling • Jun 19 '15
What is Strongloop?
I'm having a rough time trying to figure out what strongloop actually is and would appreciate it if anyone could point me in the right direction or give me an explanation.
Thanks.
2
u/cluckie Jun 19 '15
yeah, It would be interesting if someone who has used strongloop tell us about the benefits of using it
1
u/TheWobling Jun 19 '15
I would appreciate this, I've been told I would be using Strongloop at work and I'm just trying to see how it benefits me and why it's used.
1
1
u/octetcloud Jun 19 '15
We sell tools and services for node.js, primarily focussed on build REST APIs, and production tooling, see http://loopback.io, and http://strong-pm.io, and http://strongloop.com would be a good source of info, too. :-)
0
Jun 19 '15
[deleted]
-1
u/jakerella Jun 19 '15
As a follow up, there may be confusion because we also have a Node module which you install to get our tool chain (process manager, LoopBack generator, debugger, etc):
npm install -g strongloop1
u/jakerella Jun 19 '15
(weird, my original comment never showed up for anyone else... here it is again...)
Hi! My name is Jordan, I head up developer evangelism at StrongLoop. The short answer is: we're a software company that helps power Node applications of all sorts. We write software from Node and io.js core, to Express, to LoopBack, and DevOps tools for building, deploying, monitoring, profiling, debugging, and scaling Node applications (all with a slick GUI called Arc).
We're a member of the newly formed Node Foundation and we've recently introduced an API gateway that builds on our success with LoopBack, an open source REST API framework.
4
10
u/0xjake Jun 20 '15 edited Jun 20 '15
I have worked extensively with strongloop. It is essentially a framework that provides support for simplifying remotes as well as a lot of ORM functionality. Instead of going around defining endpoints for service calls, you create models and those models have auto-generated endpoints.
A typical use for Strongloop would be something like this: You have a Customers table, a Widgets table, and a WidgetItems table. Each customer needs to be able to log into your site and create widgets for themselves, and then create widget items that have a many-to-one mapping to widgets. To create a widget or a widget item there are a number of required and optional parameters, and on top of that all the parameters need to be validated by some custom rules. Strongloop would let you put all of this together with a few relatively simple config files (json) specifying names, validation rules, and database settings. You could probably get away without writing any of the actual request handlers. Strongloop assumes a lot of standard schema setups (e.g. a Customer belongs in the Customers table, with PK "customerId") and verb conventions (POST->insert, PUT->update, GET->select) to allow this.
As with most of these frameworks, if your needs are basic enough then Strongloop will get the job done very well. It has a number of deficiencies, but with node being so flexible these aren't too hard to get around. For example, in the application I was writing we were handling large amounts of traffic to a small number of model endpoints, e.g. /api/widget/getWidget. Standard load would involve bursts of 100 requests per second or so. Strongloop choked on this and ended up repeatedly crashing our server with memory leaks until we ultimately rewrote these endpoints with plain Express as a workaround.
I've also found Strongloop's documentation to be seriously lacking and in some cases I've rolled my own implementations of functionality they provide because trying to figure theirs out was taking too long. They have a lot of documentation, but it's a large framework, so it's just not enough.