Note: This article was co-written by Subramanian Krishnan and Nagarjuna Surabathina.
LoopBack is a highly-extensible, open-source Node.js framework that enables you to quickly create dynamic end-to-end REST APIs with little or no coding. LoopBack allows users to define data models and connect these models to backend systems such as databases via data sources that provide create, retrieve, update, and delete (CRUD) functions. Data sources are backed by connectors that implement the data exchange logic using database drivers or other client APIs. In general, applications don’t use connectors directly, rather they go through data sources using the DataSource and PersistedModel APIs. The models defined in a LoopBack application can be automatically exposed as REST APIs using Strong Remoting. [Source: LoopBack docs] Read more
We’re happy to announce that IBM and StrongLoop are returning to GlueCon. The StrongLoop team will be heading to Broomfield, CO from May 24-26, 2017 for this technical conference.
Never been to Gluecon? The convention describes itself like this:
Glue is a developer oriented conference that is focused on how Serverless Architectures, Containers, Microservices, APIs, DevOps, Mobile, Analytics, Performance Monitoring, and cutting edge developer platforms and tools are changing the technology landscape.
In this three-part series, we are covering systematic design as it applies to:
Let’s now turn our attention to the design of data. Read more
In 2013, we started LoopBack as a mobile-backend-as-a-service, evolving out of earlier efforts such as Deployd and JugglingDB. Users quickly told us that what they needed wasn’t a backend-as-a-service itself, but a framework to build their own MBaaS. We built LoopBack on top of the popular Express library and based it on open standards to ensure compatibility; We developed it in the open to ensure we could address users’ problems and needs.
The core LoopBack team has talked to thousands of people about LoopBack over the past three and a half years. These discussions have molded our thinking about what users need and how to proceed. Read more