You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the things I want us to consider is that the whole SQS-in/SNS-out business has its tentacles all through the invocation part of this application. Ideally, we should be able to invoke it not just by Lambda (which would still be SQS), but also from a CLI by passing it a list of strings (probably on STDIN), without having to run pretend AWS services.
Throughout the whole pipeline, we have big chains of Akka stream stuff that might be better, both for readability and reuse, if we crack them apart and name them, preferably restricting the interface parts (SQS/SNS or STDIO or whatever) to the very periphery.
Part of wellcomecollection/platform#5784
This is the specific task of refactoring the ECS service so that it can operate as an SQS triggered Lambda.
It should be preceded by the RFC described in the linked issue, and followed by an ADR describing the change made.
The text was updated successfully, but these errors were encountered: