The image shows three boxes with yes/no questions and four boxes naming ways to support JSON data in the database. At the top of the image is a box labeled with question #1, "Is your use-case for JSON data mainly document-centric?".
An arrow labeled "yes" and "(JSON collections)" leads from that box to the box labeled with question #2, "Want to map documents to relational data?". An arrow labeled "no" leads from the question-1 box to a box labeled "Hybrid use: ordinary tables with one or more JSON-type columns".
An arrow labeled "yes" and "(views, to share data with SQL)" leads from the question-2 box to the box for question #3, which is labeled "Need to update documents directly?". An arrow labeled "no" leads from the question-2 box to a box labeled "JSON collection tables".
An arrow labeled "yes" leads from the question-3 box to a box labeled "JSON-relational duality views". And arrow labeled "no" leads from that box to a box labeled "JSON collection views".