Content deleted Content added
Mindmatrix (talk | contribs) |
No edit summary |
||
Line 7:
* using [[stored procedure]]s that run on [[database server]]s, as opposed to greater reliance on logic running in middle-tier [[application server]]s in a [[multi-tier architecture]]. The extent to which [[business logic]] should be placed at the back-end versus another tier is a subject of ongoing debate. For example, Toon Koppelaars presents a detailed analysis of alternative [[Oracle Database | Oracle-based]] architectures that vary in the placement of business logic, concluding that a database-centric approach has practical advantages from the standpoint of ease of development and maintainability.<ref>[http://web.inter.nl.net/users/T.Koppelaars/J2EE_DB_CENTRIC.doc A database-centric approach to J2EE application development]</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. 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>ss
| |||