uMicro-Service-Oriented-Architecture
(M-SOA) approach
uDivision
between the database and user interface (UI) portions.
uTwo
key features involved in "thick database thinking":
ŘNothing
in the UI ever directly interacts with a database table. All interaction is accomplished through database views
or APIs.
ŘNearly
all application behavior (including screen navigation) is handled in the database.
uThick database
does not simply mean stuffing everything into the database and hoping for the best.