SWE4004 S3 Database Architectures

Get Started. It's Free
or sign up with your email address
Rocket clouds
SWE4004 S3 Database Architectures by Mind Map: SWE4004 S3 Database Architectures

1. platform as a Service (PaaS)

1.1. Allows creation of web applications without buying/maintaining the software and underlying infrastructure. Provider manages the infrastructure including network, servers, OS and storage, while customer controls deployment of applications and possibly configuration.

2. Large scale prototyping/load testing: Providers have the resources to enable this.

3. Faster development: Provider’s platforms can provide many of the core services to accelerate development cycle.

4. The meaning of service-oriented architecture (SOA).

5. File-Server Architecture

6. Service models

6.1. Software as a Service (SaaS):

6.1.1. Software and data hosted on cloud. Accessed through using thin client interface (e.g. web browser). Consumer may be offered limited user specific application configuration settings.

6.2. Infrastructure as a Service (IaaS)

6.2.1. Access to new technologies: Through use of provider’s systems, customers may access latest technology.

6.2.2. Provider’s offer servers, storage, network and operating systems – typically a platform virtualization environment – to consumers as an on-demand service, in a single bundle and billed according to usage.

7. objectives

7.1. The meaning of the client–server architecture and the advantages of this type of architecture for a DBMS.

7.2. The difference between two-tier, three-tier and n-tier client–server architectures.

7.3. About cloud computing and data as a service (DaaS) and database as a service (DBaaS).

7.4. Software components of a DBMS.

7.5. The purpose of a Web service and the technological standards used to develop a Web service.

7.6. The difference between distributed DBMSs, and distributed processing.

7.7. The architecture of a data warehouse.

7.8. About cloud computing and cloud databases.

8. architectures

8.1. Traditional Two-Tier Client-Server

8.2. Alternative Client-Server Topologies

8.3. Three-Tier Client-Server

9. Components of a DBMS

10. middleware

11. Cloud computing

11.1. Benefits

11.1.1. Cost-Reduction: Avoid up-front capital expenditure.

11.1.2. Scalability/Agility: Organisations set up resources on an as-needs basis.

11.1.3. Improved Reliability: Providers can devote expertise & resources on reliability of systems; not affordable by customer.

11.1.4. More flexible working practices: Staff can access files using mobile devices.

11.1.5. Increased competitiveness: Allows organizations to focus on their core competencies rather than their IT infrastructures.

11.1.6. Improved Security: Providers can devote expertise & resources to security; not affordable by customer.

11.2. Risks

11.2.1. Network Dependency: Power outages, bandwidth issues and service interruptions.

11.2.2. System Dependency: Customer’s dependency on availability and reliability of provider’s systems.

11.2.3. Cloud Provider Dependency: Provider could became insolvent or acquired by competitor, resulting in the service suddenly terminating.

11.2.4. Lack of control: Customers unable to deploy technical or organisational measures to safeguard the data. May result in reduced availability, integrity, confidentiality, intervenability and isolation.

11.2.5. Lack of information on processing transparency

11.3. Key Characteristics

11.3.1. On-demand self-service Consumers can obtain, configure and deploy cloud services without help from provider.

11.3.2. Broad network access Accessible from anywhere, from any standardized platform (e.g. desktop computers, laptops, mobile devices).

11.3.3. Resource pooling Provider’s computing resources are pooled to serve multiple consumers, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. Examples of resources include storage, processing, memory, and network bandwidth.

11.3.4. Rapid elasticity spikes in demand and reduces risk of outages and service interruptions. Capacity can be automated to scale rapidly based on demand.

11.3.5. Measured service Provider uses a metering capability to measure usage of service (e.g. storage, processing, bandwidth, and active user accounts).

12. Cloud-based database solutions

12.1. Data as a Service (DaaS) and

12.2. Database as a Service (DBaaS).

13. Transaction Processing Monitors