Скачать или смотреть Does a Data Access Layer make it easier to change your Database?

One primary reason for a data access layer or abstraction is your ability to move underlying databases easier. Have you ever replaced the underlying database of a large system or service? For example, moved from one relational database like PostgreSQL to MySQL. Or perhaps went from a relational database to a document or event store?

There seem to be two groups of people. Those that have will say that abstracting the underlying database is crucial. While the other group never has moved database and question abstracting or creating a data access layer because you likely won't replace the database.

For me, like many things in software architecture, it's about coupling. If you limit coupling this isn't much of a hot topic.

🔗 EventStoreDB
https://eventsto.re/codeopinion

🔔 Subscribe:    / @codeopinion  

💥 Join this channel to get access to source code & demos!
   / @codeopinion  

🔥 Don't have the JOIN button? Support me on Patreon!
  / codeopinion  

📝 Blog: https://codeopinion.com
👋 Twitter:   / codeopinion  
✨ LinkedIn:   / dcomartin  
📧 Weekly Updates: https://mailchi.mp/63c7a0b3ff38/codeo...

0:00 Intro
1:08 Abstraction
3:11 Coupling
4:08 Capabilities

#softwarearchitecture #softwaredesign #codeopinion