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

Flask

19K
16K
+ 1
66
Slim

273
389
+ 1
152
Add tool

Flask vs Slim: What are the differences?

Introduction:

Flask and Slim are both web frameworks used for developing web applications. While Flask is a Python-based microframework, Slim is a PHP-based microframework. Despite their shared purpose, there are several key differences between the two frameworks.

  1. Routing: Flask uses decorators to define routes, allowing developers to easily map URLs to functions in their code. On the other hand, Slim follows a routing API approach, where developers define routes using the router methods provided by the framework. This makes routing in Slim more explicit and organized compared to Flask.

  2. Template Engine: Flask uses Jinja2 as its default template engine. Jinja2 is a powerful and flexible templating language that allows developers to create dynamic web pages. In contrast, Slim does not come with a default template engine. However, it provides support for various template engines like Twig, Plates, Mustache, etc., allowing developers to choose the one that best suits their needs.

  3. Dependency Injection: Flask does not have built-in support for dependency injection. Although it is possible to implement dependency injection in Flask using third-party libraries or frameworks, it requires additional configuration and setup. On the other hand, Slim has built-in dependency injection support through its Container component. This makes dependency management more streamlined and convenient in Slim.

  4. Middleware: Flask allows developers to add middleware by simply applying decorators to their application routes. Developers can easily apply middleware functions to specific routes or to the entire application. In contrast, Slim uses a middleware stack to apply middleware to the application. The middleware stack allows for more fine-grained control over the order in which middleware is executed.

  5. Plugins/Extensions: Flask has a vibrant ecosystem of third-party plugins and extensions that provide additional functionality and features. These plugins can be easily integrated with Flask applications, extending its capabilities. On the other hand, Slim has a more limited selection of plugins and extensions compared to Flask. This may require developers using Slim to implement certain features from scratch or rely on other external libraries.

  6. Learning Curve: Flask has a reputation for being easy to learn and use, especially for developers familiar with Python. The simplicity and elegance of Flask's design make it a popular choice for beginners. In contrast, Slim may have a steeper learning curve for developers with limited PHP experience. Its minimalist design philosophy and absence of certain built-in features may require developers to acquire a deeper understanding of PHP and web development concepts.

In summary, Flask and Slim differ in terms of routing approaches, template engines, dependency injection support, middleware handling, plugin availability, and learning curve. While Flask offers a robust ecosystem of plugins and has a reputation for simplicity, Slim provides a more explicit routing API, built-in dependency injection, and a more fine-grained middleware stack. Developers must consider these differences when choosing the framework that best suits their web development needs.

Advice on Flask and Slim
Muhammad Waleed
Community & Content Operations · | 3 upvotes · 167.6K views
Needs advice
on
Django REST frameworkDjango REST framework
and
FlaskFlask

Hey! So I am planning to make an e-commerce website with React Native as my frontend technology stack and MongoDB as my database. I was wondering what will be the best REST framework to use for my backend that will simply serve the frontend. Is Django rest framework a good option or should I go with Flask? I am currently leaning towards flask as the development team is well versed in it. Please help!

See more
Replies (2)
Preeti Yuankrathok
Software Consultant at CODIUM · | 2 upvotes · 68.3K views

If the application is simple such as less endpoint or simple logic, I'd suggest Flask. But what you're building is quite a large system that contains many logics and a lot of models. So I'd suggest you with Django and Django REST framework. Django ORM is also one of the best ORM in the world as well.

See more
Mayur Borse
Software Engineer at hyphenOs · | 2 upvotes · 71.4K views
Recommends
on
FastAPIFastAPIfastapifastapi

FastAPI is modern microframework. If you haven't used any of them, I'd suggest FastAPI. Django REST is also good if you have previous experience with it.

See more
kristan-dev
Senior Solutions Analyst · | 8 upvotes · 370.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 · 361K 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 · 293.7K 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 · 316.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
Decisions about Flask and Slim

We decided to expose our small machine learning (ML) pipeline as a REST API. This allows us to nicely separate concerns from the rest of the codebase. There are two very popular choices in Python for building APIs: Flask and FastAPI. We have experience with both, but find that FastAPIs use of static type hints and validation with Pydantic allow us to build better APIs faster.

See more
Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of Flask
Pros of Slim
  • 10
    For it flexibility
  • 9
    Flexibilty and easy to use
  • 8
    Flask
  • 7
    User friendly
  • 6
    Secured
  • 5
    Unopinionated
  • 2
    Secure
  • 1
    Customizable
  • 1
    Simple to use
  • 1
    Powerful
  • 1
    Rapid development
  • 1
    Beautiful code
  • 1
    Easy to develop and maintain applications
  • 1
    Easy to setup and get it going
  • 1
    Easy to use
  • 1
    Documentation
  • 1
    Python
  • 1
    Minimal
  • 1
    Lightweight
  • 1
    Easy to get started
  • 1
    Orm
  • 1
    Not JS
  • 1
    Perfect for small to large projects with superb docs.
  • 1
    Easy to integrate
  • 1
    Speed
  • 1
    Get started quickly
  • 0
    Open source
  • 0
    Well designed
  • 0
    Flexibilty
  • 0
    Productive
  • 0
    Awesome
  • 0
    Expressive
  • 0
    Love it
  • 33
    Microframework
  • 27
    API
  • 22
    Open source
  • 21
    Php
  • 11
    Fast
  • 8
    Restful & fast framework
  • 7
    Easy Setup, Great Documentation
  • 5
    Modular
  • 5
    Clear and straightforward
  • 5
    Good document to upgrade from previous version
  • 4
    Dependency injection
  • 2
    Composer
  • 2
    Easy to learn

Sign up to add or upvote prosMake informed product decisions

Cons of Flask
Cons of Slim
  • 10
    Not JS
  • 7
    Context
  • 5
    Not fast
  • 1
    Don't has many module as in spring
    Be the first to leave a con

    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 Slim?

    Slim is easy to use for both beginners and professionals. Slim favors cleanliness over terseness and common cases over edge cases. Its interface is simple, intuitive, and extensively documented — both online and in the code itself.

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

    Jobs that mention Flask and Slim as a desired skillset
    What companies use Flask?
    What companies use Slim?
    Manage your open source components, licenses, and vulnerabilities
    Learn More

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

    What tools integrate with Flask?
    What tools integrate with Slim?

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

    Blog Posts

    What are some alternatives to Flask and Slim?
    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