Application vs. Database: Who Actually Owns Your Data Model?

Let's embark on a thought experiment - you need to create a new application to track the population of rare animals. What would be your first coding move: CREATE TABLE species (...) or class Species? Whichever it is, you'll eventually need to synchronize changes between the database table model and application code.
In this session, we will dive into both the code-first and database-first approaches. We'll explore the pros and cons of each method and discover the tools IntelliJ IDEA offers to satisfy both perspectives.
Speakers: Andrey Belyaev
and Franck Pachot
#IntelliJIDEA #datamodeling #applicationdevelopment #codefirstapproach
Join us:
Website: jb.gg/website
Blog: jb.gg/blog
Twitter: / intellijidea
Facebook: / intellijidea
Download IntelliJ IDEA: jb.gg/download-intellij-idea
Top 15 IntelliJ IDEA shortcuts: jb.gg/Top15IntelliJIDEAShortcuts

[@mobilDB80]

For smaller applications, I think it's legitimate to think primarily from the application perspective. For complex data structures in the relational world of E.F. Codd will benefit from a two-way approach to thinking.

[@DinHamburg]

you usually don't have a choice - you seldom build something on the green field.
Some previous app exist, some database(s) exit - filled with data - and in production.
you change/extend the software - but the data stays forever (in real life - maybe not in student projects)

[@milosristic1111]

I will watch You as soon as possible.Plenty of obligations NOW.

[@karthiksundaram544]

❤

[@rodislav]

Very simple,
The app's API owns the denormalized data, the app owns the app data, the data warehouse owns the normalized data.
The client owns the control over your business.

[@SandroMecca]

I think an egg came first, because the difference between non-chicken and chicken must have happened as a DNA mutation at embryonic or seed stage.

[@gleitonfranco1260]

🔝🧑‍💻☕‼