Today, I want to come with an advice to those of you that have an idea. An idea that could become a project that itself could become your job. My advice is very simple but powerfull : “Start simple and iterate quickly”. To illustrate this idea, let’s say you want to create a new kind of ticketing system. How to start simple ? Do you need an authentication to your system ?…

Yesterday I started working on the networking side of Rustenstore. I made a TCP server that is able to receive messages and send it back to the client. This is totaly not the aim of Rustenstore but it is a working base for networking. Next steps are : Organize the code in modules Refactor the code in components to make it less of a sandbox I don’t think I will have time to do that today but I am hyped !…

As no one knows (because no one gives a fuck), GoDDD is my implementation of Event Sourcing in Golang. I was really anoyed with this implementation. Normaly, a Domain object called on a mutation method should emit an event that is applied on itself after being saved in an event stream. For this to work properly : The event stream should receive an event that have a specific (known) type (let’s say Event); The domain object should be able to received the event name and the event payload to mutate its state; These two requirements are contradictory because the event payload is of a different structure every time.…

Today I was thinking about rustenstore (you don’t know what it is but who cares ? No one is reading this blog) and how to send the eventstreams to the clients. I told myself that using GRPC was a great idea to decrease connect/disconnect rate between the client and the server. However, a way better idea came just after. Why not just use a TCP connection ? After all, my eventstreams a binary file, so lets send their binary content through the TCP connection.…