Command Palette

Search for a command to run...

Back to Meetings

Backend Architecture Discussion

Friday, January 9, 202690 minutes4 participants
Mike ThompsonMike Thompson
Sarah ChenSarah Chen
David KimDavid Kim
John MartinezJohn Martinez

AI Summary

The engineering team met to discuss the proposed microservices migration for the notification system. Currently, all notification logic runs in the main monolith, causing scaling issues during peak usage.

Mike presented three architecture options: 1) Extract to a single notification service, 2) Split into separate services per channel (email, push, in-app), or 3) Use a serverless approach with AWS Lambda.

After extensive discussion, the team decided on Option 1 with a message queue (SQS) for decoupling. This provides the best balance of simplicity and scalability. The serverless option was rejected due to cold start latency concerns for real-time notifications.

David raised concerns about deployment complexity. The team agreed to use the same Kubernetes cluster but with a separate namespace for the new service. David will set up the CI/CD pipeline for the new service.

Timeline estimate: 4 weeks for MVP, with gradual migration of notification types over 2 additional sprints.

Key Points

  • Notification system to be extracted from monolith due to scaling issues
  • Chosen architecture: single notification service + SQS message queue
  • Serverless rejected due to cold start latency for real-time notifications
  • Deployment: same K8s cluster, separate namespace
  • David to set up CI/CD pipeline for new service
  • Timeline: 4 weeks MVP + 2 sprints for full migration

Suggested Tasks3 items

Create notification service repository and boilerplate

Assignee: Mike Thompson

HIGH

Set up CI/CD pipeline for notification service

Assignee: David Kim

HIGH

Document notification service API contracts

Assignee: Sarah Chen

MEDIUM