# Design Draft: Fast billing

**URL:** <https://forum.storj.io/t/design-draft-fast-billing/4796>\
**Category:** design draft\
**Created:** [February 20, 2020, 1:27pm UTC](https://forum.storj.io/t/design-draft-fast-billing/4796 "2020-02-20T13:27:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![littleskunk](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/littleskunk/32/63_2.png) [@littleskunk](https://forum.storj.io/u/littleskunk)\
**Post date:** [February 20, 2020, 1:27pm UTC](https://forum.storj.io/t/design-draft-fast-billing/4796/1 "2020-02-20T13:27:20Z")

</div>

[https://review.dev.storj.io/c/storj/storj/+/901/10/docs/blueprints/fast-billing-changes.md](https://review.dev.storj.io/c/storj/storj/+/901/10/docs/blueprints/fast-billing-changes.md)

---

<div class="post-metadata">

**Author:** ![Dime](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/dime/32/1131_2.png) [@Dime](https://forum.storj.io/u/Dime)\
**Post date:** [February 20, 2020, 5:10pm UTC](https://forum.storj.io/t/design-draft-fast-billing/4796/2 "2020-02-20T17:10:07Z")

</div>

Hi guys! It is interesting to read design draft, nevertheless I have very few knowledge about what is going on under the cover (in current code base), so please sorry in advance.  
As we all know - it is not a good practice to organize queues on databases - messing with reads, writes and locks is dramatically reduces performance, so it is a best practice to make queues on something like RabbitMQ or similar staff. Why don’t you use queues for such data-flow?

Also re cockroach db - it has high latencies (for ex. in comparison with proven Postgres) which seems pretty critical for read-write networking tasks… BTW Postgres supports sharding, HA clustering etc.

---

<div class="post-metadata">

**Author:** ![BrightSilence](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/brightsilence/32/6048_2.png) [@BrightSilence](https://forum.storj.io/u/BrightSilence)\
**Post date:** [February 22, 2020, 10:09am UTC](https://forum.storj.io/t/design-draft-fast-billing/4796/3 "2020-02-22T10:09:17Z")

</div>

Sorry for the later than usual response on my end. I’ve caught a bad case of the flu over the past week and still recovering and catching up. I’m happy to see this one as it intents to fix an issue of confusion I have “complained” about in the past. From what I can tell it’s a fitting solution, though I agree that if performance becomes an issue, queuing is better done outside the database.

More surprisingly the benefits do not list perhaps the most important benefit, no more 7-8 days delays payout and bandwidth usage display. Either way, looks good and looking forward to seeing it implemented.