days
0
2
hours
1
2
minutes
3
5
seconds
5
9

#akka

SMACK — Next generation Big Data

Big Data becomes Fast Data

Big Data is changing. Buzzwords such as Hadoop, Storm, Pig and Hive are not the darlings of the industry anymore —they are being replaced by a powerful duo: Fast Data and SMACK. Such a fast change in such a (relatively) young ecosystem begs the following question: What is wrong with the current approach? What is the difference between Fast and Big Data? And what is SMACK?

Akka anti-patterns: being out of touch with the hardware

Choosing Akka as a tool is often – if not always – driven by the need for good performance. Surely, the actor model itself is appealing as a means for organizing and reasoning about code, but this isn’t in itself a good reason enough to use the Akka toolkit.

Event-driven architecture

Reactive Microservices with Scala and Akka

In this article, Vaughn Vernon, author of “Implementing Domain- Driven Design”, “Reactive Messaging Patterns with the Actor Model”, and “Domain-Driven Design Distilled”, will teach you a first approach method to designing microservices, giving you a workable foundation to build on. He will introduce you to reactive software development and summarize how you can use Scala and Akka as a go-to toolkit for developing reactive microservices.

Out now!

JAX Magazine — October 2016 — Reactive programming with Scala, Lagom, Spark, Akka and Play

Reactive programming is gaining momentum but people are still reluctant to jump on the bandwagon. To help you overcome the fear of the unknown, we decided to ask Scala, Lagom, Spark, Akka and Play experts to explain how these elements coexist and work together to create a reactive universe. This JAX Magazine issue is packed with goodies — it’s our treat!

Why running 1000+ actor systems on one JVM is a bad idea

Akka anti-patterns: too many actor systems

Admittedly I’ve seen this one in use only one time, but it was one time too many. For some reason I keep seeing clients come up with this during design discussions and reviews, therefore it makes it into the list of Akka anti-patterns.

Beware of missteps

Akka anti-patterns: data races

When working with actors, you should always respect the following guideline: Do not, under any circumstances, close over mutable state. Since the actor model is a model, not a framework, it is up to you to make sure that you do, indeed, follow this guideline. Akka will not magically warn you if you misstep; however, your application will begin to act weirdly. In this article, Manuel Bernhardt explores a few ways in which you could misstep.

Mixing business logic and failure handling

Akka anti-patterns: Flat actor hierarchies

One of the fundamental ideas built into Akka is the one of failure handling through parental supervision. In other words, this means agencing actors in such a way that parent actors that depend upon the correct execution of a child to perform their work are also responsible for deciding what to do when one child actor crashes.

Anti-pattern #1

Akka anti-patterns: shared mutable state

When I work with clients on designing actor systems there are a few anti-patterns that seem to make it into initial, non-reviewed designs no matter what. In this series of short articles I would like to cover a few of those.

Dedicated to doing the right thing

The Swiss army knife of reactive systems on the JVM

Akka is in many ways a very innovative and yet robust technology. Now that it has become generally accepted that microservice-oriented architectures are a good idea, Akka will play an even more important role in the reactive system at large and already serves as a foundation for other reactive technologies such as the Play Framework and Lagom.