Database-centric architecture: Difference between revisions

Content deleted Content added
MaD70 (talk | contribs)
Reformatted previous link to a paper by Toon Koppelaars about ease of development and maintainability and added link about performance in "Thick Database Approaches" in his video about it
WikiCleanerBot (talk | contribs)
m v2.05b - Bot T20 CW#61 - Fix errors for CW project (Reference before punctuation)
Line 15:
|archive-url = https://web.archive.org/web/20060525094651/http://www.oracle.com/technology/pub/articles/odtug_award.pdf
|archive-date = 2006-05-25
}}</ref> and performance.<ref>{{cite AV media
|people = Toon Koppelaars
|date = 2016-10-31
Line 25:
|publisher = Oracle Learning
|via = Youtube
}}</ref>.
* using a shared database as the basis for communicating between [[Parallel computing|parallel processes]] in [[distributed computing]] applications, as opposed to direct [[inter-process communication]] via [[message passing]] functions and [[message-oriented middleware]]. A potential benefit of database-centric architecture in [[distributed application]]s is that it simplifies the design by utilizing DBMS-provided [[transaction processing]] and [[Index (database)|indexing]] to achieve a high degree of reliability, performance, and capacity.<ref>{{Citation |author=Lind P, Alm M |title=A database-centric virtual chemistry system |journal=J Chem Inf Model |volume=46 |issue=3 |pages=1034–9 |year=2006 |pmid=16711722 |doi=10.1021/ci050360b |postscript=. }}</ref> For example, [[Base One]] describes a database-centric distributed computing architecture for [[Grid computing|grid]] and [[Computer cluster|cluster]] computing, and explains how this design provides enhanced security, fault-tolerance, and [[scalability]].<ref>[http://www.boic.com/dbgrid.htm Database-Centric Grid and Cluster Computing]</ref>
* an overall [[enterprise architecture]] that favors shared data models<ref>{{Cite news|url=http://tdan.com/the-data-centric-revolution/18780|title=The Data Centric Revolution|newspaper=TDAN.com|access-date=2017-01-09}}</ref> over allowing each application to have its own, idiosyncratic data model.