Скачать или смотреть When NOT to write an Abstraction Layer

Common advice is to abstract dependencies. Often this is because
people have been burned by depending directly upon 3rd party dependencies that they are highly coupled to. If they need to change the dependency, which they are highly coupled with, it can be pretty painful. This is why people say to abstract any dependency to isolate it so that your application code is coupled to yourself rather than a 3rd party. While this is generally true, it depends, and you don't want to create an abstraction that is more work in short and long run by creating the wrong abstraction. Here's a concrete example of when you shouldn't abstract.

🔗 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  

Should you use the Repository Pattern? With CQRS, Yes and No!
   • Should you use the Repository Pattern? Wit...  

📝 Blog: https://codeopinion.com
👋 Twitter:   / codeopinion  
✨ LinkedIn:   / dcomartin  

#softwarearchitecture #softwaredesign #codeopinion

0:00 Intro
0:42 Abstractions & wrappers
2:09 Messaging Patterns
3:39 Don't Abstract Tools
3:54 Different Implementation of Functionality
4:55 Updating the Abstraction
5:32 Complexity