|
It is neither 'clearly' nor 'deliberate' or 'obfuscation'. It is possible that you personally simply do not understand all the terms or definitions, that is a different story. If you want to 'queue' things, there are many options, including a number of options hosted by AWS as-a-service. For quite a long time a 'queue' hasn't really been a 'queue'. There is SQS, the simplest of them all. There is MSK, which is Apache Kafka, but managed, so you don't have to deal with it yourself. There is Kinesis Streams and Kinesis Firehose, which is like a many-to-one queue, there is a hosted ActiveMQ, which is more complicated than just a 'simple' queue, and then we have Redis which gets used as a queue by plenty of libraries, and there is a set of services that you can use to 'construct' queues, like EMR, Glue, Airflow, Data Pipeline etc. You can also construct a queue out of generic hosted services by combining S3, EventBridge, Step Functions and Lambdas. So no, it is not totally useless as a name or as an acronym, and to add insult to injury: if you are not in the ecosystem you are probably not even close to the target audience. Just because you don't know something doesn't mean it therefore must be bad. You probably don't know what T&E is in the physical world, that doesn't mean it's a useless acronym or shorthand, it just means it's not for you. (It's Twin & Earth, used in a lot of domestic electrical installations) Most of AWS isn't for random people off of the street to immediately jump in to. Neither is flying jumbojets, surgery, or recombinant DNA engineering. |