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?