A Database Problem Before Recommending Sql, Nosql Or Bigdata

1. What things would you want to know about a database problem before recommending a SQL or NoSQL or BigData solution, that would help you make that recommendation? Ans) The things that we consider before recommending SQL, NoSQL or BigData are: Scalability: NoSQL databases are designed to expand transparently and horizontally to take advantage of new nodes, and designed with low-cost hardware. SQL have problems in Scalability. Data Capability: RDBMS are intolerable for large data volumes. NoSQL distributed databases, allow data to be spread across thousands of servers and can store large volume of data. Maintaining is Cheaper: Maintaining RDBMS systems is expensive and need highly trained DBAs. On the other hand, NoSQL databases require†¦show more content†¦Ans) SQL is considered a better choice because of following reasons: †¢ SQL will be a best fit where we need 100% consistency of data, such as most of financial problems which cannot be achieved by NoSQL database. †¢ SQL offers more efficient access control and permission management tools and offers better performance in data collection. †¢ SQL offers data compression techniques so that data size can be reduced. †¢ SQL offers strong authentication and access protection and has better password management too. †¢ SQL automatically updates security patches to reduce maintenance costs. 3. Describe in a few sentences a business or computational problem you would want to solve with a NoSQL database, and what makes NoSQL a better choice in this case? Ans) NoSQL database are better choice when we have tables whose size is in TB, PB ets.., and most of their data is not inter-related so they can just treat them as key value pairs. With NoSQL data can be distributed across several nodes across countries i.e Sharding. NoSQL support auto-sharding, means that they automatically spread data across an arbitrary number of servers. NoSQL databases are more scalable and provide superior performance, and their data model addresses several issues that the relational model is not designed to address: †¢ Large volumes of structured, semi-structured, and unstructured data †¢ Agile sprints,