Database and Storage

Storage design in Norscode is mostly about clarity, validation and recoverability. Many smaller products do well with simple storage models first, as long as those models are strict enough to validate, back up and migrate later.

Validate before persistence

The cheapest place to stop bad data is before it becomes part of long-term state. Good storage design therefore starts with strong validation, stable field rules and clear expectations for what each record should contain.

funksjon lagre_interesse(navn: tekst, team: tekst, fokus: tekst) -> heltall {
    hvis navn == "" da { returner 0 }
    hvis team == "" da { returner 0 }
    returner 1
}

Backups and migration thinking

Backups are only useful when restore is understood and tested. Migration plans are only useful when the existing data shape is known well enough to translate safely. That is why storage quality is not just about writing data, but also about being able to explain, recover and evolve it.

When to move beyond simple storage

Move from file-oriented patterns to richer database setups when concurrency, filtering, relationships or operational overhead start to dominate the product. The goal is not to chase sophistication early. The goal is to recognise when the original model has become the bottleneck.