Need advice about which tool to choose?Ask the StackShare community!
Apache Thrift vs Symfony: What are the differences?
Apache Thrift: Software framework for scalable cross-language services development. The Apache Thrift software framework, for scalable cross-language services development, combines a software stack with a code generation engine to build services that work efficiently and seamlessly between C++, Java, Python, PHP, Ruby, Erlang, Perl, Haskell, C#, Cocoa, JavaScript, Node.js, Smalltalk, OCaml and Delphi and other languages; 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.
Apache Thrift belongs to "Serialization Frameworks" category of the tech stack, while Symfony can be primarily classified under "Frameworks (Full Stack)".
Apache Thrift and Symfony are both open source tools. Symfony with 21.1K GitHub stars and 7.01K forks on GitHub appears to be more popular than Apache Thrift with 6.48K GitHub stars and 2.97K GitHub forks.
According to the StackShare community, Symfony has a broader approval, being mentioned in 375 company stacks & 278 developers stacks; compared to Apache Thrift, which is listed in 11 company stacks and 8 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.
Pros of Apache Thrift
Pros of Symfony
- Open source177
- Php149
- Community130
- Dependency injection129
- Professional122
- Doctrine80
- Organized75
- Modular architecture71
- Smart programming47
- Solid45
- Documentation20
- LTS releases15
- Easy to Learn10
- Decoupled framework components9
- Robust9
- Service container8
- Bundle8
- Good practices guideline8
- Simple7
- Powerful7
- Flexible6
Sign up to add or upvote prosMake informed product decisions
Cons of Apache Thrift
Cons of Symfony
- Too many dependency10
- Lot of config files8
- YMAL4
- Feature creep3
- Bloated1
Sign up to add or upvote consMake informed product decisions
What is Apache Thrift?
What is Symfony?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Apache Thrift?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Apache Thrift?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+8