[FEAT]: Add caching

[lnovitz]

Is there an existing request for this feature?

• I have searched the existing issues

Is there a pain point in the app driving this feature request?

Doesn't make sense if we're hitting the database every time a user logs in. We should be caching.

Desired Behavior

When a user logs in, load cached job app data (this should be fast, no processing page needed). If the today's date is different from the last cached date, then we can continue as normal background_tasks.add_task(fetch_emails_to_db, user)

Criteria for Completion

• login endpoint adjusted to load from cache first, check date
• fetch_emails_to_db should be modified to add email_records (batch) to cache for the user along with the current datetime
• create a cache of some sort?!

Anything else?

Since we're using Next.js, might want to consider something from below:

• https://nextjs.org/docs/app/building-your-application/caching
• https://nextjs.org/docs/app/building-your-application/data-fetching/incremental-static-regeneration
• On-demand Revalidation: Revalidate data based on an event (e.g. form submission). On-demand revalidation can use a tag-based or path-based approach to revalidate groups of data at once. This is useful when you want to ensure the latest data is shown as soon as possible (e.g. when content from your headless CMS is updated).
  https://nextjs.org/docs/app/building-your-application/caching#data-cache

Code of Conduct

• I've read the Code of Conduct and understand my responsibilities as a member of the jobba.help Community

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[lnovitz]

We don't want to cache this data because it's potentially sensitive