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.
CDSM is an eLearning company based in South Wales (United Kingdom). Our goal is to help children/adults with learning and training in school and coporate settings.
We have a varied customer base, ranging from small businesses to nation states.
We are looking for experienced/talented developers to join our team.
We run our environments via AWS. Our tech setup is React/Typescript front end, and a NET Core backend. MongoDB + Elasticsearch + Redshift for storage.
Its also coming up to exam season and summer holidays in a lot of places. Seeing the same with my product. We run it internationally so there is a spectrum (country dependant) about usage changes. Some are the same, or less, some are 2-3x more but only certain days of the week. One was 1000x more, but only for one week and is now just normal. It's been pretty crazy.
Regarding your last point. You weigh buying software over building it when you know how much it costs to buy and maintain, and have a strong grasp on how much time money and energy it costs to build it yourself. That is how you make an informed judgement. Sure there is risk, but if your burning 15K a year on a build server and you can build it yourself for 5k and run it for 1k a year then math doesn't lie about what choice you should make.
Agree, and I work in the latest 'social media platform' type end. We have many customers. I can assure the author of the post, when those customers pay for enterprise licensing and their system is broken with an obvious bug. The 'we didn't do any testing before hand because staging is a lie' doesn't actually fair well as a valid excuse for anything. In fact, you just look like an unprepared and immature muppet.
I have had to personally re-document setting up a basic Azure AD connection 4 times in a 18 month period. Each time I go back to it, the UI has changed and key pieces of functionality are just 'elsewhere'.
The EC2 console is old and outdated, its been the same since I started with it like 7 years ago. They are rolling out a new dashboard right now, a complete overhaul.
The difference - I don't have to re-document the EC2 Console for internal training.
The AWS Cli is a simple tool that just keeps working and its documentation is pretty much all you need to look at.
The Powershell interface with AzureAD was absolutely opaque, no documentation, took hours to figure out how to configure claims and when I did, it didn't even work due to hidden limitations that the paid for support could not explain.
I think that your experiences have been quite different to others, certainly mine.
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.