I tend to migrate towards languages, frameworks, and architectures that have a large community, follow web standards, and live by the following two principles:
Now LoopBack is not a full-stack solution. It’s an API server – a significant component in the full-stack architecture. You can write some server-side html rendering (MVC) since it’s built on Express and uses EJS, but it’s mostly targeted towards Single Page Applications (SPAs) like Angular and native mobile applications. In this article/video I will focus on the server aspect and maybe in a future article I will tackle the client component.
Instead of writing a 30-page article walking you through each step of setting up a typical LoopBack application, I decided to record a video of my findings. I determined what I thought were the important aspects of evaluating a framework like this. These items are part of the 80% use case; at Solution Street we want software engineers to breeze through the 80% of standard software development and focus on the 20%.
Here are the items I researched and describe or provide examples of in the video:
- Easily create a skeleton app that works from the start
- Create basic model with attributes that has CRUD processing out of the box
- Create relationships and show different relationships
- Connect to datasources – mySQL, PostgreSQL, MongoDB, etc.
- Migration of data models
- Persistence of data
- Querying data with filtering
- Hide APIs – making them private
- Custom methods
- Operational hooks (e.g., before filters)
- Override existing (default) CRUD methods
- Validations – standard and custom
- Access control lists (ACL)
- Access tokens/CORS
- ES6 support
- Console playground (like Rails console)
Here is a “video walkthrough“.