Taskflow Driver

Creation, Updates, and Deletion against a CDN provider tends to increase latency. Also, issues on the provider side can negatively affect Poppy performance.

Working with a DNS provider for CNAME records also face rate limit challenges.

To help with these issues, it makes sense for the Poppy API to accept a request and post a message to a queue. Workers can then read messages off the queue and provision the request at the CDN provider, thus making the processing of the request truly asynchronous.

The tasks should use either Taskflow, and be powered by a RabbitMQ backend. The backend should be pluggable however.

This will also convert the architecture to be similar to Openstack Designate, and will go a long way in helping performance and scalability of Poppy.