Instead we just write directly to durable queues on RabbitMQ (there are some exceptions where extreme consistency and transactions are needed).
That's is we do web->queue->databases.
There are serious cons to this bus approach as well as pros like improvements in latency.
The bottle approach is nice because you can write old school CRUD style.
Maybe I can use parts of bottle to write to our rabbit bus for the parts that are CRUD because of consistency reasons.
Instead we just write directly to durable queues on RabbitMQ (there are some exceptions where extreme consistency and transactions are needed).
That's is we do web->queue->databases.
There are serious cons to this bus approach as well as pros like improvements in latency.
The bottle approach is nice because you can write old school CRUD style.
Maybe I can use parts of bottle to write to our rabbit bus for the parts that are CRUD because of consistency reasons.