Geek Answers Handbook

Redshift as a web application?

I am creating an application (using Django ORM) that will swallow many events, say 50 / s (1-2 kbit / s). Initially, some “real-time processing” and monitoring of coverage events, so I will use redis so that some of this data makes decisions, crowding them out when it makes sense. I was going to save all entities, including events in Postgres for the "idle" storage.

In the future I will need an “analytical” opportunity for dashboards and other functions. I want to use Amazon Redshift for this. I thought I would just go over to Redshift and skip Postgres. But I also see that people say that this should play a more passive role. Perhaps I could regularly store the data window in the backend and SQL archive in Redshift.

My question is:

Is it possible to use something like Redshift as a backend for web applications, or does it usually play the role of a passive role? If not, is it realistic to think that I can scale Postgres enough so that these events start only with this? Also, if this is not the case, does the "data and archive window" method make sense?

EDIT Here are some things I saw before writing a post:

+4
source share
1 answer

Redshift (ParAccel) is an OLAP-optimized database based on the plug of a very old version of PostgreSQL.

This is good for parallel readings, which most often request a lot of data. This is bad in many small transactions, especially in the small write transactions that occur with typical OLTP workloads.

. , Redshift .

- , 50 + TPS, Redshift. . , , . Redshift .

, , , Redshift :

  • OLAP . OLTP, , .

  • ORM OLAP . ORM OLTP- , n + 1 SELECT / , .. OLAP- .

  • Redshift PostgreSQL . , PostgreSQL, .

ORM - SQLite PostgreSQL - , INSERT PostgreSQL COPY . ETL , .

, , . .

+3

More articles:


All Articles