Manage queue types across environments

This is just a general question regarding the project's view of how queue types should be managed across (or between) various deployment environments.

I've noticed that some queue abstraction libraries allow producers and consumers to operate against a "well-known" queue by name (or similar) independent of the underlying adapter.

For example, this allows producers and consumers to operate against a simple database table "queue" in a developer or CI environment while using SQS in the fully-deployed scenario.

I'm not sure that is possible or even a good idea, but it is a pattern that seems to exist.

Thoughts? Recommendations?

L’issue non nomina file, test o punti di ingresso; chiede se i tipi di coda debbano essere gestiti in modo coerente tra gli ambienti di deployment. Inizia individuando l’adapter della coda e i punti di ingresso della configurazione dell’ambiente, quindi stabilisci un ambito concreto e i criteri di accettazione prima di apportare modifiche.

Scritto dal modello di indicizzazione a partire dal testo della issue.