February 2009
Intermediate to advanced
718 pages
22h 43m
English
book
Design – Build – Run: Applied Practices and Principles for Production-Ready Software Development
by Dave Ingram
Content preview from Design – Build – Run: Applied Practices and Principles for Production-Ready Software Development
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
14.5. The Logical Data Model and Data Access
Most applications use a database or some type of data store. Maybe one day you will not need to continue to send information to a database or data store, and everything will be held in memory. In the meantime, there is a need to store the data somewhere, and the database is generally the place for it. In physical terms, this architectural layer contains the actual tables, views, and stored procedures, along with any other database-specific elements, such as triggers, functions, configuration files, and security settings that belong to the physical database or databases.
Figure 14-16 shows the sample logical data model.
Figure 14.16. Figure 14-16
I've chosen not to use a prefix or naming convention for the logical data model. This can be applied later, if necessary. The logical data model contains the main Account table and associated tables. At this point it would be a very good idea to compare the logical data model against the requirements outlined in Chapter 13 to ensure that everything has been captured appropriately. While this may seem long-winded, it really does help to ensure that all the requirements have been captured appropriately and corrected where necessary. For the purposes of space and time in the book, we'll not go over all the requirements again. If we were to have done this throughout the chapter then this would ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.