#akka

After 18 months of fighting Play Framework 2.8’s request lifecycle overhead in our high-throughput...

What is the Actor Model? Overview of the Actor Model: The Actor Model is a mathematical model for...

Kafka streams is an amazing abstraction for working with Kafka and has amazing JVM support. However,...

We often recommend asynchronous communication between Microservices by using a message broker, such as Kafka. What if you could have the same advantages of loosely coupled and reliable message delivery without the burden and cost of operating the broker infrastructure? As a bonus, you would gain low latency cross region delivery of messages.

Architecture Diagram generated from repo source Originally Posted...

Connecting an Akka streamflow with a source

A post by Rajkumar Balakrishnan

Rarely, during my life as a developer, I found pre-packaged solutions that fit my problem so well. Design patterns are an abstraction of both problems and solutions. So, they often need some kind of customization on the specific problem. While I was developing my concrete instance of Actorbase specification, I came across the Cameo pattern. It enlighted my way and my vision about how to use Actors profitably. Let's see how and why.

I am a battle-hardened, hands-on and still enthusiastic software technologist/programmer. I help SMEs conceptualize, prototype and build, deployable and maintainable backend stack, by using some of the latter-day technologies and mentor their engineering teams. Unlearning and then learning, is an activity I am always involved with. I am looking for opportunities in Europe