<Table> <Tr> <Td> </Td> <Td> The lead section of this article may need to be rewritten . Please discuss this issue on the article's talk page . Use the lead layout guide to ensure the section follows Wikipedia's norms and to be inclusive of all essential details . (March 2016) (Learn how and when to remove this template message) </Td> </Tr> </Table> <Tr> <Td> </Td> <Td> The lead section of this article may need to be rewritten . Please discuss this issue on the article's talk page . Use the lead layout guide to ensure the section follows Wikipedia's norms and to be inclusive of all essential details . (March 2016) (Learn how and when to remove this template message) </Td> </Tr> <P> In 2006, Neal Ford coined the term "polyglot programming", to express the idea that applications should be written in a mix of languages to take advantage of the fact that different languages are suitable for tackling different problems . Complex applications combine different types of problems, so picking the right language for each job may be more productive than trying to fit all aspects into a single language . This same concept can be applied to databases; so that you can have an application that talks to different databases using each for what they are best at to achieve an end goal, thus giving birth to polyglot persistence . </P> <P> There are numerous databases out there which solves different problems . Having a single database to solve all of the requirements results in non-performant solution and a "jack of all trades, master of none" situation . For example, data relationships . RDBMS solutions are good at enforcing that relationships exist . To discover a relationship or to find data from different tables that belong to the same object, we can make use of SQL join . This might work when the data is smaller is size . The problem starts when the data grows bigger . A graph database might solve the problem of relationships in case of BigData but it might not solve the problem of transactions which is provided by RDBMS . A NoSQL document database might be able to store your unstructured data to solve that problem . So, we have different problems here which are solved by different databases all from the same application . Simply put, polyglot persistence is using different data storage technologies to handle varying data storage needs . </P>

What is polyglot persistence in terms of nosql and database
find me the text answering this question