For me back end and front end being conflated is a good thing. Because most of the time it ends up one application anyway. If you need generic API you can make

For me back end and front end being conflated is a good thing. Because most of the time it ends up one application anyway. If you need generic API you can make separate application that will be API. So if you make domain driven design your front end is separate concern. API for third parties is separate concern. Still in database you might have stuff not used by external parties but then you don’t expose it in your external API. But you can make models on your front end API. Making “generic” solution might seem like saving time and money but as times go by and it turns out you have to fight with generic API to get things done because one is stuck in his ways - it definitely pays off.