Play vs Hoodie

Overview

Play

Stacks752

Followers609

Votes496

GitHub Stars12.6K

Forks4.1K

Hoodie

Stacks14

Followers29

Votes16

Hoodie vs Play: What are the differences?

Hoodie: A fast offline-first architecture for webapps. Super-simple user management & storage. Great for mobile. We want to enable you to build complete web apps in days, without having to worry about backends, databases or servers, all with an open source library that's as simple to use as jQuery; Play: The High Velocity Web Framework For Java and Scala. Play Framework makes it easy to build web applications with Java & Scala. Play is based on a lightweight, stateless, web-friendly architecture. Built on Akka, Play provides predictable and minimal resource consumption (CPU, memory, threads) for highly-scalable applications.

Hoodie and Play belong to "Frameworks (Full Stack)" category of the tech stack.

"JSON" is the top reason why over 3 developers like Hoodie, while over 73 developers mention "Scala" as the leading cause for choosing Play.

Hoodie and Play are both open source tools. Play with 11.2K GitHub stars and 3.77K forks on GitHub appears to be more popular than Hoodie with 3.51K GitHub stars and 314 GitHub forks.

🔥 Trending in Frameworks on StackShare

Node.js Frameworks

A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications

Try it View Docs Alternatives

Try

566

165k

Advice on Play, Hoodie

Leonardo

Project manager and web developer at Revo Digital

Mar 22, 2021

Needs adviceon

TypeScript

Rails

Scala

In the past few months, a project we're working on grew up quite fast. Since we're adding more and more features, I'm considering migrating my Express/TS REST API towards a more solid and more "enterprise-like" framework. Since I am experienced with TypeScript but not so much with Rails nor Play (Scala), I'd like to have some advice on which one could provide the best development experience, and most importantly, the smoothest paradigm transition from the JS/TS world. I've worked on some personal project with Rails, but I've found the Ruby language really distant from what the TypeScript ecosystem and syntax are, whereas on the opposite - during the brief tours I've taken in the past weeks - it's been a pleasure coding in Scala. Obviously, there are some key differences between the two languages - and the two frameworks consequently - but despite all the ROR automation and ease of use I don't despise at all Scala's pragmatic and great features such as static typing, pattern matching, and type inference. So... Please help me out with the choice! Regards

2.74M views2.74M

Comments

Hosam

Senior Software Engineer

Apr 18, 2021

Review

If software performance is your top priority, then Scala/Play is probably best. If developer productivity is your top priority, then Ruby on Rails is the best choice in my opinion.

The Rails framework is batteries-included. The framework takes care of many things by default so that you don't have to. Logging, security, etc. It's also well-integrated; for example, controllers understand models out of the box. I had a better experience with RoR than with Play.

On the other hand, Scala and the JVM are more performant in general, so they can scale to serve more requests per second on the same hardware.

If you're considering serverless functions, then Scala is probably a better choice because it would be faster to load, giving you better economics.

53.4k views53.4k

Comments

Detailed Comparison

Play	Hoodie
Play Framework makes it easy to build web applications with Java & Scala. Play is based on a lightweight, stateless, web-friendly architecture. Built on Akka, Play provides predictable and minimal resource consumption (CPU, memory, threads) for highly-scalable applications.	We want to enable you to build complete web apps in days, without having to worry about backends, databases or servers, all with an open source library that's as simple to use as jQuery.
-	Offline by default: Hoodie stores data locally first and syncs them in the background when possible. Great for mobile applications;One-line signup/signin/signout/resend password and other account management functions;Document-based storage with CouchDB: no building database schemas;Event system: easily listen for changes in the data to trigger view updates;JavaScript and JSON on every layer. Even the database queries are JS;Convenient, super simple local dev setup that optionally even configures .dev-domains for you;Deploy to Nodejitsu with minimal effort;Flexible, npm-based plugin system in case you need more capability;Send multi-part emails with attachments from the client
Statistics
GitHub Stars 12.6K	GitHub Stars -
GitHub Forks 4.1K	GitHub Forks -
Stacks 752	Stacks 14
Followers 609	Followers 29
Votes 496	Votes 16
Pros & Cons
Pros 81 Scala 55 Web-friendly architecture 55 Built on akka 50 Stateless 47 High-scalable Cons 3 Evolves fast, keep up with releases 1 Unnecessarily complicated	Pros 4 JSON 4 Reduces boilerplate 3 Offline first 2 Open source 2 Mobile friendly

What are some alternatives to Play, Hoodie?

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.

Symfony

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

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.