Need advice about which tool to choose?Ask the StackShare community!
Next.js vs PHP-MVC: What are the differences?
Next.js and PHP-MVC can be primarily classified as "Frameworks (Full Stack)" tools.
Next.js and PHP-MVC are both open source tools. Next.js with 38.7K GitHub stars and 4.69K forks on GitHub appears to be more popular than PHP-MVC with 1.25K GitHub stars and 494 GitHub forks.
CircleCI, Avocode, and OverCode Solutions are some of the popular companies that use Next.js, whereas PHP-MVC is used by BetRocket, Sequoia Waste Solutions, and Digimedia ENVISION. Next.js has a broader approval, being mentioned in 82 company stacks & 69 developers stacks; compared to PHP-MVC, which is listed in 11 company stacks and 8 developer stacks.
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.
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.
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.
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!
Pros of Next.js
- Automatic server rendering and code splitting46
- Built with React40
- Easy setup33
- Zero setup22
- Static site generator20
- Simple deployment12
- Incremental static regeneration12
- Frictionless development10
- Filesystem as an API10
- Everything is a function9
- Well Documented9
- Has many examples and integrations8
- Isomorphic React applications7
- File based routing + hooks built in4
Pros of PHP-MVC
- Easy to Learn1
Sign up to add or upvote prosMake informed product decisions
Cons of Next.js
- Structure is weak compared to Angular(2+)9