1. By default when we make a mapping using the relationship function, we use the cascade save-update → when an object is placed into a Session via Session.add(), all the objects associated with it via this relationship() should also be added to that same Session.

  2. Then; when the Application or any other Model is created using the job object, the job listen to catch the update. This does not seem serious but it has other implications.

event.listen(Job, 'after_insert', emit_job_create_event)
event.listen(Job, 'after_update', emit_job_update_event)
event.listen(Job, 'after_delete', emit_job_delete_event)

  1. The job listen enqueue the IndexApploiJob task in integrations-mrq, when MRQ run that task and make a request for the job endpoint.

  1. Imagin the future, if we have 20k of applicants or 100k.

  2. We reindex unnecessary the jobs. [In Elasticsearch not exists the update operation]. Then the document need analyze again.

https://s3-us-west-2.amazonaws.com/secure.notion-static.com/781fb1b5-9344-4e00-b2b8-4c7aefed3f09/Kapture_2021-05-06_at_12.33.49.mp4