3 ms·
I strongly approve. That's how I implemented the backend of my medical records exchange stack. File system based queues. Point-to-point data interchange, so no
by specialist 12y ago
I strongly approve. That's how I implemented the backend of my medical records exchange stack.
File system based queues. Point-to-point data interchange, so no concurrency; your notion of imprinted work tasks with PIDs is a good idea.
I used a "pull" model. A thread would take work from one directory and drop into another. Poor man's workflow. Worked great. Super easy to monitor and troubleshoot.
Using Java, implementing the cross platform file locking (so a downstream process wouldn't pull a task before it was ready) took some finesse, a small caveat.