Need advice about which tool to choose?Ask the StackShare community!
Drupal vs Symfony: What are the differences?
Key Differences between Drupal and Symfony
1. Architecture: Drupal is a content management system (CMS) that comes with pre-built features for managing content, users, and permissions out of the box. Symfony, on the other hand, is a PHP framework that provides a set of reusable components and tools for building web applications in a more customized manner.
2. Extensibility: Drupal offers a wide range of modules that can be easily added to extend its functionality, making it suitable for non-developers. Symfony, however, allows developers to have more control over the codebase and offers flexibility in choosing and integrating components as needed for specific requirements.
3. Learning Curve: Drupal is generally considered to be more user-friendly and easier to learn for beginners due to its pre-built features and simplified administration interface. Symfony, on the other hand, has a steeper learning curve as it requires a solid understanding of object-oriented programming and design patterns.
4. Community Support: Drupal has a large and active community that regularly contributes modules, themes, and updates, making it easier to find resources and get help. Symfony also has a strong community but is more focused on developers, providing extensive documentation and support for building custom applications.
5. Use Cases: Drupal is commonly used for building websites and content-heavy platforms, while Symfony is preferred for developing complex web applications, APIs, and enterprise-level projects that require scalability and customization.
6. Performance: Symfony is known for its high performance and faster response times compared to Drupal, making it a better choice for projects where speed and efficiency are crucial factors.
In Summary, Drupal and Symfony differ in their architecture, extensibility, learning curve, community support, use cases, and performance, catering to different needs and preferences in web development.
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.
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.
10 Years ago I have started to check more about the online sphere and I have decided to make a website. There were a few CMS available at that time like WordPress or Joomla that you can use to have your website. At that point, I have decided to use WordPress as it was the easiest and I am glad I have made a good decision. Now WordPress is the most used CMS. Later I have created also a site about WordPress: https://www.wpdoze.com
Pros of Drupal
- Stable, highly functional cms75
- Great community60
- Easy cms to make websites44
- Highly customizable43
- Digital customer experience delivery platform22
- Really powerful17
- Customizable16
- Flexible11
- Good tool for prototyping10
- Enterprise proven over many years when others failed9
- Headless adds even more power/flexibility8
- Open source8
- Each version becomes more intuitive for clients to use7
- Well documented7
- Lego blocks methodology6
- Caching and performance4
- Built on Symfony3
- Powerful3
- Can build anything3
- Views2
- API-based CMS2
Pros of Symfony
- Open source177
- Php149
- Community130
- Dependency injection129
- Professional122
- Doctrine80
- Organized75
- Modular architecture71
- Smart programming47
- Solid45
- Documentation20
- LTS releases16
- Decoupled framework components10
- Robust10
- Easy to Learn10
- Good practices guideline8
- Service container8
- Bundle8
- Powerful7
- Simple7
- Flexible6
Sign up to add or upvote prosMake informed product decisions
Cons of Drupal
- DJango1
- Steep learning curve1
Cons of Symfony
- Too many dependency10
- Lot of config files8
- YMAL4
- Feature creep3
- Bloated1