Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • "your frontend should neither know or care about the design you chose for your database layer" - uh, the frontend, API and database schema all share the application data model. They all need to know about player entities, tournament entities and the results relationship. Sure the implementation details of the database (concrete schema, with things like naming conventions, indices, surrogate keys, denormalisation) should not leak into the API or even frontend, but they're all informed by the overall data model design. Commented Nov 29, 2024 at 2:46
  • 3
    @Bergi What you call "application data model" is usually called "domain model" today, to distinguish it from a data model as in "how you store the objects." So yes, the frontend definitly knows the domain model, which I think I stated in my answer, but not the data model. Or if there even is anything worth calling a "data model" - maybe it's just a bunch of keys in a redis cluster or serialized objects on S3. Commented Nov 29, 2024 at 5:57
  • I feel the OP's concern, I know that having a design that is too flexible is bad, but having it too rigid is also bad, hence the anxiety of, " I should do this, but if I do this then it would xxx , what should I do then? " . Commented Nov 29, 2024 at 8:00