Manuel Bernhardt continues his series about Akka Typed, the new Akka Actor API that brings significant advantages over the classic one. In his fourth entry, he takes a closer look at one of the most popular use-cases for Akka: event sourcing.
Manuel Bernhardt is back for part three of his series about Akka Typed, the new Akka Actor API that brings significant advantages over the classic one. In his third entry, he looks at one of the core concepts of actor systems: supervision and failure recovery.
Manuel Bernhardt continues his series about Akka Typed, the new Akka Actor API that brings significant advantages over the classic one. This second entry goes further down the route of building typed actor systems by looking at fundamental concepts necessary for the interaction between actors.
Manuel Bernhardt starts a new series about Akka Typed, the new Akka Actor API that brings significant advantages over the classic one. This first entry gets started by easing into the topic to show us a little bit of what it’s capable of. He talks about how to build a payment processor making the most of Akka Typed.
I have been using various forms of messaging for more than 30 years. Messaging has become second nature to me, but I empathize when others say that messaging is to them unfamiliar and intimidating. Since the Actor Model is based on message passing, it stands to reason that this programming model is likewise unfamiliar and intimidating to the same large group of people. There is no need for that. Let’s fix it.
Reactive programming promises higher performance of Enterprise Java applications with lower memory requirements. This promise is achieved by avoiding blocking calls that always lead to process and context switches in the operating system. Such context switches have a high CPU and memory overhead, which, of course, is reduced by fewer of such switches. However, this performance gain of reactive programming comes at the price of poorer maintainability of the software. But is the higher performance worth the price and what are the alternatives? Let’s take a closer look at this in this article.
Reactive Programming and observables are really powerful and go beyond what promises offer. They provide key features like laziness and the ability to cancel them. This allows you to add robustness into Angular 2 applications especially at the level of HTTP to finely control what is executed.
Tim Fox of Red Hat explains the basics of Vert.x and how it will help bring us into a reactive future.
Typesafe’s Jonas Bonér explains why the Reactive Manifesto is key for the for the future of high quality development – and why its good news for Java devs.
Jamie Allen holds forth on Java 8 Lambda hype, Scala love, and breaking down reactive programming. Filmed backstage at JAX London 2013.