21–30 of 93 posts
VPC: Amazon Virtual Colocated Rack What in the world? Why would I want a rack in the world of a cloud. I want a virtualized private cloud, which not so oddly is named Virtual Private Cloud. I feel like the person who wrote this got into web dev back when I started in the 90s, then never left the time frame. This dude, much like this webpage, clearly have not kept up with the times
VPC: Amazon Virtual Colocated Rack What in the world? Why would I want a rack in the world of a cloud. I want a virtualized private cloud, which not so oddly is named Virtual Private Cloud. I feel like the person who wrote this got into web dev back when I started in the 90s, then never left the time frame. This dude, much like this webpage, clearly have not kept up with the times
Earlier quoted context omitted.
I mean, what would you call it? It's basically a 'push/pop' interface with timeouts. Like, do you think 'Kafka' is more descriptive? Or Prometheus? Or any of the essentially randomly generated names that various projects and products choose? By the standard of tech names SQS seems, relatively speaking, extremely descriptive.
Amazon Queue Service. Or pubsub.
What's in a name? Really, is "Amazon Virtual Servers" much better than "Elastic Compute" ? Maybe slightly. But at the end of the day you have to go look at it and see wtf that means no matter what, and the 'elastic' verbiage is fairly consistent across AWS products. IAM is similarly not that bad - Identity Access Management pretty much tells me what it is. When we have a field where things are named in extremely uncl…
If I want something to provision infra I could go for Chef, Puppey, Ansible, Terraform. Or is it better for me to write my Infrastructure as Code setup using Whitespace Significant Serialization Format?
What's in a name? Really, is "Amazon Virtual Servers" much better than "Elastic Compute" ? Maybe slightly. But at the end of the day you have to go look at it and see wtf that means no matter what, and the 'elastic' verbiage is fairly consistent across AWS products. IAM is similarly not that bad - Identity Access Management pretty much tells me what it is. When we have a field where things are named in extremely uncl…
with "Virtual Servers", I would have only had to look it up once. With "Elastic Computer" it took me months of rereading what that service was for it to sink in.
Some of these are clearly deliberate obfuscation. I need something to handle Queues, what should I use? Amazon SQS obviously. Oh cool, what’s that? It’s a Queue service! Oh great, why is called SQS? Simple Queue Service duh! Is there a more complex queuing service? No. There’s only SQS. The acronym is totally useless, tells you nothing beyond it being for Queues and completely obfuscates what’s happening for anyone n…
not as complete, but see also https://gist.github.com/miglen/f6eef81803a43dad434d for AWS and GCP side by side in plain english
not as complete, but see also https://gist.github.com/miglen/f6eef81803a43dad434d for AWS and GCP side by side in plain english
Thanks for the share. I actually find your link more useful than what the OP offers. If anyone finds the same with azure also, I'm interested.