Users can build custom conversational experiences using Google Assistant’s voice and visual APIs. Take users on journeys through a product, using Assistant’s natural language understanding (NLU) capabilities and developer tools.
N/A
PostgreSQL
Score 8.7 out of 10
N/A
PostgreSQL (alternately Postgres) is a free and open source object-relational database system boasting over 30 years of active development, reliability, feature robustness, and performance. It supports SQL and is designed to support various workloads flexibly.
I'm in a Me vs. The World environment rather often. I can connect to my outer realm when heading to live meetings. Auditions, job assignments all via my assistant. I like having the ability to capture the moment and rewrite it as well. This is a primary driver for me. Sometimes branching out or when collaborating, I think I work a little harder in the moment than Google Assistant might but that is moreso my limitations and not the feature so much. I catch this scene when I'm in a group environment or at times having to create and respond to a larger scale event. Not a deal breaker for me however.
PostgreSQL is best used for structured data, and best when following relational database design principles. I would not use PostgreSQL for large unstructured data such as video, images, sound files, xml documents, web-pages, especially if these files have their own highly variable, internal structure.
I think newer, complementary ideas are a bit sharper than Google Assistant especially in a Q&A environment or when seeking some depth to a subject. That enhancement is to be expected I feel. And Google Assistant is not so self limiting so I don't have a lot of improvement needs because I use this for what I've become accustomed to and for the ability overall.
It is always important to do your best around hectic places, in bad tower signal areas or even if trying to do something new while using Google Assistant. Have patience in the setting. It pays off.
I feel this can be adjusted and after some trial and error you sort of start knowing what will work and how. And I have to say the overall impact becomes personal and we are all different. I'm small scale and as I've said, it works.
Postgresql is the best tool out there for relational data so I have to give it a high rating when it comes to analytics, data availability and consistency, so on and so forth. SQL is also a relatively consistent language so when it comes to building new tables and loading data in from the OLTP database, there are enough tools where we can perform ETL on a scalable basis.
The data queries are relatively quick for a small to medium sized table. With complex joins, and a wide and deep table however, the performance of the query has room for improvement.
There are several companies that you can contract for technical support, like EnterpriseDB or Percona, both first level in expertise and commitment to the software.
But we do not have contracts with them, we have done all the way from googling to forums, and never have a problem that we cannot resolve or pass around. And for dozens of projects and more than 15 years now.
The online training is request based. Had there been recorded videos available online for potential users to benefit from, I could have rated it higher. The online documentation however is very helpful. The online documentation PDF is downloadable and allows users to pace their own learning. With examples and code snippets, the documentation is great starting point.
I chose this because it was easier for me and can be accessed via mobile and laptop too because it enables cross device support because it helps in adding more depth to my life, and can help me save tons of time.
Although the competition between the different databases is increasingly aggressive in the sense that they provide many improvements, new functionalities, compatibility with complementary components or environments, in some cases it requires that it be followed within the same family of applications that performs the company that develops it and that is not all bad, but being able to adapt or configure different programs, applications or other environments developed by third parties apart is what gives PostgreSQL a certain advantage and this diversification in the components that can be joined with it, is the reason why it is a great option to choose.
Easy to administer so our DevOps team has only ever used minimal time to setup, tune, and maintain.
Easy to interface with so our Engineering team has only ever used minimal time to query or modify the database. Getting the data is straightforward, what we do with it is the bigger concern.