StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Frameworks
  4. Frameworks
  5. Redwood vs Symfony

Redwood vs Symfony

OverviewDecisionsComparisonAlternatives

Overview

Symfony
Symfony
Stacks8.5K
Followers6.2K
Votes1.1K
GitHub Stars30.7K
Forks9.7K
Redwood
Redwood
Stacks28
Followers50
Votes6

Redwood vs Symfony: What are the differences?

1. **Architecture**: Redwood uses a full-stack JavaScript framework, including React, GraphQL, and Prisma, while Symfony is a PHP framework that follows the MVC architecture. 2. **Community Support**: Symfony has a larger and more established community with extensive documentation and resources, whereas Redwood is a newer framework with a growing but smaller community. 3. **Language**: Redwood utilizes JavaScript for both frontend and backend development, while Symfony is primarily based on PHP, which may affect the developer's language preferences and compatibility with existing codebases. 4. **Performance**: Symfony is known for its high performance and scalability, with optimizations for handling large projects, whereas Redwood, being a newer framework, may have some performance limitations that are being actively improved. 5. **Flexibility**: Symfony is highly flexible and allows developers to customize and extend functionalities easily, while Redwood follows more conventions over configurations approach, which provides a more straightforward structure but limited customization options. 6. **Learning Curve**: Due to its extensive features and configurations, Symfony may have a steeper learning curve for beginners, while Redwood aims to be more user-friendly and straightforward for new developers to pick up and start building applications quickly.

In Summary, Redwood and Symfony differ in terms of architecture, community support, language, performance, flexibility, and learning curve.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Symfony, Redwood

Fabian
Fabian

May 5, 2020

Needs adviceonGraphQLGraphQLC++C++SymfonySymfony

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.

Golang: It's newer than PHP, I've heard of its good performance, and it would be nice to learn a new (growing) language.

2.4M views2.4M
Comments

Detailed Comparison

Symfony
Symfony
Redwood
Redwood

It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP..

It is an opinionated, full-stack, serverless web application framework that will allow you to build and deploy JAMstack applications with ease. Imagine a React frontend, statically delivered by CDN, that talks via GraphQL to your backend running on AWS Lambdas around the world, all deployable with just a git push—that's Redwood.

-
Opinionated defaults for formatting, file organization, webpack, Babel, and more; Simple but powerful routing (all routes defined in one file) with dynamic (typed) parameters, constraints, and named route functions (to generate correct URLs); Automatic page-based code-splitting; Boilerplate-less GraphQL API construction; Cells: a declarative way to fetch data from the backend API; Generators for pages, layouts, cells, SDL, services, etc; Scaffold generator for CRUD operations around a specific DB table; Forms with easy client- and/or server-side validation and error handling; Hot module replacement (HMR) for faster development; Database migrations (via Prisma 2); First class JAMstack-style deployment to Netlify
Statistics
GitHub Stars
30.7K
GitHub Stars
-
GitHub Forks
9.7K
GitHub Forks
-
Stacks
8.5K
Stacks
28
Followers
6.2K
Followers
50
Votes
1.1K
Votes
6
Pros & Cons
Pros
  • 177
    Open source
  • 149
    Php
  • 130
    Community
  • 129
    Dependency injection
  • 122
    Professional
Cons
  • 10
    Too many dependency
  • 8
    Lot of config files
  • 4
    YMAL
  • 3
    Feature creep
  • 1
    Bloated
Pros
  • 2
    Cells
  • 2
    React+Prisma+GraphQL
  • 1
    Storybook integrated development
  • 1
    Easy setup + generators
Integrations
CakePHP
CakePHP
PHP
PHP
ReactPHP
ReactPHP
React
React
AWS Lambda
AWS Lambda
Netlify
Netlify
GraphQL
GraphQL

What are some alternatives to Symfony, Redwood?

Node.js

Node.js

Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

Rails

Rails

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

Django

Django

Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Laravel

Laravel

It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.

.NET

.NET

.NET is a general purpose development platform. With .NET, you can use multiple languages, editors, and libraries to build native applications for web, mobile, desktop, gaming, and IoT for Windows, macOS, Linux, Android, and more.

ASP.NET Core

ASP.NET Core

A free and open-source web framework, and higher performance than ASP.NET, developed by Microsoft and the community. It is a modular framework that runs on both the full .NET Framework, on Windows, and the cross-platform .NET Core.

Spring

Spring

A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments.

Spring Boot

Spring Boot

Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration.

Android SDK

Android SDK

Android provides a rich application framework that allows you to build innovative apps and games for mobile devices in a Java language environment.

Phoenix Framework

Phoenix Framework

Phoenix is a framework for building HTML5 apps, API backends and distributed systems. Written in Elixir, you get beautiful syntax, productive tooling and a fast runtime.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase