LoopBack is a highly extensible, open-source Node.js framework based on Express that enables you to quickly create dynamic end-to-end REST APIs and connect to backend systems such as databases and SOAP or REST services.
With LoopBack, you can easily create models based on a schema (if you have one) or define models if you don’t and build relationships between models.
LoopBack 4 is the latest release from the LoopBack team and includes:
- A new core to deliver great extensibility and flexibility written in TypeScript/ES2017.
- Creation experience for defining REST APIs and handling API requests and responses.
- Programming model with dependency injection and concepts like components, mixins, and repositories to make LoopBack extensible
- GraphQL support through OASGraph
The diagram below demonstrates how LoopBack serves as a composition bridge between incoming requests and outgoing integrations. It also shows the different personas who are interested in various capabilities provided by LoopBack.
Why should a developer contribute?
LoopBack is built on Node.js, an increasingly popular choice for app development in general and for API development in particular. Node.js enables asynchronous and non-blocking program execution that is particularly well-suited for high-latency uses such as mobile and other networked apps.
LoopBack supports popular Node.js programming constructs such as Express middleware and Promises. So, contributing to the project helps you make better APIs and uses a framework that you’re probably already familiar with.
What business problems will the software address?
APIs enable businesses to expand the reach of their products and services to audiences of developers who consume those APIs, and LoopBack makes it really easy to create a REST API with minimal coding. LoopBack provides a consistent way to design and implement APIs, including the REST layer, models, and ORM.
LoopBack has connectors for legacy systems found in typical enterprise settings, from DB2/Oracle/MSSQL databases to SOAP web services, which reduces the cost of integrating the new API tier with existing system-of-record tiers.