2. eZ provides an events calendar, but it’s very basic
Due to services like Google Calendar, users expect very advanced calendaring
Recurring events is one of those modeling problems that seems easy on the surface,
but is really quite complex.
Presenter: Joe Kepley 2/9/12 SLIDE 1
3. Record per event, separate storage of recurrence rules
Natural extension of single event storage with a rules table
Easy to understand
Easy to query
Requires generation of events via scheduled job
Multiple records per occurrence
Presenter: Joe Kepley 2/9/12 SLIDE 1
4. Single event storage with separate storage for recurring events
Storage is bifurcated
All recurring events have to be checked on each pass
Complex queries
Presenter: Joe Kepley 2/9/12 SLIDE 2
6. Can we make it actually work?
Optimization Assumptions
In most applications, one-time events are the 80-90% case.
Typical event load is in the <10,000/year range.
Data is only queried across a given range. This month or year, not all future points.
Presenter: Joe Kepley 2/9/12 SLIDE 4
8. Needs work!
Translations
Date exceptions within a recurring rule
Time zone bugs/testing
Improvements to data model
http://github.com/blendinteractive/BlendCalendar
Presenter: Joe Kepley 2/9/12 SLIDE 4