ReActed: a distributed, actor-based and replay oriented Java framework

It's not everyday that someone comes up with a full-blown actor framework.

I am very happy to host an event about ReActed (https://www.reacted.io), a Java framework to build reactive, distributed actor-based microservices. The author Pierre Falda will introduce us to his work, show some use cases and explain what are the main differences with existing solution like Akka.

Sponsor for the night is Lunatech (https://lunatech.nl), the most community-friendly software consultancy that I know. I am glad that we can keep hosting events together even during these times of remoteness ❤️

17:30: streaming starts & intro
17:40: ReActed talk (see below)
18:20: Q&A until closure

ReActed talk:
Choosing the best technology for a project is far from being a purely technological decision. You have to consider different factors such as learning curve, interactions, extensibility, manpower availability, costs, support, ecosystem, future-proofness.
A technology or an approach can deeply shape the way the applications are designed within your company. Poor flexibility, extensibility or testing capabilities directly impact the maintenance costs, influencing how quickly a business can change, evolve or the quality of the deliveries.
ReActed aims to be a new opensource project meant to address most of the above points. It is a full Java 11 implementation of a distributed actor framework that provides:

• Sane defaults and a lot of sugar that allow to be easily and quickly productive
• Actor paradigm implementation for creating reactive applications with automatic vertical scalability
• A location agnostic communication system that leverages the programmer from writing any networking, routing or technology specific code
• Automatic cluster formation and maintenance that allows automatic horizontal scalability
• Driver based approach: local/remote communication and service registries are managed through technology drivers. A ReActed node can use any technology (also at the same time) to communicate with other nodes as soon as a specific driver is available, adapting to virtually any pre existent setup.
• Out of the box flow control and fully compliant reactive-streams for local and distributed streams
• Local and remote message subscription system for quickly creating choreography oriented systems
• Replay capabilities for resetting the state of the system to almost any given time
• Graph API for declarative distributed pipelines definition under development

This presentation will go in some details of the above features and will show some use case. This will be followed by a QA session for collecting feedbacks and ideas

Speaker Bio:
Pierre is a former CTO, startupper and fearless software engineer with over 15 years of experience in a broad spectrum of technologies and industries: research, security, Linux kernel, embedded, space, avionics, finance and saas platforms.
Currently working at a trading firm, he is now in love with the Java world and focused on both microservices oriented architectures and reactive applications.