Play vs Spring Boot: What are the differences?
What is 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.
What is Spring Boot? Create Spring-powered, production-grade applications and services with absolute minimum fuss. 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.
Play and Spring Boot belong to "Frameworks (Full Stack)" category of the tech stack.
"Scala", "Web-friendly architecture" and "Built on akka" are the key factors why developers consider Play; whereas "Powerful and handy", "Easy setup" and "Java" are the primary reasons why Spring Boot is favored.
Play and Spring Boot are both open source tools. It seems that Spring Boot with 39.3K GitHub stars and 25.5K forks on GitHub has more adoption than Play with 11.2K GitHub stars and 3.75K GitHub forks.
MIT, PedidosYa, and Intuit are some of the popular companies that use Spring Boot, whereas Play is used by Keen, Kifi, and Drillist.com. Spring Boot has a broader approval, being mentioned in 326 company stacks & 585 developers stacks; compared to Play, which is listed in 111 company stacks and 46 developer stacks.
What is Play?
What is Spring Boot?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
Sign up to add, upvote and see more consMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Some may wonder why did we choose Grails ? Really good question :) We spent quite some time to evaluate what framework to go with and the battle was between Play Scala and Grails ( Groovy ). We have enough experience with both and, to be honest, I absolutely in love with Scala; however, the tipping point for us was the potential speed of development. Grails allows much faster development pace than Play , and as of right now this is the most important parameter. We might convert later though. Also, worth mentioning, by default Grails comes with Gradle as a build tool, so why change?
I use Spring-Boot because it almost let you get things done quickly for a JVM-target project, with auto configuration components and dependency management starters. It is almost perfectly tailored for microservices applications development with a single unit deployment artifact (JAR) along with support for Service Registry and Discovery, Circuit Breaker pattern...
Any third-party library or any back-end service would perfectly integrate well since Spring offers integration support for most of mainstream services, let it be a RDBMS service, a NoSQL database, a Message Broker...
Coming to day-to-day development, Spring-Boot enjoys a great community so you can get support, direction, focused guidance from almost everywhere.
We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.
To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas
To build #Webapps we decided to use Angular 2 with RxJS
#Devops - GitHub , Travis CI , Terraform , Docker , Serverless
Since you said that your middleware will be accessing DB and expose API, you can go with Node.js. It will make your development fast and easy. Suppose in future you will add some business logic you can choose Java with Spring Boot or Python with Flask / Django. NOTE: Language or framework doesn't matter. Choose based on your programming knowledge.
spring boot allow my team to start building web services quickly and package it in a stand alone application
Play is a central framework/component/library (not sure what to call things these days) in Scala. We <3 Scala, and therefore we <3 Play.
Play is on of several frameworks we are prototyping and vetting for various public-facing websites, and may ultimately be the framework behind the main datapile.io website.
Spring-Boot allows us to create stand-alone web servers and helps us configure many of our dependencies with sane default, while maintaining flexibility where we need it.
I used Play to build a configuration UI for the service, which let you create and manage the menus (a hierarchical tree of options and actions).