If I have to have a constantly-running fargate application, doesn't it kind of defeat the purpose of the architecture? That will incur significant cost.
from the 7th of April you can now use lambda with node.js runtime to stream a response (aws.amazon.com/blogs/compute/introducing-aws-lambda-response-streaming/) if you don't care about the streaming capability (that I did in that architecture) you can use a lambda function that buffer the response and returns the final HTML. There are options, but depends what are your architecture characteristics to express.
If I have to have a constantly-running fargate application, doesn't it kind of defeat the purpose of the architecture? That will incur significant cost.
from the 7th of April you can now use lambda with node.js runtime to stream a response (aws.amazon.com/blogs/compute/introducing-aws-lambda-response-streaming/)
if you don't care about the streaming capability (that I did in that architecture) you can use a lambda function that buffer the response and returns the final HTML.
There are options, but depends what are your architecture characteristics to express.