Andrija PetrovicNov 25, 2024

The initial #devcontainers setup I had to see running smoothly was just for test.
However, the test was not trivial.
I built (actually, my son did 😉 😆 ) a fine little lib based on #rust #lapin that allows for publishing/consuming Remote Method Invocation (RMI) structs (#json-ized)
The #devcontainers setup has 3 nodes: producer, processor and consumer.
- Producer publishes a RMI request via #rabbitmq
- Processor processes the request and publishes the RMI result on the result channel
- Consumer consumes the RMI result

And this works.
Now is the time for a more serious setup: #svelte frontend (my younger son built it 😎 ) that will publish identity-related RMIs (register, login, etc) to #rabbitmq and a #rust based Identity processor that will allow for the basic functionality of the #svelte frontend

Show threadAndrija PetrovicNov 25, 2024
Talking about a #rust based identity processor, the whole job is actually easy to find:
Spawn a new #rust #loco project with
loco new <whatever_project_name>
and in the models directory you will find a very elaborate implementation of an identity processor
Show threadAndrija Petrovic
This turned out into an interesting journey, I learned a lot about #seaorm by reading what #loco did with it, how they enhanced it. My current #rust implementation remains purely #seaorm based, but #loco has a lot to offer. Using just the #seaorm layer #loco built seems attractive.
Dec 5, 2024 at 9:50pmWeb