Do you do anything to handle packet loss, or operate under the assumption it should be minimal on a LAN?
In the configurations I have implemented, LAN packet loss is rare. Operations are idempotent and thus can be repeated.
Everybody has their preferences. Personally, I avoid having too many layers and too many intervening abstractions. In my designs, keeping it lean maximizes throughput and simplicity means that I can debug it without tearing out too many hairs. In many projects that I have worked on we spent more time debugging third party modules than the stuff that we designed and implemented.
I am curious about the details of how you do it.
Obviously, my designs are for systems that work well with those principles. It is by far not a generalized architecture. I still use MQTT, TCP, WebSockets, IPC, UDS etc where they provide essential and critical capabilities.
My philosophy is simple. Use the simplest, easiest tool that gets the job done without needless complexity or difficulties. If you are having too many problems, then revise the design.
Feels like AI is good at generating that kind of noise.
They lost me at this header. MQTT was quite literally designed for satellite based communication. Its biggest strength is dealing with intermittent connections. If you’re going to fire and forget important data with MQTT you’re already using it wrong.
Apache 2 Should replace Kafka + Flint.
Deploy AI Features at the Edge