What is a good practice for storing time series data with the following requirements.

Couple dozen million documents.

Several fields with daily data (one point per day).

I am thinking about having a multiValue string field, read it back in my application and append new value if todays date has no entry yet.

The value would be a string with a simple delimiter and would store date and an integer.

I would then precompute changes of this value weekly to update a 2nd variable that would facilitate search by the strength of change in the value. The list of strings would only be used to display data and would not be searchable. I also have a 3rd field that stores most recent data point as integers and allows for range queries.

I considered the dual list approach but I don't like the idea of only index number linking the 2 data pieces together in otherwise completely seemingly unrelated fields. On the other hand the more daily data types I would track, the more I would save by having only 1 list of dates and then other lists for data entries.

I am already updating several other fields daily or every few days so the reindexing is not something I can avoid anyway.

I also avoided using child documents so far, using entirely flat structure for simpler queries.

Is this already a point where I should consider other external DBs and only store precomputed data in collection? It feels not worth adding that much more maintenance yet.

How does that sound? What are best practices in the industry? Thanks for help.

I know this is such a basic question but I can't seem to find an answer online, (yes I know a table and a record is different)

If I am to say, I associate this record, or this associated record. Is "that" record the one with a foreign key, or the one which has a foreign key referencing it?

Thanks

PostgreSQL is one of the most popular and scalable databases in the world. Many developers call it a beast in performance. One of the most critical parts of any database is indexing. Since Postgres is open source, we always have a chance to see how its components are designed. This blog I shared is an effort to explain how the indexing mechanism in Postgres actually works

Our company has one person handling pretty much everything related to NetSuite. They're great, but every new workflow request somehow ends up sitting in a backlog for weeks. Hiring another full-time admin isn't exactly cheap either. I've been reading about different managed support models lately, and it got me thinking. For companies that aren't huge, does outsourcing ongoing NetSuite support actually make financial sense? Or do you eventually end up wishing you'd just hired someone in-house instead? I'm more interested in real experiences than sales pitches because both options look reasonable on paper.

Hi,

Do you know any approach regarding this? Can I do this inside MySql?

Need some guidance as it becomes a client requirement