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


+ 1

+ 1
Add tool

Next.js vs Symfony: What are the differences?

Next.js: A small framework for server-rendered universal JavaScript apps *. Next.js is a minimalistic framework for server-rendered React applications; *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.

Next.js and Symfony belong to "Frameworks (Full Stack)" category of the tech stack.

"Automatic server rendering and code splitting" is the top reason why over 9 developers like Next.js, while over 153 developers mention "Open source" as the leading cause for choosing Symfony.

Next.js and Symfony are both open source tools. It seems that Next.js with 38.2K GitHub stars and 4.6K forks on GitHub has more adoption than Symfony with 21K GitHub stars and 6.98K GitHub forks.

eTobb, Improvely, and Chooos are some of the popular companies that use Symfony, whereas Next.js is used by Avocode, OverCode Solutions, and CybrHome. Symfony has a broader approval, being mentioned in 355 company stacks & 267 developers stacks; compared to Next.js, which is listed in 79 company stacks and 66 developer stacks.

Advice on Next.js and Symfony
Needs advice

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 · 94.9K views

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
Decisions about Next.js and Symfony

We choose Next.js for our React framework because it's very minimal and has a very organized file structure. Also, it offers key features like zero setups, automatic server rendering and code splitting, typescript support. Our app requires some loading time to process the video, server-side rendering will allow our website to display faster than client-side rending.

See more
Fronted Rent

We’re a new startup so we need to be able to deliver quick changes as we find our product market fit. We’ve also got to ensure that we’re moving money safely, and keeping perfect records. The technologies we’ve chosen mix mature but well maintained frameworks like Django, with modern web-first and api-first front ends like GraphQL, NextJS, and Chakra. We use a little Golang sparingly in our backend to ensure that when we interact with financial services, we do so with statically compiled, strongly typed, and strictly limited and reviewed code.

You can read all about it in our linked blog post.

See more
Lucas Litton
Founder & CEO at Macombey · | 13 upvotes · 346.2K views

Next.js is probably the most enjoyable React framework our team could have picked. The development is an extremely smooth process, the file structure is beautiful and organized, and the speed is no joke. Our work with Next.js comes out much faster than if it was built on pure React or frameworks alike. We were previously developing all of our projects in Meteor before making the switch. We left Meteor due to the slow compiler and website speed. We deploy all of our Next.js projects on Vercel.

See more

Hey guys,

My backend set up is Prisma / GraphQL-Yoga at the moment, and I love it. It's so intuitive to learn and is really neat on the frontend too, however, there were a few gotchas when I was learning! Especially around understanding how it all pieces together (the stack). There isn't a great deal of information out there on exactly how to put into production my set up, which is a backend set up on a Digital Ocean droplet with Prisma/GraphQL Yoga in a Docker Container using Next & Apollo Client on the frontend somewhere else. It's such a niche subject, so I bet only a few hundred people have got a website with this stack in production. Anyway, I wrote a blog post to help those who might need help understanding it. Here it is, hope it helps!

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Next.js
Pros of Symfony
  • 41
    Automatic server rendering and code splitting
  • 35
    Built with React
  • 28
    Easy setup
  • 22
    Universal JavaScript
  • 21
  • 21
    Zero setup
  • 16
    Static site generator
  • 11
    Simple deployment
  • 11
    Incremental static regeneration
  • 10
    Just JavaScript
  • 9
    Frictionless development
  • 9
    Filesystem as an API
  • 8
  • 7
    Isomorphic React applications
  • 7
    Everything is a function
  • 7
    Well Documented
  • 6
    Not nuxt
  • 6
    Has many examples and integrations
  • 4
    Not vue
  • 2
    File based routing + hooks built in
  • 1
  • 1
    Not angular
  • 173
    Open source
  • 146
  • 127
    Dependency injection
  • 127
  • 120
  • 78
  • 72
  • 68
    Modular architecture
  • 45
    Smart programming
  • 42
  • 18
  • 14
    LTS releases
  • 9
    Easy to Learn
  • 9
  • 9
    Decoupled framework components
  • 8
  • 8
    Good practices guideline
  • 8
    Service container
  • 7
  • 6
  • 4

Sign up to add or upvote prosMake informed product decisions

Cons of Next.js
Cons of Symfony
  • 8
    Not Vue
  • 7
    Structure is weak compared to Angular(2+)
  • 2
    Is no Angular
  • 2
    Not flutter
  • 1
    Not Angular 2
  • 9
    Too many dependency
  • 7
    Lot of config files
  • 4
  • 2
    Feature creep
  • 1

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is Next.js?

Next.js is a minimalistic framework for server-rendered React applications.

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!

Jobs that mention Next.js and Symfony as a desired skillset
What companies use Next.js?
What companies use Symfony?
See which teams inside your own company are using Next.js or Symfony.
Sign up for Private StackShareLearn More

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

What tools integrate with Next.js?
What tools integrate with Symfony?

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

Blog Posts

What are some alternatives to Next.js and Symfony?
Create React App
Create React apps with no build configuration.
Gatsby lets you build blazing fast sites with your data, whatever the source. Liberate your sites from legacy CMSs and fly into the future.
Hexo is a fast, simple and powerful blog framework. It parses your posts with Markdown or other render engine and generates static files with the beautiful theme. All of these just take seconds.
A highly-extensible, open-source Node.js framework that enables you to create dynamic end-to-end REST APIs with little or no coding. Connect to multiple data sources, write business logic in Node.js, glue on top of your existing services and data, connect using JS, iOS & Android SDKs.
Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project.
See all alternatives