Your point that DB Procedures as a separation of logic being a reasonable choice I think boils down as much to your criteria of a reasonable choice. Good design

Your point that DB Procedures as a separation of logic being a reasonable choice I think boils down as much to your criteria of a reasonable choice. Good design is about understanding your priorities and how they affect the outcome. For example, if I prioritize tests and testability higher than just shipping code, then I will very like care a lot about where my logic lives and if I can test it. If I just care about shipping code, where my logic lives and how I test it is less important than a working product. Well informed tradeoffs are often reasonable choices.