Table of Contents What is design, what is architecture ? (application, IS) Can you end with CA doing emerging design ? Could you do CA in procedural ? Is DI imporant when in dynamic typing ? Why decoupling database from application (eg, ORM does not map to object but DS) How does OO handle relationships ? Is batch processing good (sometimes) ? What can I do with that ? Why did OO failed ?

Source: https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html Entities encapsulate Enterprise wide business rules. An entity can be an object with methods, or it can be a set of data structures and functions.

Source: https://blog.cleancoder.com/uncle-bob/2019/06/16/ObjectsAndDataStructures.html That’s a lot of recompiling. And a lot of redeploying.

Source: https://blog.cleancoder.com/uncle-bob/2019/06/16/ObjectsAndDataStructures.html Think of it this way. The database schema is not tuned for just one application; it must serve the entire enterprise. So the structure of that data is a compromise between many different applications.

If you handle relationships with pointers (header has a list of details), then you'll load huge amounts of data. Even if using lazy loading, when you search for data is a huge collection, how will you end up ?

Classes and Data Structures are opposites in at least three different ways. Classes make functions visible while keeping data implied. Data structures make data visible while keeping functions implied. Classes make it easy to add types but hard to add functions. Data structures make it easy to add functions but hard to add types.