Can any application currently using a relational database be rewritten to use an Aggregate Data Model, by Focusing on data modelling aspects only (ignoring other features like salability or transaction handling)?

Why / Why not?

  • $\begingroup$ What are your thoughts? What prevents you from being able to answer this on your own? Is there some aspect of either concept that you're unsure about? $\endgroup$ – D.W. Apr 9 at 21:53
  • $\begingroup$ Would you like to define 'Aggregate Data Model'/give a reference? google seems confused whether it means a NoSQL database; or a data warehouse/cube/BI tool. What's it an aggregate of? How could you aggregate something if you don't record the raw/based-on data? $\endgroup$ – AntC Apr 9 at 22:57
  • $\begingroup$ @AntC let's say nosql $\endgroup$ – Irina Crabbs Apr 10 at 9:42
  • $\begingroup$ To repurpose an old gag ... Stackoverflow definition: a means to transfer words from the notes of the instructor to the notes of the student, without passing through the minds of either. $\endgroup$ – AntC Apr 11 at 0:11
  • $\begingroup$ Perhaps you mean a reporting database as opposed to a database optimised for transactional performance? Physical standby/hot standby databases typically are used for that. See here en.wikipedia.org/wiki/Oracle_Database#Database_options at "physical standby ... reporting". All vendors offer something comparable. The data model in the reporting database might be augmented with aggregates (ideally organised as Views, perhaps materialised). $\endgroup$ – AntC Apr 11 at 0:17

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.