








Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
This overview covers various types of databases: centralized, distributed, relational, NoSQL, cloud, object-oriented, hierarchical, and personal. Each type is discussed in detail, including advantages, disadvantages, and examples. Centralized databases ensure data consistency and reduce the risk of manipulation. Distributed databases improve modular development and data availability. Relational databases ensure data consistency and integrity. NoSQL databases handle large data sets and offer flexibility. Cloud databases provide access to cloud computing services. Object-oriented databases represent data as objects. Hierarchical databases organize data in parent-child relationships. Network databases allow multiple children and parent nodes. Personal databases are simple and designed for a single user. Operational databases handle real-time data updates. Enterprise databases manage massive amounts of data and allow multiple user access.
Typology: Summaries
1 / 14
This page cannot be seen from the preview
Don't miss anything!
a) N-tier architecture The N- tier architecture application is distributed among three or more separate computers in a distributed network. The common form of N-tier is the 3-tier application, where the user interface programming is in the users computer and the business logic is in a centralized computer and the data which is needed in the computer that manages the database. It is implied on the client/server program model. If there are more than three distribution levels or tiers involved the additional tiers are usually associated with the business logic tier. It is also referred to as the pulling apart of an application into separate layers or finer grains. One of the best example of this architecture in the web applications is the shopping cart web application. Here the client tier interacts with the user via the GUIs with the application and the application server. In most of the web applications the client is a web browser. The integration tier allows the N-tier architecture to be vendor independent. The business tier is also considered as the integration tier. The encapsulation will allow the application to communicate with the business tier in a way that all the nodes are intelligible. The final application tier is the data tier. It mostly consists of the database servers. The data is kept neutral and independent from the application servers or the business logic. If the data has its own tier it improves the scalability and the performance and as it grows it easily moves to another powerful machine. Benefits of N-Tier Architecture It helps in improving the scalability and supports the cost-efficient application building. It helps in making the applications more readable and reusable. The applications that are made are robust as they have no single point of failure. The tiers function with relative independence. Reusability is important for the web applications.
Authentication and authorization is provided for the security. This allows the web server to restrict the user access which is based on the pre-determined criteria. It helps the developers to build the web applications as it allows the developers to apply their specific skill to that part of a program which best suits their skill set.
There are various types of databases used for storing different varieties of data:
It is the type of database that stores data at a centralized database system. It comforts the users to access the stored data from different locations through several applications. These applications contain the authentication process to let users access data securely. An example of a Centralized database can be Central Library that carries a central database of each library in a college/university.
● It has decreased the risk of data management, i.e., manipulation of data will not affect the core data. ● Data consistency is maintained as it manages data in a central repository.
● Homogeneous DDB: Those database systems which execute on the same operating system and use the same application process and carry the same hardware devices. ● Heterogeneous DDB: Those database systems which execute on different operating systems under different application procedures, and carries different hardware devices.
● Modular development is possible in a distributed database, i.e., the system can be expanded by including new computers and connecting them to the distributed system. ● One server failure will not affect the entire data set.
a. Key-value storage: It is the simplest type of database storage where it stores every single item as a key (or attribute name) holding its value, together. b. Document-oriented Database: A type of database used to store data as JSON-like document. It helps developers in storing data by using the same document-model format as used in the application code. c. Graph Databases: It is used for storing vast amounts of data in a graph-like structure. Most commonly, social networking websites use the graph database. d. Wide-column stores: It is similar to the data represented in relational databases. Here, data is stored in large columns together, instead of storing in rows.
● It enables good productivity in the application development as it is not required to store data in a structured format. ● It is a better option for managing and handling large data sets. ● It provides high scalability. ● Users can quickly access data from the database through key-value.
Document databases are primarily built for storing information as documents, including, but not limited to, JSON documents. These systems can also be used for storing XML documents, for example. Key-value stores group associated data in collections with records that are identified with unique keys for easy retrieval. Key-value stores have just enough structure to mirror the value of relational databases while still preserving the benefits of NoSQL. Wide-column databases use the tabular format of relational databases yet allow a wide variance in how data is named and formatted in each row, even in the same table. Like key-value stores, wide-column databases have some basic structure while also preserving a lot of flexibility. Graph databases use graph structures to define the relationships between stored data points. Graph databases are useful for identifying patterns in unstructured and semi-structured information. Why use NoSQL? Customer experience has quickly become the most important competitive differentiator and ushered the business world into an era of monumental change. As part of this revolution, enterprises are interacting digitally – not only with their customers, but also with their employees, partners, vendors, and even their products – at an unprecedented scale. This interaction is powered by the internet and other 21st century technologies – and at the heart of the revolution are a company’s cloud, mobile, social media, big data, and IoT applications.
How are these applications different from legacy enterprise applications like ERP, HR, and financial accounting? Today’s web, mobile, and IoT applications share one or more (if not all) of the following characteristics. They need to: Support large numbers of concurrent users (tens of thousands, perhaps millions) Deliver highly responsive experiences to a globally distributed base of users Be always available – no downtime Handle semi- and unstructured data Rapidly adapt to changing requirements with frequent updates and new features
It is the database that typically follows the network data model. Here, the representation of data is in the form of nodes connected via links between them. Unlike the hierarchical database, it allows each record to have multiple children and parent nodes to form a generalized graph structure.
● It is simple and easy to handle. ● It occupies less storage space as it is small in size.
● Multi processes are supportable over the Enterprise database. ● It allows executing parallel queries on the system. ●