Explain Amazon SimpleDB with its benefits.

-

 AMAZON SIMPLEDB

Amazon SimpleDB is a highly available NoSQL data storage that relieves database administrators of their duties. Developers just use web service requests to save and access data objects, and Amazon SimpleDB handles the rest. Amazon SimpleDB, unlike relational databases, is designed to provide high availability and flexibility with minimal or no administration overhead. Amazon SimpleDB automatically builds and manages numerous globally dispersed duplicates of your data behind the scenes to provide high availability and data durability. The service only costs you for the resources used in storing your data and delivering your requests. You may alter your data model on the fly, and data is indexed for you automatically. You can concentrate on application development without having to worry about infrastructure provisioning, high availability, software maintenance, schema, and index management, and performance optimization using Amazon SimpleDB. 

This SimpleDB service provides streamlined access to data storage and query tools, allowing quickly uploading data and easily retrieving or changing that data. Customers who have relatively simple data needs, such as data storage, should utilize SimpleDB. A firm, for example, may use cookies to track visits to its website. The company may read the cookies to determine the visitor's identity and the feeds they are not interested in. Amazon SimpleDB allows users to store tens of attributes for a million customers, but not thousands of attributes for a single customer.


Benefits of Amazon Simple DB

Low touch 

The service enables you to devote your complete attention values added application development rather than time-consuming database administration. Amazon SimpleDB supports infrastructure provisioning, hardware and software maintenance, data replication and indexing, and performance tweaking automatically. 


Highly available:

Amazon SimpleDB produces numerous globally scattered copies of each data item you save automatically. This ensures high availability and durability; if one replica fails, Highly Amazon SimpleDB may fail over to another replica in the system. 


Flexible: 

As your company or application grows, you can quickly represent these changes in Amazon SimpleDB without having to worry about breaking a strict schema or refactoring code - simply add another characteristic to your Amazon SimpleDB data set as needed. You may also pick between consistent and eventually consistent read requests, giving you the freedom to tailor read performance (latency and throughput) and consistency requirements to the demands of your application, or even divergent sections of your application.


Simple to use: 

Amazon SimpleDB simplifies access to the store and query tasks that are normally performed by a relational database cluster while excluding additionally complicated, often unneeded database activities. Through a simple set of API methods, you may rapidly add data and simply retrieve or change that data.


Designed for use with other Amazon Web Services: 

Amazon SimpleDB is intended to be readily integrated with other AWS services such as Amazon S3 and EC2, providing the framework for developing web-scale applications. Developers, for example, can run their programs on Amazon EC2 and store their data objects on Amazon S3. Amazon SimpleDB may then be used from within the application in Amazon EC2 to query the object metadata and return references to the objects stored in Amazon S3. Developers may also utilize Amazon SimpleDB in conjunction with Amazon RDS for applications that require both relational and non-relational databases. Data transfers between Amazon SimpleDB and other Amazon Web Services within the same Region are free. 


Secure: 

Amazon SimpleDB offers an HTTPS endpoint for a secure, encrypted connection between your application or client and your domain. Furthermore, by integrating with AWS Identity and Access Management, you may provide user or group-level access to specified SimpleDB domains and activities.


Inexpensive: 

Amazon SimpleDB passes on the financial benefits of Amazon's scalability to you. You just pay for the resources you use. This implies that with Amazon SimpleDB, data store reads, and writes are paid by the computing resources spent by each operation, and you are not billed for computing resources when you are not actively utilizing them (i.e., making requests).



Comments

Post a Comment

Popular posts from this blog

Suppose that a data warehouse for Big-University consists of the following four dimensions: student, course, semester, and instructor, and two measures count and avg_grade. When at the lowest conceptual level (e.g., for a given student, course, semester, and instructor combination), the avg_grade measure stores the actual course grade of the student. At higher conceptual levels, avg_grade stores the average grade for the given combination. a) Draw a snowflake schema diagram for the data warehouse. b) Starting with the base cuboid [student, course, semester, instructor], what specific OLAP operations (e.g., roll-up from semester to year) should one perform in order to list the average grade of CS courses for each BigUniversity student. c) If each dimension has five levels (including all), such as “student < major < status < university < all”, how many cuboids will this cube contain (including the base and apex cuboids)?

-
Image
a) A Snowflake Shema is shown in figure below: b) The specific OLAP operations to be performed: 1. Roll-up on course from course_id to department. 2. Roll-up on a student from student_id to university. 3. Dice on course, student with department ="CS" and university = "biguniversity" 4. Drill-down on a student from the university to student_name. c) N = 4 dimensions The cube will contain 54 = 625 cuboids.
Read more

Suppose that a data warehouse consists of the four dimensions; date, spectator, location, and game, and the two measures, count and charge, where charge is the fee that a spectator pays when watching a game on a given date. Spectators may be students, adults, or seniors, with each category having its own charge rate. a) Draw a star schema diagram for the data b) Starting with the base cuboid [date; spectator; location; game], what specific OLAP operations should perform in order to list the total charge paid by student spectators at GM Place in 2004?

-
Image
  b) The specific OLAP operations to be performed are: 1. Roll-up on date from date id to year. 2. Roll-up on spectator from spectator id to status. 3. Roll-up on location from location id to location name. 4. Roll-up on the game from game id to all. 5. Dice with status= “students”, location name= “GM Place”, and year=2004
Read more

Suppose that a data warehouse consists of the three dimensions time, doctor, and patient, and the two measures count and charge, where a charge is the fee that a doctor charges a patient for a visit. a) Draw a schema diagram for the above data warehouse using one of the schemas. [star, snowflake, fact constellation] b) Starting with the base cuboid [day, doctor, patient], what specific OLAP operations should be performed in order to list the total fee collected by each doctor in 2004? c) To obtain the same list, write an SQL query assuming the data are stored in a relational database with the schema fee (day, month, year, doctor, hospital, patient, count, charge)

-
Image
Solution: a) Star Schema is shown in the figure below: b) First, we should use the roll-up operation to get the year 2004(rolling-up from the day then month to a year). After getting that, we need to use the slice operation to select (2004). Second, we should use roll-up operation again to get all patients. Then, we need to use the slice operation to select (all). Finally, we get a list of the total fee collected by each doctor in 2004. So, 1. roll up from day to month to year 2. slice for year = “2004” 3. roll up on patient from the individual patient to all 4. slice for patient = “all” 5. get the list of the total fees collected by each doctor in 2004 c) Select doctor, Sum(charge) From fee Where year = 2004 Group by doctor
Read more