BT

InfoQ Homepage Actor Model Content on InfoQ

News

RSS Feed
  • Designing Reactive Systems Using DDD, Event Storming and Actors

    Domain-driven design (DDD) is often used for finding boundaries (bounded contexts) around microservices. But everything in domain-driven design (DDD) is not good for microservice, Lutz Huehnken claimed in a presentation at microxchg 2018 in Berlin where he discussed how DDD, Event Storming and the Akka-based Lagom framework can be used to build reactive systems.

  • QCon London: Asynchronous Event Architectures with or without Actors

    Synchronous request-response communication in microservices systems can be really complicated. Fortunately, asynchronous event-based architectures can be used to avoid this, Yaroslav Tkachenko claimed in a presentation at QCon London 2018, where he described his experiences with event-driven architectures and how Actors can be used in systems built on this architecture.

  • Focus on the Process, Not on Individual Microservices

    The key to success when working with a microservices based distributed system is to focus on the distributed process as a whole, not on the microservices themselves. The services are the least important part, Eric Ess claimed at the recent Microservices Conference in London, in his presentation on how to monitor distributed processes at jet.com.

  • The Long History of Microservices

    Microservices has a very long history, not as short as many believe. Neither was SOA invented in the 90s. We have been working with the core ideas behind services for five decades, Greg Young explained at the recent Microservices Conference in London, during his presentation on working with microservices.

  • Vaughn Vernon on Microservices and Domain-Driven Design

    Although a monolith can be modeled in a respectable way, often they are turned into a big ball of mud. This is caused by multiple domain models becoming entangled within the monolith, and in Vaughn Vernon's experience this can happen within a few weeks or months, he claimed in a presentation at the Scala Days conference earlier this year.

  • Q&A on Akka.NET 1.1 with Aaron Stannard

    Akka.NET 1.1 was recently released, bringing new features and performance improvements. InfoQ reached out to Aaron Stannard, maintainer of Akka.net, to learn more about Akka.Streams and Akka.Cluster. Stannard also explains how the roadmap is planned with regards to the JVM implementation of Akka.

  • Vaughn Vernon: Challenges in Software Development of Today

    Projects and development teams are struggling with poorly designed systems, with many developers dedicated to patching systems just to keep them alive. Largely the software development culture is broken, Vaughn Vernon claimed in his presentation at the Domain-Driven Design Europe conference earlier this year, talking about problems he has encountered but also about solutions to these problems.

  • A Whole System Based on Event Sourcing is an Anti-Pattern

    Command Query Responsibility Segregation (CQRS) was never meant to be the end goal of what we are trying to achieve, it is a stepping stone towards the ideas of Event sourcing, Greg Young stated in his presentation at the Domain-Driven Design Europe conference earlier this year. He noted though that just applying CQRS is still a valuable pattern.

  • Lagom, a New Microservices Framework

    Lightbend, the company behind Akka, has released an open source microservices framework, Lagom built on their Reactive Platform, in particular the Play Framework and the Akka family of products together with ConductR for deployment. By default, Lagom is message-driven and asynchronous, and using distributed CQRS persistence patterns with event sourcing as the primary implementation.

  • An Introduction to Actor Model, with Examples in Akka

    For developers who have experienced the problems with creating and managing multithreaded applications and are looking for a higher level of abstraction, Arun Manivannan has written a series of, so far, six blog posts explaining the principles of Actor model using an picture-rich visualization and some simple Akka examples.

  • Building a Reactive Process Manager Using Actor Model

    Vaughn Vernon describes a reactive process manager supervising the process of finding the best loan quotes from banks with a focus on the reactive part, using Actor model for the implementation with examples written in Scala using Akka and C# using his recently published Dotsero toolkit.

  • Experiences Building a Reactive Event-Driven CQRS Application

    CQRS and Event Sourcing provide a clear and concise way to build distributed applications that adhere to the reactive manifesto, Duncan DeVore claimed in a recent presentation sharing his experiences building a distributed application using Akka and Scala.

  • .NET Actor Model Implementations Differ in Approach

    Last week Vaughn Vernon published Dotsero, a .NET actor model toolkit that follows the Akka API and earlier this year a preview of the Orleans framework based on the Actor model was released by Microsoft Research. In a recent twitter discussion Vaughn and Sergey Bykov, lead of the Orleans project at Microsoft Research, discussed the different approaches taken in Orleans and Dotsero.

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.