Database-Centric Vs Tired Architecture

Consider 3 applications:

1. One is for a fitness club that has a backend database and offers some services on the website,
2. another is an e-commerce site, with heavy dependence on Database,
3. a point of sale application with heavy use of database

I need to choose among tiered architecture and database-centric, as defined in this book. I can't seem to find resources that discuss exact motivations of choosing one over the other, apart from this page, which states:

using stored procedures that run on database servers, as opposed to greater reliance on logic running in middle-tier application servers 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-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.

It seems to me point of sale should follow database-centric, and fitness center application should follow tiered architecture, but I am not sure about the ecommerce. Any pointers are greatly appreciated.

and Database Centric Architecture: