And the part where he says people with this mutation are more prone to bacterial infections is not worrying, because…?
In a world of more and more antibiotic resistant bacteria, that does not seem like a good trade-off…
One of the effects of ISG15 deficiency is a disease called "Type I interferonopathy".
Among the symptoms of this disease includes things like necrotic lesions and severe multi-systemic damages.
From what I gather the fact that these people are not more susceptible to viral infections was a surprise. Which probably relates to why the doctors in the parent article were investigating its possible anti-viral properties.
This is researched as a potential treatment to an acute viral infection. For the duration of the treatment, you can accept the increased risk of bacterial infections.
Just like you accept the risk of increased yeast infections while treating bacterial infections with antibiotics, or the risk of any infection while treating a cancer with chemotherapy.
Probably the issue is microphages being wiped out which allows bacteria to thrive. But you wouldn't take this _all the time_, only when you had a specific viral infection to get rid of.
This "solution" essentially hides away long polling of the queue behind the scenes and triggers the Lambda when message shows up - and scales the poll sizes as number of messages increase and decrease.
It's what you had to previously do yourself with, for example, another Lambda, but handled by AWS and hidden from you. It's not a real event-driven model, like for example triggering Lambda by SNS.
The biggest thing to notice: because your queue gets polled behind the scenes, you will still be charged for the polling requests! Even if your queue is empty most of the time, you will pay for the requests that "check" for new messages.
In other words: by simply creating a Lambda and adding SQS queue as a trigger to it, you're adding a minimal spend to your AWS bill, that it will generate whether you're using it or not.
And because the polling is hidden from you and happens "automagically", you don't have control over how often it happens and how big the polling is, so you don't have control over the bill it will generate.
I can't say on Google certs, but I passed the AWS ones - I wouldn't go for developer and sys ops both - they are the same level certs in the same certification path, so it seems like a waste of money to get them both really :)
Quick note, it's "solutions architect" not "system architect".
AWS certs are very focused on AWS products, so may not be helpful for Google Cloud. The developer/sysops -> devops path may be a bit better of the two, as it focuses on how to get stuff done, while solutions architect is a bit more higher level knowledge of putting AWS products together.
I was skimming the sys ops course and it seams to have some stuff missing from what I've learned so far that I could really use - log files, alerts, analytics, monitoring, etc... While I appreciate the whole serverless idea and let Lamda and such do the heavy lifting, the programmer side of me says meh... I'll just do it myself.
If both aren't needed, I'll probably do sys ops next then.
"Their ad blocker blocker and paywall works, preventing me from reading articles."
Well, Adblocker in Chrome seems to be blocking the ads on the page quite well. Some single requests are being logged after the page loads, but nothing as to what the article mentions.
Now I'm kicking myself because I did something very similar for one of my clients based on AWS and shared it publicly (https://github.com/pbudzon/aws-image-gateway)! Not sure how it compares cost-wise, though. It's a combination of CloudFront, API Gateway, Lambda and S3. I'm quite sure CloudFront doesn't have limitations on what you can cache, like Cloudflare seems to have.
Like others who commented, I don't get the idea of image-resize-as-a-service, so I remember I laughed at my client when they asked me for this. For some reason I believe it's better for the world if we don't make people think it's ok to throw around gigantic images around the cables when it's completely unnecessary...
Not your fault. Developers tend to sometimes underestimate the power of releasing a command line utility as a web based/API tool that can help non techies do simple stuff. Image resizing is a recurring candidate but there are others like conversion tools (to pdf), checkers/monitors (ssl for example) etc. Yes, you could do these on your server with a simple cmd line but tons of folks are willing to pay to be able to use a browser/API to do the same.
It feels like a compelling property here is to have a "single point of continuously increasing quality"—that is, one changing chunk of code that is continuously improved and battle tested as more and more users report issues that require workarounds.
(But of course ever-changing externally hosted web services like these have their drawbacks.)
