-
@LeXavTwit Yes. I wouldn't use DB triggers either At the same time, I saw and did data transformation at app level as well Why should we do groupBy, counts and app level? Each component excels at their own thing. I underutilized DB due to lacking the right testing tooling because of TDDPermalink On twitter.com
Mood +1 🙂
-
@LeXavTwit Mocking everything seemed useless nor provided robustness to the application Good coverage, you start the app, crash Then, you learn about the main DB APIs and do the rest at app logic level Smaller mock (seems right), when you start the app works (seems right). It's slow 😓Permalink On twitter.com
-
@LeXavTwit Because we are using the wrong tool for the problem. I was misusing TDD. And only doing unit testing didn't provide the right speed. I still needed manual tests or very E2E tests. Bad experience.Permalink On twitter.com
-
@LeXavTwit For the last few years, I started to move more responsibility into the DB layer. Leveraging quite powerful features of Postgres for example. Indeed, some areas of the application were IO intensive but not too complex domain-wise. Mocking that part could have been a waste 😓On twitter.com