JBoss Seam vs Symfony

Overview

Symfony

Stacks8.5K

Followers6.2K

Votes1.1K

GitHub Stars30.7K

Forks9.7K

JBoss Seam

Stacks8

Followers15

Votes0

GitHub Stars32

Forks51

JBoss Seam vs Symfony: What are the differences?

## Introduction
This Markdown code will provide key differences between JBoss Seam and Symfony.

1. **Architecture**:
   Symfony is a PHP framework that follows the model-view-controller (MVC) architecture, whereas JBoss Seam is a Java framework that integrates different Java EE technologies to provide a unified development model.

2. **Development Language**:
   Symfony is based on PHP language, while JBoss Seam is based on Java language.

3. **Community Support**:
   Symfony has a large and active community with extensive documentation and support resources available, whereas JBoss Seam has a smaller community and fewer resources for developers.

4. **Ease of Use**:
   Symfony is known for its simplicity and ease of use, with clear and well-defined conventions, making it easier for developers to learn and use, while JBoss Seam may have a steeper learning curve due to its complex architecture and integration of various technologies.

5. **Update Frequency**:
   Symfony has a regular release cycle with frequent updates and improvements, ensuring that developers have access to the latest features and enhancements, whereas JBoss Seam may have longer intervals between updates, potentially leading to slower adoption of new technologies and features.

6. **Framework Ecosystem**:
   Symfony has a rich ecosystem of plugins and extensions that enhance its functionality and provide additional features, while JBoss Seam may have a more limited ecosystem in terms of available plugins and extensions.

In Summary, the key differences between JBoss Seam and Symfony lie in their architecture, development language, community support, ease of use, update frequency, and framework ecosystem.

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 Symfony, JBoss Seam

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

Symfony	JBoss Seam
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 application framework for Enterprise Java. It is inspired by the following principles: One kind of "stuff" Seam defines a uniform component model for all business logic in your application.
-	Solder; Apache DeltaSpike; Seam Catch; Apache DeltaSpike; Seam Config; Apache Aries
Statistics
GitHub Stars 30.7K	GitHub Stars 32
GitHub Forks 9.7K	GitHub Forks 51
Stacks 8.5K	Stacks 8
Followers 6.2K	Followers 15
Votes 1.1K	Votes 0
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	No community feedback yet
Integrations
CakePHP PHP ReactPHP	Java Jira Java EE

What are some alternatives to Symfony, JBoss Seam?

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.

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.

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.

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

JBoss Seam vs Symfony: What are the differences?

## Introduction
This Markdown code will provide key differences between JBoss Seam and Symfony.

1. **Architecture**:
   Symfony is a PHP framework that follows the model-view-controller (MVC) architecture, whereas JBoss Seam is a Java framework that integrates different Java EE technologies to provide a unified development model.

2. **Development Language**:
   Symfony is based on PHP language, while JBoss Seam is based on Java language.

3. **Community Support**:
   Symfony has a large and active community with extensive documentation and support resources available, whereas JBoss Seam has a smaller community and fewer resources for developers.

4. **Ease of Use**:
   Symfony is known for its simplicity and ease of use, with clear and well-defined conventions, making it easier for developers to learn and use, while JBoss Seam may have a steeper learning curve due to its complex architecture and integration of various technologies.

5. **Update Frequency**:
   Symfony has a regular release cycle with frequent updates and improvements, ensuring that developers have access to the latest features and enhancements, whereas JBoss Seam may have longer intervals between updates, potentially leading to slower adoption of new technologies and features.

6. **Framework Ecosystem**:
   Symfony has a rich ecosystem of plugins and extensions that enhance its functionality and provide additional features, while JBoss Seam may have a more limited ecosystem in terms of available plugins and extensions.

In Summary, the key differences between JBoss Seam and Symfony lie in their architecture, development language, community support, ease of use, update frequency, and framework ecosystem.

JBoss Seam vs Symfony

Overview