BUS 112 Assignment-4
pdf
keyboard_arrow_up
School
San Jose State University *
*We aren’t endorsed by this school
Course
112
Subject
Information Systems
Date
Dec 6, 2023
Type
Pages
4
Uploaded by ConstableCrabPerson2017
Assignment
1.
Describe various cloud database services provided by cloud computing vendors Amazon,
Microsoft, and Google. Identify their key characteristics and compare them in a tabular format.
AWS Database Services
Key Characteristics
Amazon Aurora
Designed to provide high performance and
availability on a global scale, the system
integrates other AWS services with full
compatibility for MySQL and PostgreSQL
Amazon RDS
Within the cloud, this type of database is
most often used to set up, operate, and scale
the database.
Amazon Redshift
Data are structured to semi-structured and
analyzed using SQL across data
warehouses, operational databases, and data
lakes without requiring the management of
data warehouse infrastructure.
Amazon DynamoDB
With this database, you can run any
high-performance application at any scaling
level because it is a fully managed,
serverless, key-value NoSQL database.
Amazon DocumentDB
As a JSON document database, it simplifies
architecture and provides cost-effective and
easy-to-use capabilities for storing and
operating critical documents.
Amazon Neptune
Cloud-based graph database service
designed to make the creation and
maintenance of graph-based applications
easier
Microsoft Database Services
Key Characteristics
Azure Cosmos DB
With its support for the open-source
databases PostgreSQL, MongoDB, and
Apache Cassandra, you can develop a
high-performance application at any scale
and of any size.
Azure SQL DB
Using this platform, apps can be built in a
simplified and flexible manner where they can
scale to meet demand and gain insight into
the context of near-real-time events without
affecting performance.
Azure Database for MySQL
This is an open source that is primarily used
for application development, which is
cost-effective and easier to set up, operate,
and scale compared to other open-source
platforms.
Azure Database for MariaDB
The MariaDB database service is an
open-source database service that is fully
managed by the community and provides
high availability and elastic scaling for
open-source developers using it.
Azure Database for PostgreSQL
Open-source developers are more likely to
find success with open-source technologies
when they are focused on application
innovation, as it is fully managed and can
scale the workload quickly with ease while
securing enterprise-ready apps.
Azure Cache for Redis
This is an open-source Redis server that has
been designed to accelerate the app's data
layer with an in-memory data store that has
been designed for web apps to provide speed
and scale.
Google Cloud Database Services
Key Characteristics
Cloud SQL
With the help of this service, you will be able
to set up, maintain, manage, and administer
the relational databases on the platform
efficiently and effectively.
Cloud Spanner
In addition to its high scalability, it is
compatible with both relational and
non-relational workloads, in which case it is
suitable for both relational and non-relational
workloads.
Cloud Bigtable
In addition to being fast, fully managed, and
massively scalable, it has tens of thousands
of columns and billions of rows that are used
to store large amounts of single-keyed data
with low latency in a NoSQL database service
Firestore
NoSQL database that is primarily focused on
storing documents. The documents are
arranged into a structure in which there is no
table or row, but rather there are a series of
key-value pairs organized within each
document as a set.
Firebase Realtime Database
Syncing data between users via JSON
messaging, a cloud-hosted NoSQL database
allows for real-time data syncing, from any
active client to any other, on a global scale. In
addition to being able to be used locally, it
can also be used internationally.
Memorystore
An open-source Redis and Memcached
database the purpose of which is to enable
high availability, failover, patching, and
monitoring of Redis and Memcached
databases. There is a range of use cases
from simple ones to real-time analytics that
can be performed.
AWS’s strengths are in its dominant market position where it provides support for large
organizations with extensive training on a global reach. But its weaknesses are difficult to use,
its overwhelming options, and its cost management
Microsoft Azure is the second largest provider of cloud database service and integration with
Microsoft tools and software. Having a broad feature set and their support for Open source. But
it’s weakness is in it’s documentation and also incomplete management tooling.
Google Cloud is designed with cloud-native businesses in mind. Having a commitment in Open
source and portability while having affordable discounts. Its weaknesses would be that of Late
entry to the IaaS market, and fewer features and services than its competitors.
2. Describing the ERD Relationships listed:
According to the diagram, The Student-to-Professor Entity (Many-to-One Relationship):
Where Each Student is advised by One Professor
The Professor-to-Class Entity (One-to-Many Relationship):
Where One Professor can teach many Classes
The Professor-to-Student Entity (One-to-Many Relationship):
Where One Professor Can Advise Many Students
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
The Class-to-Professor Entity (Many-to-One Relationship):
Where Many Class is Taught by One Professor
3. Creating the ERD Relationships with the description listed:
4. Writing the Business Rules according to the ERD diagram:
There are 4 Entities:
Publisher, Book, Contract and Author
Relationships:
Book and Author Entities:
The relationship is 1:M (A single Author can write many books.
Many Books can be written by a Single Author)
Author and Contract Entities:
The relationship is 1:M (Single Author can sign many contracts,
Many Contracts can be signed by a Single Author)
Contract and Publisher Entites:
The relationship is 1:M (Single Publisher can submit many
Contract, Many Contract is submitted by a Single Publisher)
Publisher and Book Entites:
The relationship is 1:M (Publisher can publish many Books, Many
Books can be published by a Publisher)