ActiveOrient Case Study: Universal Store Facility

In a recent screencast Dave Kimura worked hard to get quick responses from large tables in a sql-database.

Recently I published an introduction of ActiveOrient in dev.to. The latest part covers a setup to build a time-grid based graph-database which offers constant access times to big data tables by design.

Would be interesting to compare the Postgres-based solution with the ActiveOrient-Approach

Details:
https://dev.to/topofocus/activeorient-universal-store-facility-58bi

Conclusion

Database Design matters, even if a flexible multi-model-database is used. This time-grid pattern opens a door to ┬╗sustainable programming┬ź. In contrast to classical RDMS(SQK)-Databases, using a Time-Grid, time-dependent data are stored in an unified environment. Queries are time-invariant. That means: if a database matures, grows and evolves, on can expect constant access times to its heart: the Time-Grid. The possibility of an assignment of any (seriable) ruby object to the time-grid is self evident.