Need advice about which tool to choose?Ask the StackShare community!
Symfony vs WordPress: What are the differences?
Symfony: 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; WordPress: A semantic personal publishing platform with a focus on aesthetics, web standards, and usability. The core software is built by hundreds of community volunteers, and when you’re ready for more there are thousands of plugins and themes available to transform your site into almost anything you can imagine. Over 60 million people have chosen WordPress to power the place on the web they call “home” — we’d love you to join the family.
Symfony belongs to "Frameworks (Full Stack)" category of the tech stack, while WordPress can be primarily classified under "Self-Hosted Blogging / CMS".
"Open source", "Php" and "Community" are the key factors why developers consider Symfony; whereas "Customizable", "Easy to manage" and "Plugins & themes" are the primary reasons why WordPress is favored.
Symfony and WordPress are both open source tools. It seems that Symfony with 21.1K GitHub stars and 7.01K forks on GitHub has more adoption than WordPress with 12.6K GitHub stars and 7.69K GitHub forks.
Stack Exchange, ebay, and LinkedIn are some of the popular companies that use WordPress, whereas Symfony is used by Typeform, Accenture, and Docplanner. WordPress has a broader approval, being mentioned in 5305 company stacks & 1389 developers stacks; compared to Symfony, which is listed in 375 company stacks and 278 developer stacks.
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.
So many choices for CMSs these days. So then what do you choose if speed, security and customization are key? Headless for one. Consuming your own APIs for content is absolute key. It makes designing pages in the front-end a breeze. Leaving Ghost and Cockpit. If I then looked at the footprint and impact on server load, Cockpit definitely wins that battle.
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 Symfony
- Open source170
- Php143
- Dependency injection125
- Community124
- Professional117
- Doctrine76
- Organized69
- Modular architecture64
- Smart programming44
- Solid40
- Documentation16
- LTS releases13
- Easy to Learn8
- Robust8
- Good practices guideline7
- Bundle7
- Decoupled framework components7
- Simple6
- Service container6
- Powerful4
- Flexible3
Pros of WordPress
- Customizable409
- Easy to manage360
- Plugins & themes349
- Non-tech colleagues can update website content258
- Really powerful245
- Rapid website development143
- Best documentation76
- Codex50
- Product feature set43
- Custom/internal social network34
- Open source13
- Great for all types of websites7
- Huge install and user base5
- Best4
- I like it like I like a kick in the groin4
- Most websites make use of it4
- Open Source Community4
- Perfect example of user collaboration4
- It's simple and easy to use by any novice4
- Community3
- API-based CMS3
- Easy To use2
- <a href="https://secure.wphackedhel">Easy Beginner</a>1
Sign up to add or upvote prosMake informed product decisions
Cons of Symfony
- Too many dependency9
- Lot of config files7
- YMAL3
- Feature creep2
- Bloated1
Cons of WordPress
- Hard to keep up-to-date if you customize things11
- Plugins are of mixed quality10
- Not best backend UI8
- Complex Organization1
- Great Security1