Backbone.js vs Symfony

Overview

Backbone.js

Stacks7.5K

Followers3.5K

Votes675

GitHub Stars28.1K

Forks5.3K

Symfony

Stacks8.5K

Followers6.2K

Votes1.1K

GitHub Stars30.7K

Forks9.7K

Backbone.js vs Symfony: What are the differences?

Developers describe Backbone.js as "Give your JS App some Backbone with Models, Views, Collections, and Events". Backbone supplies structure to JavaScript-heavy applications by providing models key-value binding and custom events, collections with a rich API of enumerable functions, views with declarative event handling, and connects it all to your existing application over a RESTful JSON interface. On the other hand, Symfony is detailed as "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.

Backbone.js can be classified as a tool in the "Javascript MVC Frameworks" category, while Symfony is grouped under "Frameworks (Full Stack)".

"Javascript structure", "Models" and "Simple" are the key factors why developers consider Backbone.js; whereas "Open source", "Php" and "Community" are the primary reasons why Symfony is favored.

Backbone.js and Symfony are both open source tools. Backbone.js with 27.5K GitHub stars and 5.72K forks on GitHub appears to be more popular than Symfony with 21K GitHub stars and 6.98K GitHub forks.

According to the StackShare community, Backbone.js has a broader approval, being mentioned in 1066 company stacks & 213 developers stacks; compared to Symfony, which is listed in 355 company stacks and 267 developer stacks.

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)

Manual

Advice on Backbone.js, Symfony

Fabian

May 5, 2020

Needs adviceon

GraphQL

C++

Symfony

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

Backbone.js	Symfony
Backbone supplies structure to JavaScript-heavy applications by providing models key-value binding and custom events, collections with a rich API of enumerable functions, views with declarative event handling, and connects it all to your existing application over a RESTful JSON interface.	It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP..
Statistics
GitHub Stars 28.1K	GitHub Stars 30.7K
GitHub Forks 5.3K	GitHub Forks 9.7K
Stacks 7.5K	Stacks 8.5K
Followers 3.5K	Followers 6.2K
Votes 675	Votes 1.1K
Pros & Cons
Pros 135 Javascript structure 101 Models 98 Simple 76 Restful 59 Easy api Cons 1 Requires underscore.js	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
Integrations
No integrations available	CakePHP PHP ReactPHP

What are some alternatives to Backbone.js, Symfony?

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 is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

AngularJS

AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding.

Django

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

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 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

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.

Vue.js

It is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API.

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 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.

Related Comparisons

Backbone.js vs Symfony