Many years ago, the database was used as the logical core of an application. It was essentially the domain model as well as all the business logic constraints. Front ends were usually designed to be prettier interfaces to database tables - the grid with action buttons at the end. It was common to design the database first before doing any of the code or prototyping.

Advances in UI/UX principles, software architecture, and available technologies have moved application development away from this paradigm and toward one that uses the database as cold persistence storage. Apps are now designed with the work the user must complete as the main focal point without regard to how this data will end up in storage.

This also has big ramifications for how agile and cross-functional teams develop software as we embrace technologies and patterns that are even more loosely coupled and free us to develop each piece to do what it does best.

What you'll learn:
- How did we get here? The transition from a database-centered business world to a function-centered business world
- How does this work? Designing software from the standpoint of the work rather than the storage
- How can this happen? Architectures like CQRS, actor models, functional programming, and microservices as well as technology choices like caches and NoSql models enabling agile, incremental software development that is user-focused