Need advice about which tool to choose?Ask the StackShare community!
Phoenix Framework vs Symfony: What are the differences?
- Architecture: Phoenix Framework, built on Elixir, uses a more functional programming approach with a focus on concurrency and scalability, while Symfony, built on PHP, follows a more traditional object-oriented programming model with an emphasis on flexibility and maintainability.
- Language: Phoenix Framework utilizes the Elixir language, which is known for its high-performance and fault-tolerant capabilities, whereas Symfony is based on PHP, a widely-used scripting language that powers a large portion of the web.
- Performance: Phoenix Framework is designed to handle a high volume of requests efficiently due to its underlying Erlang VM, whereas Symfony might experience performance bottlenecks under heavy loads because of the nature of PHP.
- Learning Curve: Phoenix Framework may have a steeper learning curve for developers unfamiliar with functional programming concepts, whereas Symfony, with its more traditional approach, might be easier for developers already familiar with PHP and object-oriented programming.
- Community Support: Symfony, being built on PHP, has a larger community and ecosystem of third-party libraries and plugins available, making it easier to find solutions and resources compared to the relatively newer and smaller community around Phoenix Framework.
- Scalability: Phoenix Framework is known for its built-in support for horizontal scalability through technologies like distributed Erlang, making it easier to scale to handle larger workloads compared to Symfony's standard practices for scaling web applications.
In Summary, the key differences between Phoenix Framework and Symfony lie in their architectural approach, programming languages used, performance capabilities, learning curves, community support, and scalability options.
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.
#rust #elixir So am creating a messenger with voice call capabilities app which the user signs up using phone number and so at first i wanted to use Actix so i learned Rust so i thought to myself because well its first i felt its a bit immature to use actix web even though some companies are using Rust but we cant really say the full potential of Rust in a full scale app for example in Discord both Elixir and Rust are used meaning there is equal need for them but for Elixir so many companies use it from Whatsapp, Wechat, etc and this means something for Rust is not ready to go full scale we cant assume all this possibilities when it come Rust. So i decided to go the Erlang way after alot of Thinking so Do you think i made the right decision?Am 19 year programmer so i assume am not experienced as you so your answer or comment would really valuable to me
Pros of Phoenix Framework
- High performance120
- Super fast76
- Rapid development70
- Open source62
- Erlang VM60
- Well designed46
- Channels45
- Easily Scalable39
- Very extensible35
- Restful35
- Functional Programming11
- Inspired by Rails10
- Great community10
- Beautiful code8
- Ecto8
- Scalable6
- Fault tolerant6
- LiveView feature5
- Elegant4
- Insanely fast and easy4
- Feels like working with rails framework with more power4
- Built-in websocket support3
- Benevolent dictator that decides project course3
- Great integration with GraphQL3
- 2
- Front-End Agnostic2
- Functional approach1
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 Phoenix Framework
- No jobs6
- Very difficult5
Cons of Symfony
- Too many dependency10
- Lot of config files8
- YMAL4
- Feature creep3
- Bloated1