Current process strings together Twilio, Rock, and Postgres. The dependency on Rock can cause issues with scaling up to handle CLC traffic, and the foreign key relationship between Postgres and Rock can get out of sync (this happened to me during testing but has not happened to attendees as far as i'm aware)
The current authentication method is a JWT containing a Rock cookie. We could change this to be an Auth0 JWT. The postgres DB would foreign key to Auth0's user ID instead of Rock and we'd remove the dependency on WMR rock.
For getting people's info into Rock for follow-up purposes, that could be a post-conference ETL process.
gburgett
commented
1 year ago
Current process strings together Twilio, Rock, and Postgres. The dependency on Rock can cause issues with scaling up to handle CLC traffic, and the foreign key relationship between Postgres and Rock can get out of sync (this happened to me during testing but has not happened to attendees as far as i'm aware)
The current authentication method is a JWT containing a Rock cookie. We could change this to be an Auth0 JWT. The postgres DB would foreign key to Auth0's user ID instead of Rock and we'd remove the dependency on WMR rock.
For getting people's info into Rock for follow-up purposes, that could be a post-conference ETL process.