SObjectizer Tales – 28. If I had a magic wand...

by Marco Arena

In this episode I delve into what I dislike the most about the library and explore what I would change if I had a magic wand.

SObjectizer Tales – 27. Design ideas

by Marco Arena

In this episode we aim to inspire new ideas and approaches to design applications using SObjectizer and its paradigm.

SObjectizer Tales – 26. Dispatcher selection

by Marco Arena

In this episode we explore guidelines and considerations for binding agents to dispatchers. We'll emphasize the significance of asking pertinent questions rather than expecting definitive answers, as the decision-making process hinges on the unique requirements of the system.

SObjectizer Tales – 25. Runtime telemetry

by Marco Arena

In this episode we learn how to get insights into application performance using SObjectizer's monitoring system.

SObjectizer Tales – 24. Delivering messages at shutdown

by Marco Arena

In this episode we learn a feature of SObjectizer to perform arbitrary actions just before shutdown, including message delivery.

Providing a stable memory address

by Jens Weller

Some APIs allow you to store a pointer to your data element. This is used to access additional information from your types to display them in Model/View Architecture.

A while ago I showed how you can implement a tree with shared_ptr and enable_shared_from_this and then display this in QTreeView. And when working on my current project I knew this problem would come around again. Maybe not for a tree and a tree view, but I'll clearly need to have some way to have ui panels display and edit my data classes and store a stable memory adress as a pointer in Qt models. Back in 2015 the Qt5 example still used a pointer allocated with raw new for this, in Qt6 the example uses unique_ptr. Using shared_ptr for this back in 2015 was a good decision, and the code works very well. For the moment I don't see that my current project would need to make use of enable_shared_from_this, so using unique_ptr would be a good option...

SObjectizer Tales – 23. Mutable messages

by Marco Arena

In this episode we explore mutable messages, a feature enabling us to exchange messages that can be modified by the receiver.

SObjectizer Tales – 22. Performance, part 3

by Marco Arena

In this episode we conclude our exploration of performance considerations within the actor model, with a specific focus on typical benchmarks.

SObjectizer Tales – 21. Performance, part 2

by Marco Arena

In this episode we continue our exploration of performance considerations within the actor model, with a specific focus on measuring service time.

SObjectizer Tales – 20. Performance, part 1

by Marco Arena

In this episode we embark on a three-part full-immersion on performance metrics and considerations in message-passing styled applications, with a specific emphasis on SObjectizer and the in-process actor model.