Need advice about which tool to choose?Ask the StackShare community!

Akka

738
754
+ 1
79
Play

680
491
+ 1
491
Add tool

Akka vs Play: What are the differences?

Developers describe Akka as "Build powerful concurrent & distributed applications more easily". Akka is a toolkit and runtime for building highly concurrent, distributed, and resilient message-driven applications on the JVM. On the other hand, Play is detailed as "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.

Akka belongs to "Concurrency Frameworks" category of the tech stack, while Play can be primarily classified under "Frameworks (Full Stack)".

"Great concurrency model" is the primary reason why developers consider Akka over the competitors, whereas "Scala" was stated as the key factor in picking Play.

Akka 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 Akka with 10.1K GitHub stars and 3.04K GitHub forks.

Coursera, Zalando, and Keen are some of the popular companies that use Play, whereas Akka is used by Asana, Rainist, and ContentSquare. Play has a broader approval, being mentioned in 112 company stacks & 47 developers stacks; compared to Akka, which is listed in 76 company stacks and 57 developer stacks.

Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Akka
Pros of Play
  • 29
    Great concurrency model
  • 15
    Fast
  • 10
    Actor Library
  • 9
    Open source
  • 6
    Resilient
  • 5
    Scalable
  • 5
    Message driven
  • 78
    Scala
  • 55
    Built on akka
  • 55
    Web-friendly architecture
  • 50
    Stateless
  • 47
    High-scalable
  • 46
    Fast
  • 39
    Open source
  • 34
    Java
  • 27
    High velocity
  • 24
    Fun
  • 9
    Lightweight
  • 8
    Non-blocking io
  • 5
    Developer friendly
  • 5
    Simple template engine
  • 4
    Scalability
  • 3
    Pure love
  • 2
    Resource efficient

Sign up to add or upvote prosMake informed product decisions

Cons of Akka
Cons of Play
  • 3
    Mixing futures with Akka tell is difficult
  • 2
    Closing of futures
  • 2
    No type safety
  • 1
    Typed actors still not stable
  • 0
    Very difficult to refactor
  • 3
    Evolves fast, keep up with releases
  • 1
    Unnecessarily complicated

Sign up to add or upvote consMake informed product decisions

What is Akka?

Akka is a toolkit and runtime for building highly concurrent, distributed, and resilient message-driven applications on the JVM.

What is Play?

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.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Akka?
What companies use Play?
See which teams inside your own company are using Akka or Play.
Sign up for Private StackShareLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Akka?
What tools integrate with Play?
What are some alternatives to Akka and Play?
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.
Scala
Scala is an acronym for “Scalable Language”. This means that Scala grows with you. You can play with it by typing one-line expressions and observing the results. But you can also rely on it for large mission critical systems, as many companies, including Twitter, LinkedIn, or Intel do. To some, Scala feels like a scripting language. Its syntax is concise and low ceremony; its types get out of the way because the compiler can infer them.
Erlang
Some of Erlang's uses are in telecoms, banking, e-commerce, computer telephony and instant messaging. Erlang's runtime system has built-in support for concurrency, distribution and fault tolerance. OTP is set of Erlang libraries and design principles providing middle-ware to develop these systems.
Kafka
Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
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.
See all alternatives
How developers use Akka and Play
datapile uses
Play

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.

papaver uses
Akka

we used akka as our concurrency system at talenthouse. had the chance to write several worker. we used both akka messaging and rabbitmq to communicate. quite a slick system, was fun writing it in scala.

Stanislaus Madueke uses
Play

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

fileee GmbH uses
Akka

Akka powers our asynchronous document upload processor, handling e.g. tasks for OCR, thumbnail generation and document analysis.

Ascendify uses
Play

Moving some micro services to Play Framework with Scala

papaver uses
Play

used play at talenthouse. uber powerful backend.

Jovi Kao uses
Play

API server framework