This is awesome feedback, thanks everyone!
Yeah, I think I realized pretty quickly that some sort of process-per-date wasn’t really going to work out.
Having a process per future event sounds like a pretty good direction though.
Our current older calendar does a daily job that assures all recurrence patterns are run/up-to-date as far out as 2 years. It would be great if this wasn’t a limitation, but I’m not sure how to go about it. Possibly future dates from a recurring event could be auto-generated from a recurrence pattern definition on a per-room level only when checking that room for conflicts? I still have to figure out how to define that recurrence pattern too. 
Is there a way to define a datetime range (i.e. May 3rd, 1pm-3pm) in a single datatype or is just defining a start-datetime and end-datetime the best way to go about that?
I like the idea of each room having its own leader process that knows all of the events it exists in. I’ll have to take a look at Trevoke’s project to try and wrap my brain around it more. 
