LoopBack is an open-source Node.js framework built for API developers. Its primary goal is to help create APIs as microservices from existing services/databases and expose them as endpoints for client applications, such as web, mobile, and IoT. LoopBack connects the dots between accepting API requests and interacting with backend resources. By facilitating developers to implement API logic with out of box integration capabilities, LoopBack establishes itself as the API composition layer to differentiate from other frameworks, such as Express, Hapi, and Sails.
Up to version 3.x, LoopBack built on the popular Express framework. In retrospect, basing LoopBack on Express was the right decision: Standing on the shoulders of Express enabled LoopBack to focus on adding value for API creation experience without reinventing the wheel. LoopBack also has benefitted from the Express ecosystem, especially ready-to-use middleware modules from npm as well as valuable knowledge and support by the community.
With LoopBack, developers can create and expose APIs just like following a recipe. LoopBack introduces a set of core concepts that represent the key aspects of API implementation. To create APIs out of existing databases or services, developers can simply scaffold a LoopBack application, then add necessary JSON declarations and Node.js code to get their APIs up and running in a few minutes.
LoopBack uses Express routing and middleware as the plumbing to a request/response pipeline for API use cases, such as authentication, authorization, and routing. Beyond inbound HTTP processing, LoopBack provides integration facilities such as models, datasources, and connectors to allow API logic to interact with various backend systems, including but not limited to, databases, REST APIs, SOAP web services and gRPC microservices. The ability to glue inbound communication and outbound integration makes LoopBack a very powerful framework for API developers. The diagram below illustrates how LoopBack fits into a typical end-to-end API processing flow.
LoopBack has grown significantly in features and users with many years of development and multiple releases. LoopBack has been well-recieved by the developer community. As an indication, the community has developed many extensions. The core team has also learned a lot from what we have done as well as great feedback from the community.
Why LoopBack 4?
Like many projects, LoopBack has started to experience growing pains, especially as:
Technical debt is accumulating, for example inconsistent designs across modules and feature flags for different behaviors. Here are a few examples:
- Various modules use different registries to manage different types of artifacts, such as remoting metadata, models, datasources, and middleware.
- Different flavors are used to allow custom logic to intercept requests/responses at various layers, such as middleware, remote hooks, CRUD operation hooks, and connector hooks.
- More feature flags were added over time to keep backward compatibility while enabling users to opt-in to new behaviors.
It is becoming more difficult to add new features or fix bugs as some areas start to reach the limit of the current design.
loopback-datasource-jugglermodule is a kitchen sink for many things, such as typing, data modeling, validation, aggregation, persistence, and service integration.
- Models are overloaded with multiple responsibilities, such as data representation, persistence, and mapping to REST. Models are tied to datasources and it’s not easy to reuse the same model definition against different datasources.
It’s not easy to extend the framework without requesting the core team to make code changes in LoopBack modules. The current version of LoopBack has ad-hoc extensibility at various layers. Extension points are not consistently defined. For example,
- Use Express to register middleware.
- Use remoting hooks to intercept remote method invocations.
- Use CRUD hooks to add logic around CRUD operations.
More projects start to use LoopBack as the underlying platform. Such use cases require more knowledge of LoopBack internals and more flexibility and dynamicity to leverage LoopBack to manage and compose artifacts using a metadata driven approach. Some good examples are:
- Multi-tenancy which requires artifact isolation between tenants.
- Metadata APIs to manage/activate model definitions and datasources.
- New interaction patterns for connectors, such as eventing or messaging.
- Extra metadata for model definitions.
Since the release of 3.x, the team has been brainstorming about how to sustain and advance LoopBack. We did a lot of homework, triaged existing GitHub issues, reached out to community members and downstream products, and evaluated relevant frameworks and technologies to answer to the following questions:
- Who is the target audience of LoopBack? Why are they interested in LoopBack? What do they use LoopBack for and how do they use it?
- What are the critical pain points? Can we address them incrementally without rebuilding a new foundation?
- What are the most requested features? Is it possible to add such features with the current design?
- What are latest and greatest technologies in our space? What value will they bring in if we start to adopt them?
- How to scale the development and maintenance of LoopBack? How do we allow larger development teams to collaborate on creating APIs using LoopBack?
- How to further grow the community and expand its ecosystem? What can we do to bring more users and contributors to LoopBack?
LoopBack has gained traction among a spectrum of users beyond Node.js application developers, including:
- API developers - Use LoopBack to create APIs in Node.js.
- LoopBack maintainers and contributors - Build and maintain modules by the LoopBack project .
- Extension developers - Contribute extensions to LoopBack to augment the framework.
- Platform developers - Leverage LoopBack as the base to build their value-added offerings.
The core team decided to make a bold move and rebuild LoopBack to meet the needs of all the above groups. The decision led to the inception of LoopBack 4, a new generation of API creation platform. For more information, read the blog post Announcing LoopBack.next, the Next Step to Make LoopBack Effortlessly Extensible.
LoopBack 4’s goals are:
Catch up with latest and greatest technology advances.
Promote extensibility to grow the ecosystem.
- Build a minimal core and enable everything else to be implemented via extensions.
- Open the door for more extension points and extensions.
Align with cloud native experience for microservices.
- Adopt cloud native microservices by adopting initiatives such as Cloud Native Computing Foundation.
- Make LoopBack a first-class citizen of the microservices ecosystem.
Remove the complexity and inconsistency across modules.
- Use a consistent registry and APIs to manage artifacts and their dependencies.
- Pay down technical debts by refactoring complex modules.
Separate concerns for better composability.
- Introduce new concepts such as controllers and repositories to represent different responsibilities.
- Break down the runtime as a set of services and utilize the extension points/extensions pattern to manage the registration, resolution, and composition.
We decided not to take a “big-bang” approach to build LoopBack 4. Instead, we are doing it incrementally in multiple stages with smaller steps. This approach allows us to better engage the community from the beginning. We are following the principles below to pursue architectural simplicity and extensibility:
Imperative first, declarative later
Everything can be done by code via
APIs. The LoopBack team or community contributors can then create varieties of user experiences with such APIs. For example, with APIs to define models, we allow applications to declare models in JSON or YAML files so that they can be discovered and loaded. An extension can parse other forms of model definition, such as JSON schemas, ES6 classes with decorators, schemas in OpenAPI spec, or even XML schemas into LoopBack model definitions.
We can also leverage programming constructs such as decorators allow developers to supply metadata in code. Furthermore, LoopBack artifacts can be declared in JSON or YAML files, which will be handy for users to generate and manipulate them by hand or tooling.
Build minimum features and add more later if necessary
Apply YAGNI (You Aint’t Gonna Need It). Design and build for what is needed now, not for what you think you may need in the future. There are many different perspectives in API creation and people ask for a lot of features. Starting with MVP allow us to reach the root of the issues without being derailed by noises and build the absolutely necessary features as the core building blocks.
Developer experience first
Always keep in mind that LoopBack is built for developers by developers. Our first priority is to make API developers’ life easier. When we design APIs and user interfaces such as a CLI or GUI, we want to make sure they are intuitive to and natural to their thought process.
Here are the stages we are marching through toward the final version of LoopBack 4 as illustrated below.
Rebase and rewrite the core
Leverage TypeScript for better code quality and productivity.
Unify the asynchronous programming model/style.
- 100% promise-based APIs.
- Async/Await as first-class async programming style.
Implement an IoC Container for better visibility and extensibility
- Universal registry across different modules
- Dependency injection as a pattern to manage dependencies
Introduce Component as packaging model for extensions
- Component can be a npm module or a local directory
- Component encapsulates a list of extensions as a whole
Validate the core design by implementing an REST/HTTP invocation chain
Add top-down REST API creation which starts with OpenAPI specs.
Build sequence of actions for inbound http processing
- Introduce sequence as the composition of actions
- Implement the most critical actions to fulfill the REST API routing and invocation
Introduce controllers as entry points for API-related business logic.
Models are the centerpieces of the current LoopBack applications. . They take multiple responsibilities:
- Data modeling
- Anchor for API related business logic
- Persistence or service invocation
- Mapping to REST HTTP/JSON endpoints
Authentication as a component
Implement the core functionality of authentication as a component, which includes:
- Decorators to denote authentication requirement
authenticateaction to handle authentication
- Extension points for various authentication strategies
Rebuild our integration and composition capabilities
- Introduce repositories to represent data access patterns such as CRUD or Key/Value stores
- Provide a reference implementation of CRUD and KV flavors of repository interfaces using the legacy juggler and connectors
- Refactor/rewrite the juggler into separate modules
- Typing system
- Model and relation definition
- Query and mutation language
- Repository interfaces and implementations for data access
- Service interfaces and implementations for service invocations
- Define interfaces and metadata for connectors
- Rewrite connectors
Declarative metadata and bootstrapping
LoopBack manages a set of artifacts, such as models, relations, datasources, connectors, ACLs, controllers, repositories, actions, sequences, components, utility functions, and OpenAPI specs. In addition to the programmatic approach to describe these artifacts by code (apis and decorators), we would like to add declarative support so that they can be declared in JSON/YAML files.
- Define a new domain-specific language (DSL) in JSON/YAML format and corresponding templates.
- Define the project layout to organize project artifacts.
- Leverage the IoC Context to manage metadata/instances of such artifacts following the extension point/extension pattern.
- Define the lifecycle and serialization/de-serialization requirements for each type of artifact.
- Add a boot component to discover/load/resolve/activate the artifacts. The boot process can be tailored for both tooling and runtime.
Tooling (CLI & UI)
- Add CLI and UI tools to:
- Scaffold LoopBack 4 applications
- Manage artifacts such as sequences, actions, controllers, repositories, services, datasources and models
- Add CLI and UI tools to:
Enable cloud native experience
- Allow controllers to be exposed as gRPC services
- Allow interaction with other gRPC services
- Integration with microservices deployment infrastructure such as Docker and Kubernetes
- Integration with service mesh
The following diagram illustrates the high-level building blocks of LoopBack 4:
Please note there is a common layer below the different functional areas in the stack. Let’s examine the need to build a new core foundation for LoopBack 4.
A new core foundation
The core responsibility
LoopBack itself is already modular. For example, a typical LoopBack 3.x application’s dependency graph will have the following npm modules:
LoopBack manages various artifacts across different modules. The following are a list of built-in types of artifacts that LoopBack 3.x supports out of box:
- Model definitions/relations: describes data models and their relations
- Validation: validates model instances and properties
- Model configurations: configures models and attaches them to data sources
- Datasources: configures connectivity to backend systems
- Connectors: implements interactions with the underlying backend system
- Components: wraps a module that be bootstrapped with LoopBack
- ACLs: controls access to protected resources
- Built-in models: provides set of prebuilt models such as User, AccessToken, and Role
- Express middleware
- remote hooks
- CRUD operation hooks
- connector hooks
- Security integration
- Identity and token management
- Authentication schemes
- Passport component for various authentication strategies
- Storage component for various local/cloud object storage systems
- Local file system
- Amazon S3
- Google Cloud
- IBM Cloud Object Storage
- Push component for mobile push notifications
- Different API styles
Metadata for these artifacts form the knowledge base for LoopBack to glue all the pieces together and build capabilities to handle common API use cases.
How to represent the metadata and their relations is the key responsibility of the LoopBack core foundation. It needs to provide a consistent way to contribute and consume such building blocks.
Key ingredients for the core
The core foundation for LoopBack 4 is responsible for managing various artifacts independent of the nature of such artifacts.
A consistent registry to provide visibility and addressability for all artifacts.
Visibility: Each artifact has a unique address and can be accessed via a URI or key. Artifacts can also be visible at different scopes.
Extensibility: LoopBack artifacts can be managed by types. New artifact types can be introduced. Instances for a given type can be added, removed, or replaced. Organizing artifacts in a hierarchy of extension points/extensions decouples providers and consumers.
Ability to compose with dependency resolution.
- Composability: It’s common that one artifact to have dependencies on other artifacts. With dependency injection or service locator patterns, the core will greatly simplify how multiple artifacts work together.
A packaging model for extensions.
- Pluggability: Extensions can be organized and contributed as a whole. We need to have a packaging model so that extension developers can create their own modules as bundles and plug into a LoopBack application.
Why not Express?
Do we need to build our own core foundation? Can we continue to use Express? Our conclusion is no. Here are the gaps between what Express and LoopBack’s needs.
Lack of extensibility.
Express is a routing and middleware web framework with minimal functionality of its own: An Express application is essentially a series of middleware function calls. For details, see Using middleware.
Express is only extensibile via middleware. It neither exposes a registry nor provides APIs to manage artifacts such as middleware or routers. For its purpose, Express only deals with middleware-like extensions that intercept http requests/responses. LoopBack needs much more extension points and extensions.
Lack of composability.
Express is not composable. For example,
app.use()is the only way to register a middleware. The order of middleware is determined by the order of
app.use. This simplistic approach works for a single monolithic application where all middleware are known and arranged ahead of time. But it does not support the case when middleware from other components need to be added between existing ones. LoopBack had to introduce a phase-based extension and hack Express to provide this capability.
Express doesn’t provide any way to manage dependencies between artifact instances either.
Lack of declarative support.
Fast, unopinionated, minimalist web framework for Node.js. In contrast, LoopBack is designed to facilitate API creation and composition by conventions and patterns as best practices. More types of constructs are introduced.
Deep dive into LoopBack 4 extensibility
There are several key pillars to make extensibility a reality for LoopBack 4.
- Context, the IoC container to manage services
- Dependency injection to facilitate composition
- Decorators to supply metadata using annotations
- Component as the packaging model to bundle extensions
Please check out Extending LoopBack 4.
Rebuilding LoopBack experience on top of the new core
With the extensible foundation in place, we start to rebuild the LoopBack REST API experience by “eating your own dog food” with the following artifacts:
- Sequence and actions: A sequence of actions to handle HTTP requests/responses.
- Controllers: A class with methods to implement API operations behind REST endpoints.
- Model: Definition of data models.
- Repositories: Interfaces of access patterns for data sources.
The features are provided by the following modules:
Example for application developers
Before we go further, let’s try to build a ‘hello world’ application with LoopBack 4.
Example for extension developers
Learn from existing ones