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

Slim

275
373
+ 1
143
Symfony

7.2K
5.5K
+ 1
1.1K
Add tool

Slim vs Symfony: What are the differences?

Developers describe Slim as "A PHP micro framework". 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. On the other hand, Symfony is detailed as "A PHP full-stack web framework". Symfony is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP. Symfony can be used to develop all kind of websites, from your personal blog to high traffic ones like Dailymotion or Yahoo! Answers.

Slim belongs to "Microframeworks (Backend)" category of the tech stack, while Symfony can be primarily classified under "Frameworks (Full Stack)".

"Microframework" is the primary reason why developers consider Slim over the competitors, whereas "Open source" was stated as the key factor in picking Symfony.

Slim and Symfony are both open source tools. It seems that Symfony with 21K GitHub stars and 6.98K forks on GitHub has more adoption than Slim with 9.92K GitHub stars and 1.84K GitHub forks.

Docplanner, Webedia, and eTobb are some of the popular companies that use Symfony, whereas Slim is used by Coderus, WebbyLab, and Die Coder GmbH. Symfony has a broader approval, being mentioned in 355 company stacks & 267 developers stacks; compared to Slim, which is listed in 26 company stacks and 19 developer stacks.

Advice on Slim and Symfony
Needs advice
on
GolangGolangNode.jsNode.js
and
SymfonySymfony

I'm about to begin working on an API, for which I plan to add GraphQL connectivity for processing data. The data processed will mainly be audio files being downloaded/uploaded with some user messaging & authentication.

I don't mind the difficulty in any service since I've used C++ (for data structures & algorithms at least) and would also say I am patient and can learn fairly quickly. My main concerns would be their performance, libraries/community, and job marketability.

Why I'm stuck between these three...

Symfony: I've programmed in PHP for back-end in a previous internship and may do so again in a few months.

Node.js: It's newer than PHP, and it's JavaScript where my front-end stack will be React and (likely) React Native.

Go: It's newer than PHP, I've heard of its good performance, and it would be nice to learn a new (growing) language.

See more
Replies (1)
Max Musing
Founder & CEO at BaseDash · | 6 upvotes · 150.6K views
Recommends
on
Node.jsNode.js
at

Go with Node.js. There's something really satisfying about being able to use a single language across your entire tech stack. Especially once you integrate GraphQL, which is effectively JSON.

Your second best option is Go, but the ecosystem around Node.js is quite a bit stronger. This will play a big factor when you start building functionality like file management, messaging (especially in real-time), and authentication. The libraries and documentation are just stronger for Node.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Slim
Pros of Symfony
  • 32
    Microframework
  • 27
    API
  • 21
    Open source
  • 20
    Php
  • 11
    Fast
  • 8
    Restful & fast framework
  • 7
    Easy Setup, Great Documentation
  • 5
    Clear and straightforward
  • 5
    Good document to upgrade from previous version
  • 4
    Modular
  • 1
    Composer
  • 1
    Dependency injection
  • 1
    Easy to learn
  • 176
    Open source
  • 148
    Php
  • 129
    Community
  • 128
    Dependency injection
  • 121
    Professional
  • 79
    Doctrine
  • 74
    Organized
  • 70
    Modular architecture
  • 46
    Smart programming
  • 44
    Solid
  • 20
    Documentation
  • 15
    LTS releases
  • 10
    Easy to Learn
  • 9
    Decoupled framework components
  • 9
    Robust
  • 8
    Service container
  • 8
    Bundle
  • 8
    Good practices guideline
  • 7
    Simple
  • 7
    Powerful
  • 6
    Flexible

Sign up to add or upvote prosMake informed product decisions

Cons of Slim
Cons of Symfony
    Be the first to leave a con
    • 9
      Too many dependency
    • 7
      Lot of config files
    • 4
      YMAL
    • 2
      Feature creep
    • 1
      Bloated

    Sign up to add or upvote consMake informed product decisions

    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.

    What is Symfony?

    It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP..

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

    What companies use Slim?
    What companies use Symfony?
    See which teams inside your own company are using Slim or Symfony.
    Sign up for StackShare EnterpriseLearn More

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

    What tools integrate with Slim?
    What tools integrate with Symfony?

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

    What are some alternatives to Slim and Symfony?
    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.
    Flask
    Flask is intended for getting started very quickly and was developed with best intentions in mind.
    Django REST framework
    It is a powerful and flexible toolkit that makes it easy to build Web APIs.
    Sinatra
    Sinatra is a DSL for quickly creating web applications in Ruby with minimal effort.
    FastAPI
    It is a modern, fast (high-performance), web framework for building APIs with Python 3.6+ based on standard Python type hints.
    See all alternatives