1. Events and threading are both approaches to handling concurrency but have key differences in how they manage parallel processing and synchronization. 2. With events, each event is handled independently without preemption or explicit synchronization, whereas threads require managing shared states and locks which can cause issues like deadlocks. 3. The document recommends using an event-based approach for cases where fast iteration, easy testing, and avoiding thread-safety issues are priorities, and using threads only where explicit concurrency is needed and there is a performance benefit. It introduces Gearman as an events-based job queue system.

1. Thoughts on Events + A brief intro to a practicable events SDK – Gearman [email_address]

12. Working model Both synchronous and asynchronous (event silent db persistency)