TruffleMuffin
Joined 11 years ago
Joined 11 years ago
Perfect for a use case I have currently which I built a custom Lambda function to execute.
The one missing piece is that I don't see any way at the moment on how to deal with queue message attributes. I use these to contain critical meta data across messages of different types with with cross cutting information. For example. "A tenant identifier" for a multi-tenant scenario.
That data is lost with a pure subscription as I understand it.
I genuinely want to support local businesses, and I make the effort to buy local from Waterstones whenever possible. But it's not always feasible with the amount I buy. I have many thousands of books, including those on Kindle. I don't have physical space for them otherwise.
Can't start EC2 instances, and failed tasks for multiple production accounts in London.
Anyone else experiencing issues?
Only gripe is no embeddable checkout but its not a huge deal, and they have superior test platform than even Stripe. The test cards are right there in slide in panel, and you have option to select paid/cancel/fail etc to test different outcomes.