Define Your System Objects
Your first step is to identify the layers into which your application can be divided. Good examples of these objects are client, server, and database. You want to be careful not to define lower-level objects. Of course, your definition of lower level will vary wildly in a client-server application as opposed to an API-based database library.
Be sure that each system object you define can stand alone. If you can create an object with clean lines of separation from other parts of the system, then it can be a system object. We’ll look at an example in a moment.
By keeping these objects as large as you can, your teams will be able to work independently for longer stretches of time. Defining every single object in ...
Get Ship it! now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
