This is interesting. I've just started having video meetings with a colleague (not Japanese) who aggressively interjects these words when I'm speaking, to the point that I find it distracting. I'm simply not accustomed to having someone say "mmm hmm" several times during a single sentence, and I find I start to lose my train of thought.
We're opposites. I completely lose track of my thoughts and my mind starts to wonder if I don't interject or use small affirmations throughout a conversation. Half the time I interrupt people is because I literally won't remember 30 seconds later what my thought was because there will be a avalanche of other thoughts during that time. I feel like a conversation that is not collaborative is not a conversation.
Unless you're telling a long story in which I generally will try not to interrupt, but one has their limit to being spoken at.
While you _can_ tack all of those things on to your API, many people (myself included) prefer to separate those concerns. A dedicated API Gateway can prevent a lot of additional load from hitting the backend services. A gateway can also be a nice abstraction of the public interface from the underlying service(s).
It's worth noting that AWS's free tier has absolutely no safety net and you can easily end up with an unexpected bill, sometimes a very large one. The single best thing AWS could do to encourage people to learn about its services by trying them out would be to have a safe-by-default billing configuration. A user should have to flip a switch in their account to allow any usage over a given dollar amount, with services being halted in the event they would breach this limit without having flipped that switch.
You would be surprised how many users don't want that. Take e.g. a startup run by two people in Singapore that gets featured on HN unbeknownst to the founders as they are asleep. They experiences a ton of traffic, which makes them exceed the free tier limits. If you were one of these founders, what reality would you want to wake up to? That your web app was hugged to death and you lost out on a significant growth momentum or that your web app stayed up and now you have to pay a bill to AWS (but hopefully have made some revenue, too)?
I'd also say that in the year of our lord 2022 literally everyone has heard about unexpected cloud bills (yes, happens with GCP and Azure all the time as well) and hence should know that they have to set their account up properly - there is a ton of tutorials by AWS and others on how to set up your budgets and billing alerts.
> I'd also say that in the year of our lord 2022 literally everyone has heard about unexpected cloud bills (yes, happens with GCP and Azure all the time as well) and hence should know that they have to set their account up properly - there is a ton of tutorials by AWS and others on how to set up your budgets and billing alerts.
> Technical Product Management @ AWS
Thank you for your reply. However, I must respectfully disagree. Even in your hypothetical startup example, we should default to do not charge people until they flip a switch saying they are in production. I know it doesn't matter to you right now because AWS has so much demand but I think in terms of developer experience (DX), it would be really nice if we could rely on some kind of a sandbox. Even Microsoft Azure has Visual Studio subscription, which has a cap. Please consider adding this option.
There are some expensive car seats designed to cram all three kids into a back seat, but buying a larger car instead is cheaper. They also tend to be designed for triplets, if all three kids are different sizes it becomes a lot more complicated.
Most cars only have attachments for two car seats in the rear, so even if you did have space the middle seat would have to use the generally discouraged seat belt install instead.
This whole time I've been seeing intermittent timeouts when checking a UDP service via NLB; I've been wondering if it's general networking trouble or something specifically with the NLB. EC2 hosts are all fine, as far as I can tell.
Don't forget to request your credit per their SLA[0]. You have 10 days to request your credit, which by my calculations should be 10% of this months' charge. Not a fair trade for leaving us dead in the water, but SLAs in general are worthless.
