- Главная
- Разное
- Дизайн
- Бизнес и предпринимательство
- Аналитика
- Образование
- Развлечения
- Красота и здоровье
- Финансы
- Государство
- Путешествия
- Спорт
- Недвижимость
- Армия
- Графика
- Культурология
- Еда и кулинария
- Лингвистика
- Английский язык
- Астрономия
- Алгебра
- Биология
- География
- Детские презентации
- Информатика
- История
- Литература
- Маркетинг
- Математика
- Медицина
- Менеджмент
- Музыка
- МХК
- Немецкий язык
- ОБЖ
- Обществознание
- Окружающий мир
- Педагогика
- Русский язык
- Технология
- Физика
- Философия
- Химия
- Шаблоны, картинки для презентаций
- Экология
- Экономика
- Юриспруденция
Data Access Patterns. Three Tier Architecture презентация
Содержание
- 1. Data Access Patterns. Three Tier Architecture
- 2. Three Tier Architecture Presentation Layer (UI classes)
- 3. Three Tier Architecture Presentation Layer (UI classes)
- 4. Three Tier Architecture Presentation Layer (UI classes)
- 5. Facade Шаблон фасад (англ. Facade) —
- 6. Motivation Most software systems require persistent data
- 7. Data Access Layer A better design is
- 8. Program select
- 9. Data Access Layer To avoid problems associated
- 10. Program to an Interface; Not Implementation
- 11. Three Tier Architecture UI Business Logic Persistent Data
Three Tier Architecture Presentation Layer (UI classes) Business Logic Layer (data classes holding business logic) Persistent Data Layer (databases, DBMS, data access classes)
Слайд 2Three Tier Architecture
Presentation Layer (UI classes)
Business Logic Layer (data classes holding
business logic)
Persistent Data Layer (databases, DBMS, data access classes)
Слайд 3Three Tier Architecture
Presentation Layer (UI classes)
Business Logic Layer (data classes holding
business logic)
Persistent Data Layer (databases, DBMS, data access classes)
Слайд 4Three Tier Architecture
Presentation Layer (UI classes)
Business Logic Layer (data classes holding
business logic)
Persistent Data Layer (databases, DBMS, data access classes)
controller
façade
Слайд 5Facade
Шаблон фасад (англ. Facade)
— структурный шаблон проектирования, позволяющий скрыть сложность
системы путём сведения всех возможных внешних вызовов к одному объекту, делегирующему их соответствующим объектам системы.
Слайд 6Motivation
Most software systems require persistent data (i.e. data that persists between
program executions).
In general, distributing low-level data access logic throughout a program is not a good idea (design).
In general, distributing low-level data access logic throughout a program is not a good idea (design).
Program
select * from Items
rs.getString("Name")
Слайд 7Data Access Layer
A better design is one that includes a data
access layer which encapsulates the details of the underlying persistence API.
It abstracts the low-level details of persistent storage.
It provides an interface that is usually a better match for the style of programming used in the domain logic. For example, the data access layer might provide an OO interface onto relational data.
It abstracts the low-level details of persistent storage.
It provides an interface that is usually a better match for the style of programming used in the domain logic. For example, the data access layer might provide an OO interface onto relational data.
Слайд 8
Program
select * from Items
rs.getString("Name")
Program
select * from Items
rs.getString("Name")
customer = dao.find(id)
update(customer)
Слайд 9Data Access Layer
To avoid problems associated with mixing SQL and application
logic, SQL statements and data base design details are often encapsulated in a data access layer
The data access layer presents an interface that is convenient for application programs.
The data access layer presents an interface that is convenient for application programs.
