Jobleads Releases Review (248 - 250)
Infrastructure Team
Authentication history migration to user service
Problem: Authentication logs were duplicated. That led to incorrect BI analysis.
Solution: We found the root cause in our SSR and passed the topic to Job Seekers. Additionally, we moved the storing mechanism out of the monolith.
Effect: No duplicates. Stronger decoupling.
Limitation of activation mail sendout
Problem: Our mailing system allowed us to spam our users, as reactivation emails could be sent instantly with just a click. It was leading to user frustration and lowering the scoring of our SMTP server.
Solution: Now we send up to three emails per hour per user.
Effect: Nobody will be spamed by us.
User history service
Problem: We aim to create more personalized communication with users. To achieve this, we must collect multiple events from all services.
Solution: The first version is ready and we are working on deployment.
Effect: Soon.
Batchjob optimization next round
Problem: Acquiring changes was leading to DB problems because batch jobs are fast now.
Solution: Additional changes were applied. Including SKIP LOCKED directive.
Effect: Smoth and fast background processing.
Job exports timeout
Problem: The biggest exports had problems with database disconnection because of the long-running process.
Solution: The job export process was refactored.
Effect: All exports work as expected.
Always fresh jobs for developers and testers
Problem: Job data included in the local / QA environment were getting older. It was problematic in the long run because we were forced to recreate data periodically.
Solution: The import process will change the necessary dates.
Effect: Always fresh jobs. No need to recreate data dump.
Release versioning
Problem: We have an increasing number of independent services that are deployed separately. We need a single location where all deployments will be visible, along with details about the changes made.
Solution: We integrated semantic release into main services.
Effect: Information about all deployments will be visible on Slack #release_notes_jl and in GitLab release page (per project).