CQRS is a pattern for decoupling write operations from read operations. This short video illustrates how to implement CQRS with Akka 2.6 by reading tagged events. The video continues from where the Event Sourcing video left off.
A four-minute video explaining why it is bad to block inside an actor, and how you can use custom dispatchers to manage blocking when you cannot avoid it. The slides and sample code are available on GitHub.
A four-minute video explaining why it is bad to block inside an actor, and how you can use custom dispatchers to manage blocking when you cannot avoid it. The slides and sample code are available on GitHub.
An eight minute video demonstrating how to use Event Sourcing in Akka 2.6. Sample code from the Akka CQRS example project (Java or Scala). Including how to integrate with Cluster Sharding and Akka HTTP.
A ten minute overview of Akka Cluster Sharding, how it can help, and a code walk through of basic usage of the Akka Cluster Sharding API. We review the architecture and code in the Akka Cluster Sharding sample Scala app, including how to integrate Akka HTTP with Cluster Sharding.
A ten minute overview of Akka Cluster Sharding, how it can help, and a code walk through of basic usage of the Akka Cluster Sharding API. We review the architecture and code in the Akka Cluster Sharding sample Scala app, including how to integrate Akka HTTP with Cluster Sharding.
A short video where we walk through the basics of the actor model writing an actor in Java with the new Actor APIs Akka 2.6
A short video where we walk through the basics of the actor model writing an actor in Java with the new Actor APIs Akka 2.6
Today’s applications are expected to support a multitude of devices, employ hybrid cloud deployments, persist petabytes of data, deliver millisecond response time and have near-perfect reliability. Traditional patterns and practices for enterprise Java application development simply can’t support these demands, or are so complicated that entire systems can be brought down by single points of failure.
Most likely, your job is heavily focused on helping your organization modernize for the digital era. As the days of purely Object-Oriented Programming and related frameworks come to a close, enterprises migrating to distributed, cloud infrastructures are embracing a different approach: the Actor Model.
Like most things in life, in software there exists an Old and a New way of doing things. The growth of computing power, increase in the sheer number of users, cheaper and more available hardware, and the explosive IoT market mandates that we build our systems using modern methods that diverge from past.
Since its stable release in 2016, Akka Streams is quickly becoming the de facto standard integration layer between various Streaming systems and products. Enterprises like PayPal, Intel, Samsung and Norwegian Cruise Lines see this is a game changer in terms of designing Reactive streaming applications by connecting pipelines of back-pressured asynchronous processing stages.