Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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



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.


But only one server can access each SQLite at a time?


I've heard worse, e.g.

You use POST for your Cs and GET for your Qs. Tada!


Huh?

That's EXACTLY what CQRS.

I think you might struggle to understand CQRS.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: