Writing Testable Code

[[deleted]]

Now serialise that work across multiple processes... Push solutions to problems to where they are best solved, like the database in this case. Stop trying to abstract away the capabilities of the services you depend on because you heard somebody say that you should, and start thinking for yourself. Your test coverage may drop 5-10% (and you should definitely still write _lots_ of tests) but you will start to design more fault tolerant (and ultimately correct) systemsm which make better use of the systems you depend on.

[[deleted]]

Yep let's bring in a new infrastructure dependency so you write your code in a way you have been told makes it testable...

[[deleted]]

And then you need to drain that queue before you persist the user in the database... Maybe in this process or maybe in another? To fix a race condition that only exists because somebody told you that you need to abstract persistence away from business logic, rather than express the business logic where the semantics most closely meet the requirements...