How to migrate from Akka to Pekko?

Since Pekko is a fork of Akka 2.6.x with some features from 2.7.0, migration involves updating dependencies and adapting to Pekko's Apache 2.0 license. Check the official documentation on pekko.apache.org for specific steps and compatibility notes.

Pekko vs Akka: which one should I choose for a new project?

Pekko uses the permissive Apache 2.0 license, making it better for open-source or commercial projects seeking freedom from licensing restrictions. However, Akka might have a more mature ecosystem, so weigh licensing needs against community support.

What JDK version is required for Pekko?

Pekko requires JDK 17 or later, as specified in the prerequisites section of the README. Ensure your development environment and build tools like sbt are configured accordingly to avoid compatibility issues.

How to set up Pekko persistence for event sourcing?

Pekko provides libraries for durable state management and event sourcing. Refer to the persistence module documentation on pekko.apache.org for implementation details, examples, and best practices tailored to distributed systems.

Does Pekko support reactive streams?

Yes, Pekko includes reactive stream processing for handling data flows asynchronously, as mentioned in the key features. This is part of the streams library, enabling backpressure and efficient data handling in distributed applications.

How to build Pekko from source on Windows?

The README mentions issues with Windows builds (#829), so it's recommended to use Linux or Mac for development. If necessary, seek community solutions or workarounds in GitHub discussions, as the CI build is Linux-based.

Open-Awesome

Apache Pekko

Apache-2.0Scala

Build highly concurrent, distributed, and resilient message-driven applications using Java/Scala with the Actor Model.

Visit Website GitHub

1.6k stars208 forks0 contributors

What is Apache Pekko?

Apache Pekko is an open-source framework for building highly concurrent, distributed, and resilient message-driven applications using Java or Scala. It leverages the Actor Model to provide intuitive abstractions for managing concurrency, fault tolerance, and scalability, solving the complexities of building robust distributed systems.

Target Audience

Java and Scala developers building concurrent, distributed, or resilient applications, such as microservices, real-time systems, or data processing pipelines.

Value Proposition

Developers choose Pekko for its powerful Actor Model implementation, which simplifies concurrency and distribution, and its comprehensive libraries for persistence, streams, and HTTP. As a fork of Akka under the Apache 2.0 license, it offers a permissively licensed alternative with similar capabilities.

Overview

Build highly concurrent, distributed, and resilient message-driven applications using Java/Scala

Use Cases

Best For

Building highly concurrent microservices architectures
Developing fault-tolerant distributed systems with supervision strategies
Creating real-time data processing and stream processing applications
Implementing resilient message-driven backends for web or mobile apps
Scaling applications elastically across multiple nodes or clusters
Migrating from Akka to a permissively licensed framework

Not Ideal For

Building simple REST APIs or monoliths without concurrency or distribution needs
Teams with tight deadlines and no prior experience in actor-based systems or Scala
Projects requiring extensive Windows development support, due to reported build issues
Applications that prioritize rapid prototyping over long-term resilience and scalability

Pros & Cons

Pros

Actor Model Abstraction

Provides intuitive high-level abstractions for concurrency and distributed computing, simplifying the development of robust systems, as emphasized in the project description and philosophy.

Permissive Licensing

As a fork of Akka under the Apache 2.0 license, it offers a free and open-source alternative, mentioned in the README as a key differentiator from Akka's Business Source License.

Comprehensive Feature Set

Includes built-in libraries for persistence, streams, and HTTP, providing a full toolkit for distributed applications, based on the key features listed in the README.

Built-in Resilience

Features fault tolerance and supervision strategies for handling failures gracefully, which is a core part of its resilience and elasticity claims.

Cons

Windows Build Challenges

The README notes reports of issues when building with Windows (#829), which can complicate development and setup on that platform, limiting cross-platform ease.

Steep Learning Curve

Requires deep understanding of the Actor Model and distributed systems concepts, making it less accessible for teams unfamiliar with these paradigms, despite its abstractions.

Ecosystem Immaturity

As a fork, it might have fewer third-party integrations and community resources compared to established frameworks like Akka, potentially slowing down development and troubleshooting.

Open Source Alternative To

Apache Pekko is an open-source alternative to the following products:

Akka

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

Frequently Asked Questions

Related Projects

Akka Streams

A platform to build and run apps that are elastic, agile, and resilient. SDK, libraries, and hosted environments.

Stars13,278

Forks3,543

Last commit11 days ago

Aeron

Efficient reliable UDP unicast, UDP multicast, and IPC message transport

Stars8,753

Forks1,070

Last commit20 hours ago

pulsar

Event driven concurrent framework for Python

Stars1,848

Forks161

Last commit6 years ago

Turbine

SSE Stream Aggregator

Stars833

Forks251

Last commit3 years ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub