How can we store a large amount of information.
My world, I know a person is good.

rproffitt commented: "My world, I understand it alone" +17

Dani AI

Generated

Hi — good question. As suggested, the right way to store "a large amount" of information depends on a few concrete choices: is the data structured records, free-form text, media files, or sensor streams? Will it be updated constantly or mostly written once and read many times? Is access local (on a phone or wearable) or from many users across the internet? Rough size estimates (GB, TB, PB) and privacy needs (personal data, consent) change the approach.

Practical options and tradeoffs you can use as a decision guide: use relational or document stores for records and searchable fields; use object storage for large files (images, audio, video); use key-value or in-memory caches for very low-latency reads; and use embedded mobile databases with background sync for devices and wearables. Plan for partitioning/sharding, compression, tiered hot/cold storage, backups, and monitoring so you can grow without rearchitecting. If you will store personal data, add encryption at rest and in transit, strict access controls, and a clear retention policy.

Next steps: estimate current size and 1-3 year growth, list read/write patterns, and state whether the data must be available offline. Share those details and I (or others) can recommend a concrete architecture, a minimal prototype to try, and what to measure during the test run.

Details would help, like

  1. what type of information
  2. frequency of updates
  3. frequency and type of access
  4. scope of access
  5. how large is "large"
  6. single user, or multi-user

Typically "large" amounts of data are stored in one or more databases such as SQL Server.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.