Quote: "PartiQL requires the Java Runtime (JVM) to be installed on your machine."
And that right there is where they lost me. Nooo thank you.
PartiQL: One query language for all your data
71–80 of 88 posts
Re: PartiQL: One query language for all your data
#72There is one word that every vendor hates: "vendor agnostic". Minor differences in SQL dialects are not a bug, they are features for most vendors.
Most customers running on Amazon (or any cloud) want to move from having to maintain their own databases (which takes a lot of effort) to paying someone else do it. Amazon knows this.
This move looks like Amazon has everything to win and every other vendor has everything to lose. Even if they say the opposite (you can switch from Amazon to your own) - they know that extremely few customers have the will to operationalize their own databases. So they know that only the opposite will happen - customers will switch from self hosted to Amazon services. They have also been openly predatorial towards other open source databases (e.g. aws elasticsearch and mongo). No wonder all Amazon services already support this.
In that context, who is the target audience and what is the deployment model here? Are vendors going to integrate this directly into their databases? Or users have to run their own proxy instances? Or is it compiled into the application as a library?
Re: PartiQL: One query language for all your data
#73Earlier quoted context omitted.
The SQL standard includes JSON support: https://modern-sql.com/blog/2017-06/whats-new-in-sql-2016
The SQL standard is different from what databases actually support. No RDBMS supports this yet. Only Elasticsearch, Couchbase, and managed services like Rockset and CosmosDB.
[deleted]
Re: PartiQL: One query language for all your data
#74Earlier quoted context omitted.
It's extremely relevant to the OP.
Still, it is always appropriate to add a disclosure that you're affiliated with the project you're linking to.
That's a good point. I usually make it clearer but I guess the original comment in this thread was a little ambiguous. Thanks for the feedback.
Re: PartiQL: One query language for all your data
#75Earlier quoted context omitted.
The SQL standard includes JSON support: https://modern-sql.com/blog/2017-06/whats-new-in-sql-2016
The SQL standard is different from what databases actually support. No RDBMS supports this yet. Only Elasticsearch, Couchbase, and managed services like Rockset and CosmosDB.
Oracle 12.2+ reportedly supports the ISO SQL/JSON though I haven't tried it. Which btw looks like mostly just renames of Postgres functions.
https://docs.oracle.com/en/database/oracle/oracle-database/1...
Re: PartiQL: One query language for all your data
#76Earlier quoted context omitted.
You missed the point. The modern infrastructure's primary value is scalability. This number is of course bad, for the data. But this number will be more impressive when the data is million time bigger.
You missed the point. Modern infrastructure's scalability is irrelevant if even one user's experience is poor. In the era of 64-core processors, scaling horizontally is meaningless for 99.9% of architecture designs. Latency matters to everyone, always. Trivial queries taking nearly 1/10th of a second on modern kit is absolutely atrocious, and shows a total lack of awareness of performance as a feature.
I mean modern infrastructure's user experience is very poor compared to decades ago's PC based software...
Re: PartiQL: One query language for all your data
#77@dlurton since you seem to be speaking for the PartiQL team on this (congrats on the launch!): The reference implementation is open source; what's the plan for the language spec? Is that something that AWS is going to own and control? The website references the PartiQL Steering Committee -- is that just AWS folks or is the intention to make it more broadly composed of members of the community you build?
I'm interested in adopting PartiQL for our product, but would we get to participate in the evolution of the language or would we purely be downstream of the decisions made to benefit AWS products and services?
Re: PartiQL: One query language for all your data
#78AWS is all-in on data lock-in.
This may be powerful and useful, but it is proprietary, nontransparent, unstandardized, and nonportable.
I get that every database has some platform lock-in, but its getting ridiculous. At least amazon's relational offerings need to adhere to binary driver protocols.
Re: PartiQL: One query language for all your data
#79Re: PartiQL: One query language for all your data
#80Earlier quoted context omitted.
Which ones?
I don't know much about compilers, but basically the ones don't have anywhere else to put the context of a closure.
I don't think that's what happens in the JVM, you can google up the invokevitual + other supporting gunk/mechanism for this.