Anatomy of a Distributed System in PHP

Question

I\'ve a problem which is giving me some hard time trying to figure it out the ideal solution and, to better explain it, I\'m going to expose my scenario here.

Answer 1

I would avoid sqlite for this sort of task, although it is a very wonderful database for small apps, it does not handle concurrency very well, it has only one locking strategey which is to lock the entire database and keep it locked until a sinlge transaction is complete.

Consider Postgres which has industrial strength concurrency and lock management and can handle multiple simultanious transactions very nicely.

Also this sounds like a job for queuing! If you were in hte Java world I would recommend a JMS based archictecture for your solution. There is a 'dropr' project to do something similar in php but its all fairly new so it might not be suitable for your project.

Whichever technoligy you use you should go for a "free market" solution where the worker threads consume available "jobs" as fast as they can, rather than a "command economy" where a central process allocates tasks to choosen workers.