Nosql has transformed and disrupted how web pages are presented. It's more suitable for web apps and has been fully adopted by major IT players such as Google.
Sql with its stability and power, begins to run into challenges with super large databases.
Large queries don't just die, they just take 8 hours or more to return
data. Join operations can be highly expensive.
I worked for a major healthcare institution who suffered immensely from their massive SQL solution. A Google exec on their board, steered them to Nosql where they began implementing huge data migration projects.
Reason: Doctors and nurses wanted web apps for immediate patient feedback. Sql was too slow.
Nosql has transformed and disrupted how web pages are presented. It's more suitable for web apps and has been fully adopted by major IT players such as Google.
Sql with its stability and power, begins to run into challenges with super large databases.
Large queries don't just die, they just take 8 hours or more to return
data. Join operations can be highly expensive.
I worked for a major healthcare institution who suffered immensely from their massive SQL solution. A Google exec on their board, steered them to Nosql where they began implementing huge data migration projects.
Reason: Doctors and nurses wanted web apps for immediate patient feedback. Sql was too slow.
With cache you can make web apps respond faster, not only by using NoSQL solutions.