-
Notifications
You must be signed in to change notification settings - Fork 153
Closed
Labels
meeting notesTopic requests and notes from meetingsTopic requests and notes from meetingsservices isolationDesign documents in scope of Services Isolation workDesign documents in scope of Services Isolation work
Description
PR #52
Meeting Notes
- @akaplya concern about the durability of the message queue in case of using it as transport for full cache invalidation purpose.
- @melnikovi suggest using Amazon SQS as a message queue
- @kandy proposed don't setup reverse proxy in front of service in private network until such necessity appears. Also, proposed to make service application as fast as possible at first and only then use reverse proxy to decrease the load on service.
- @MaxLesechko propose to use application data cache versioning instead of full cache cleaning
- @viktym proposed to postpone using a reverse proxy in service-to-service communication on the first iteration, application data cache versioning should be described in a separate document, investigate the possibility and pitfalls of using a message queue for managing cache invalidation process
Metadata
Metadata
Assignees
Labels
meeting notesTopic requests and notes from meetingsTopic requests and notes from meetingsservices isolationDesign documents in scope of Services Isolation workDesign documents in scope of Services Isolation work