Could you elaborate a bit more on the challenges you faced with backward compatibility during the migration to Clerk? It would be interesting to see a deeper dive into how this affected the deployment process. Great insights overall!
The biggest challenge was related to latency. While components are excellent (and we're huge believers in them), API-over-HTTP frequently means greater latency. As we're all likely painfully aware, unplanned or unpredictable latency can have some pretty large ramifications. This bit us a bit and required some logic changes across our app.
Next, we encountered operational challenges due to the fact that our database was no longer the source of truth for users. We keep a local cached copy, but it's just that--only a cache.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Could you elaborate a bit more on the challenges you faced with backward compatibility during the migration to Clerk? It would be interesting to see a deeper dive into how this affected the deployment process. Great insights overall!
Hey Sawyer--
The biggest challenge was related to latency. While components are excellent (and we're huge believers in them), API-over-HTTP frequently means greater latency. As we're all likely painfully aware, unplanned or unpredictable latency can have some pretty large ramifications. This bit us a bit and required some logic changes across our app.
Next, we encountered operational challenges due to the fact that our database was no longer the source of truth for users. We keep a local cached copy, but it's just that--only a cache.