Khononov, Vlad. Learning Domain-Driven Design (English Edition). O'Reilly Media. Kindle 版.

Foreword

1. strategic design: understand the business domain and break it into smaller problems
2. tactical design: make software architecture and implementation from problems created in the above step

Preface

Referring to the Business Logic part in this section reminded me that I also wondered what business logic was in the early years of my career.

"architects. Its strategic design decision tools will help you decompose a large system into components—services, microservices, or subsystems—and design how the components are integrated with one another to form a system. (p.10)"
This kind of design should be done when architecting apps for ODC, too. What puzzles me is if we should recommend OutSystems developers to study and employ DDD. Isn't it too complicated?