Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unique benefits #20

Open
sjmog opened this issue Aug 22, 2014 · 4 comments
Open

Unique benefits #20

sjmog opened this issue Aug 22, 2014 · 4 comments

Comments

@sjmog
Copy link

sjmog commented Aug 22, 2014

Aside from simplifying relational structures for the server, what are the unique benefits of flattening records in this way? Are there any benchmarks?

@supairish
Copy link

I'm curious to this as well. What is your primary use case for this type of feature? Thanks!

@alvinsj
Copy link
Owner

alvinsj commented Aug 24, 2014

I am using this primarily to create extra tables of denormalized records. Then I use them instead to perform SQL query to display some real time reports of the data. Currently I use some background queue to create the records.

@sjmog
Copy link
Author

sjmog commented Aug 25, 2014

What is the benefit over just using SQL queries to grab records and relations?

Do you have any benchmarks for performance comparisons?

@alvinsj
Copy link
Owner

alvinsj commented Aug 25, 2014

@sjmog, I guess it depends on the use case and the context. There are articles discussing about this, e.g. "normalize until it hurts, denormalize until it works". In my case, it reduces the SQL JOIN's query on large number of records and helped on the responsiveness when displaying data report. No benchmark built for this yet, but I guess you can find some related benchmarks on normalized vs. denormalized tables.

Yea, there is no one solution for all problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants