Need advice about which tool to choose?Ask the StackShare community!

Flask

18.7K
15.8K
+ 1
82
LoopBack

285
556
+ 1
33
Add tool

Flask vs LoopBack: What are the differences?

# Introduction
In this Markdown code, we will discuss the key differences between Flask and LoopBack.

1. **Architecture**: Flask is a microframework, providing only the essentials for web development, while LoopBack is a more comprehensive framework with built-in models, data sources, and relationships.
2. **Language Support**: Flask is a Python-based framework, making it easy for Python developers to use, whereas LoopBack is a Node.js-based framework, catering to JavaScript developers.
3. **Scalability**: Flask is more lightweight and suitable for small to medium-sized applications, whereas LoopBack is designed to handle large-scale, enterprise-level applications with ease.
4. **Community Support**: Flask has a strong community backing due to its widespread adoption in the Python community, while LoopBack has a smaller but dedicated community of Node.js developers.
5. **REST API Development**: LoopBack comes with built-in tools and functionalities for quickly developing REST APIs, making it a preferred choice for API-centric applications, while Flask requires more manual configuration for API development.
6. **Documentation**: Flask has extensive and well-documented resources available, making it easy for beginners to get started, whereas LoopBack's documentation is comprehensive but may be overwhelming for newcomers.

In Summary, Flask and LoopBack differ in architecture, language support, scalability, community support, REST API development, and documentation, catering to different developer preferences and project requirements. 
Advice on Flask and LoopBack
kristan-dev
Senior Solutions Analyst · | 8 upvotes · 346.9K views

My journey to developing REST APIs started with Flask Restful, and I've found it to be enough for the needs of my project back then. Now that I've started investing more time on personal projects, I've yet to decide if I should move to use Django for writing REST APIs. I often see job posts looking for Python+Django developers, but it's usually for full-stack developers. I'm primarily interested in Data Engineering, so most of my web projects are back end.

Should I continue with what I know (Flask) or move on to Django?

See more
Replies (1)
Rafael Torres
Technical Lead at 4Agile · | 9 upvotes · 337.3K views

If you want to be a Web developer with knowledge in another frontend and NoSql technology, maybe continue with Flask. However, if you want to create very fast solutions to grow up with a new business and merge these with data analysis and other tools, Django is the answer. Basically read more about the service architecture where you feel more comfortable, Microservice or Monolithic, but please will not married with any because they solve issues to different contexts.

See more
Girish Sharma
Software Engineer at FireVisor Systems · | 6 upvotes · 274.9K views
Needs advice
on
BottleBottleFlaskFlask
and
NamekoNameko

Which is the best Python framework for microservices?

We are using Nameko for building microservices in Python. The things we really like are dependency injection and the ease with which one can expose endpoints via RPC over RabbitMQ. We are planning to try a tool that helps us write polyglot microservices and nameko is not super compatible with it. Also, we are a bit worried about the not so good community support from nameko and looking for a python alternate to write microservices.

See more
Replies (1)
Recommends
on
BottleBottle

Bottle is much less bloated and fast. Its built-in templating system is one of the fastest as it compiles the templates in bytecode. Also Bottle has no depenencies, preventing dependency bloat.

See more
Saurav Pandit
Application Devloper at Bny Mellon · | 6 upvotes · 292.1K views

I have just started learning Python 3 weeks ago. I want to create a REST API using python. The API will be used to save form data in an Oracle database. The front end is using AngularJS 8 with Angular Material. In python, there are so many frameworks to develop REST APIs.

I am looking for some suggestions which REST framework to choose?

Here are some features I am looking for:

  • Easy integration and unit testing, like in Angular. We just want to run a command.

  • Code packaging, like in java maven project we can build and package. I am looking for something which I can push in as an artifact and deploy whole code as a package.

  • Support for swagger/ OpenAPI

  • Support for JSON Web Token

  • Support for test case coverage report

Framework can have features included or can be available by extension. Also, you can suggest a framework other than the ones I have mentioned.

See more
Replies (1)
Recommends
on
FlaskFlask
at

For starters flask provides a beautiful and easy way to create REST APIs. Also its supported by excellent beginner docs as well as a very active community. Another good thing with Flask is its widely available list of plugins which allow you to build as you go. Its also good in performance and can scale to a quite decent level. However, if you are sure your project is going to be fairly big, it would be better to start with Django as it provides a lot of features out of the box and is extremely stable in performance. Both these frameworks have support for Swagger, JWT, Coverage Report although you have to install plugins for them. Deploying both of these are fairly simple and there is huge documentation available. Django has one of the best documentations I have come across. I hope I was able to answer your queries.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Flask
Pros of LoopBack
  • 14
    Flexibilty
  • 10
    For it flexibility
  • 9
    Flexibilty and easy to use
  • 8
    Flask
  • 7
    User friendly
  • 6
    Secured
  • 5
    Unopinionated
  • 3
    Orm
  • 2
    Secure
  • 1
    Beautiful code
  • 1
    Easy to get started
  • 1
    Easy to develop and maintain applications
  • 1
    Not JS
  • 1
    Easy to use
  • 1
    Documentation
  • 1
    Python
  • 1
    Minimal
  • 1
    Lightweight
  • 1
    Easy to setup and get it going
  • 1
    Perfect for small to large projects with superb docs.
  • 1
    Easy to integrate
  • 1
    Speed
  • 1
    Get started quickly
  • 1
    Customizable
  • 1
    Simple to use
  • 1
    Powerful
  • 1
    Rapid development
  • 0
    Open source
  • 0
    Well designed
  • 0
    Productive
  • 0
    Awesome
  • 0
    Expressive
  • 0
    Love it
  • 11
    Need a nodejs ReST-API, DB, AAA, Swagger? Then loopback
  • 9
    Easy Database Migration
  • 6
    Code generator
  • 4
    The future of API's
  • 2
    GraphQL
  • 1
    Typescript

Sign up to add or upvote prosMake informed product decisions

Cons of Flask
Cons of LoopBack
  • 10
    Not JS
  • 7
    Context
  • 5
    Not fast
  • 1
    Don't has many module as in spring
  • 7
    Community is slow
  • 1
    Backward compatibility

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is Flask?

Flask is intended for getting started very quickly and was developed with best intentions in mind.

What is LoopBack?

A highly-extensible, open-source Node.js framework that enables you to create dynamic end-to-end REST APIs with little or no coding. Connect to multiple data sources, write business logic in Node.js, glue on top of your existing services and data, connect using JS, iOS & Android SDKs.

Need advice about which tool to choose?Ask the StackShare community!

Jobs that mention Flask and LoopBack as a desired skillset
What companies use Flask?
What companies use LoopBack?
See which teams inside your own company are using Flask or LoopBack.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Flask?
What tools integrate with LoopBack?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

What are some alternatives to Flask and LoopBack?
Django
Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
Tornado
By using non-blocking network I/O, Tornado can scale to tens of thousands of open connections, making it ideal for long polling, WebSockets, and other applications that require a long-lived connection to each user.
ExpressJS
Express is a minimal and flexible node.js web application framework, providing a robust set of features for building single and multi-page, and hybrid web applications.
Node.js
Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.
React
Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project.
See all alternatives