4 ms·

Why not? The In-Reply-To header in emails makes following threads pretty easy and you can fire a web hook to API gateway to kick off a Lambda function when you

by throwaway2016a 10y ago

Why not? The In-Reply-To header in emails makes following threads pretty easy and you can fire a web hook to API gateway to kick off a Lambda function when you reply to a Trello story. You might need a database to map the In-Reply-To header to a Trello story if the customer replies to their own message but DynamoDB on AWS would let you do this for pretty munch free. AWS Lambda is actually absurdly powerful when combined with other AWS products. Think IFTTT only with custom code. I am 100% sure there is nothing this product does that can't be done with Lambda, SES, and AWS API Gateway from a technical standpoint. Granted by the time you are done it would cost enough to pay for over a year of this service. Which is why I didn't say I would write it myself. Even if it takes a weekend the break even is too long. Bit if someone wants to open source it ;)

fiatjaf 10y ago
"I am 100% sure there is nothing this product does that can't be done with Lambda, SES, and AWS API Gateway from a technical standpoint." That's a strange thing to say. How many products are there that cannot be done with Lambda, SES and AWS API Gateway?
- throwaway2016a 10y ago
  Good question. Quite a few... those are very niche products. In fact if I think long on it I am not including the front-end in that 100%. If you want a front-end you'd need a tiny bit of S3 or a server. Lambda is good for stateless APIs and event processing but is not good for anything that requires persistence. SES is an email product so it's usage is niche but it is surprisingly powerful. Example: firing a lambda function when an email bounces or is received. I didn't list a database in there. I'm assuming Trello can be used like a database (and looking at their API it seems it can in this case). So to answer your question: - Any app that requires state - Any app that requires persistent connections - Any app where a unit of work can take more than 6 seconds - Any front-ends [1] - Apps where local cache is needed to provide any sort of reasonable performance - Apps that need a database Cannot be made with just those three tools. [1] It is possible to make a front-end with API gateway and Lambda. API gateway can return different mime types, including HTML. But it would be a huge hack and also not likely cost effective. A static site generated and hosted on S3 with Cloud Front in-front of it is very cost effective but requires the client use javascript. If noscript is a requirement you're stuck with a server.

fiatjaf 10y ago

"I am 100% sure there is nothing this product does that can't be done with Lambda, SES, and AWS API Gateway from a technical standpoint." That's a strange thing to say. How many products are there that cannot be done with Lambda, SES and AWS API Gateway?

throwaway2016a 10y ago
Good question. Quite a few... those are very niche products. In fact if I think long on it I am not including the front-end in that 100%. If you want a front-end you'd need a tiny bit of S3 or a server. Lambda is good for stateless APIs and event processing but is not good for anything that requires persistence. SES is an email product so it's usage is niche but it is surprisingly powerful. Example: firing a lambda function when an email bounces or is received. I didn't list a database in there. I'm assuming Trello can be used like a database (and looking at their API it seems it can in this case). So to answer your question: - Any app that requires state - Any app that requires persistent connections - Any app where a unit of work can take more than 6 seconds - Any front-ends [1] - Apps where local cache is needed to provide any sort of reasonable performance - Apps that need a database Cannot be made with just those three tools. [1] It is possible to make a front-end with API gateway and Lambda. API gateway can return different mime types, including HTML. But it would be a huge hack and also not likely cost effective. A static site generated and hosted on S3 with Cloud Front in-front of it is very cost effective but requires the client use javascript. If noscript is a requirement you're stuck with a server.