I worked on an embedded system in the logistics industry where one process drove rendering on screen, and two other processes did a lot of the backend work and

I worked on an embedded system in the logistics industry where one process drove rendering on screen, and two other processes did a lot of the backend work and implemented lots of business logic. They communicated over IPC. This was design this way on purpose, because the back end processes were existing applications. Rather than re writing them entirely, the developers added IPC communication. Also, they believed it was better for a separate process to crash and just restart rather than showing it to the user and confusing them (the person delivering products to a grocery store). The whole thing was a convoluted mess. My advice to you is start simple. You don’t need multiple processes unless there’s a damn good reason. Everything should be a single process.