top | item 46014426 (no title) azkalam | 3 months ago - Write side is a Postgres INSERT- Read side is a SELECT on a Postgres view discuss order hn newest zknill|3 months ago I think you might struggle to "scale the read and write sides independently".It's a real stretch to be describing a postgres view as CQRS andersmurphy|3 months ago Sqlite can scale CQRS to 100000 events per second on a relatively small VPS. That's 10x what the author achieves with postgres.You can scale them independently in that you can control the rate at which your views are read and the batch size of your updates.The whole big win wirh CQRS is it allows for very efficient batching. load replies (1) mrkeen|3 months ago I've heard worse, e.g.You use POST for your Cs and GET for your Qs. Tada! anthonylevine|3 months ago Huh?That's EXACTLY what CQRS.I think you might struggle to understand CQRS.
zknill|3 months ago I think you might struggle to "scale the read and write sides independently".It's a real stretch to be describing a postgres view as CQRS andersmurphy|3 months ago Sqlite can scale CQRS to 100000 events per second on a relatively small VPS. That's 10x what the author achieves with postgres.You can scale them independently in that you can control the rate at which your views are read and the batch size of your updates.The whole big win wirh CQRS is it allows for very efficient batching. load replies (1) mrkeen|3 months ago I've heard worse, e.g.You use POST for your Cs and GET for your Qs. Tada! anthonylevine|3 months ago Huh?That's EXACTLY what CQRS.I think you might struggle to understand CQRS.
andersmurphy|3 months ago Sqlite can scale CQRS to 100000 events per second on a relatively small VPS. That's 10x what the author achieves with postgres.You can scale them independently in that you can control the rate at which your views are read and the batch size of your updates.The whole big win wirh CQRS is it allows for very efficient batching. load replies (1)
anthonylevine|3 months ago Huh?That's EXACTLY what CQRS.I think you might struggle to understand CQRS.
zknill|3 months ago
It's a real stretch to be describing a postgres view as CQRS
andersmurphy|3 months ago
You can scale them independently in that you can control the rate at which your views are read and the batch size of your updates.
The whole big win wirh CQRS is it allows for very efficient batching.
mrkeen|3 months ago
You use POST for your Cs and GET for your Qs. Tada!
anthonylevine|3 months ago
That's EXACTLY what CQRS.
I think you might struggle to understand CQRS.