CODEWITHSUNDEEP
javascriptnode.jsexpressmongooseloopbackjs
Salih Şenol Çakarcı
Salih Şenol Çakarcı

Reputation: 2330

Loopback with ExpressJS

I have examined and practiced on creating Rest Api's with loopback and ExpressJS seperately

While Using Loopback;

  1. It was really time consuming to read all the documentation and learning loopback specific stuff
  2. It also enables you to create your Api in a short period of time and has lots of magic things inside it.
  3. I saw that if I face problems while developing with loopback. I usually get stuck in finding answers from community.

While Using ExpressJs

  1. You write almost every api endpoint in same format with lots of copied code.
  2. You are comfortable with it and can do anything with ease. But time consuming if compared with loopback.

My point is to utilize best parts of both ExpressJs and Loopback

So my question is "Does it make sense to use Loopback with ExpressJs and also use Mongoose?"

Related with my question Loopback has a documentation about adding ExpressJS route in Loopback application. Loopback with Express Route

If it makes sense is there any recommendation for folder structuring ?

Upvotes: 2

Views: 721

Answers (1)

Serg
Serg

Reputation: 2427

As @Jspdown wrote in his comment to your question Loopback is really based on Express, so you don't need to make choice between them.

When you work on your application using Express and produce 'lots of copied code', soon you start to optimize it and in fact develop your own framework. So this is exactly what Loopback team already have done for you.

Thus the choice is not Loopback or Express but it is - to invest into study ready-made framework or to develop your own framework. As for me I think that if you are working on relatively simple projects and/or quick prototypes or going to change your programming tools soon - don't study, just do. But if you are working on large, mission critical system in long-lasting project - Loopback is helpful.

Upvotes: 2

Related Questions