> But I can’t help but think in the general case this blog post is advocating for putting business logic inside my data layer. That’s not a bad thing, provided

> But I can’t help but think in the general case this blog post is advocating for putting business logic inside my data layer. That’s not a bad thing, provided the business/domain rules are invariant. > That way when the rules inevitably change, you just have to change your config instead of rework your type system or database relations. This is why it makes sense to do fast-moving projects in, say, TypeScript on NodeJS (or back-in-the-day: PHP) with a denormalized object-store (e.g. JSON blobs in Redis) and lots of E2E tests - while doing legacy-business stuff in, say, .NET and RDBMS. It’s disappointing how often people instead misinterpret the above to stereotype a platform as good or bad (well, PHP probably deserved it…). Right-tool-for-the-right-job and all.