Love for Mollie - and literally had this exact theme last year at work. Stripe implemented, then customer A couldn't use it due to US base, so went to Adyen, built integration, rejected as less than $5 million as first responder said, then went to Mollie.
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.
Weird example, do people actually use multiple consumers doing different things to a single message? You just queue multiple messages with different properties and consumers process things the same way.
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 work in this area and the answer to some of your questions are really already available. Rubrics/CASE/CLR/Learning Outcomes etc are known within the teaching community. Their implementation in the digital space is where you are seeing the gap. A traditional classroom environment doesn't always translate into a digital one for the reasons you specify, but thats not the only way to do it.
Depends on the book. I read a lot, and if I am trying a new author out or a book I am not sure of, a hardback at £20 is a bit of a risk compared to kindle 99p perhaps.
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.
I have an ELB API operations issue on my dashboard, the two together means new tasks can't get healthy. So we lost tasks in the failed AZ and new ones in a healthy AZ can't receive traffic.
Yeah same here, and I'm also seeing troubles querying my Redshift cluster -- I'm guessing it is a more widespread issue, potentially with the datacentre itself (eu-west-2a).
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.
reply