Philosophy Mondays: Human-AI Collaboration
Today's Philosophy Monday is an important interlude. I want to reveal that I have not been writing the posts in this series entirely by myself. Instead I have been working with Claude, not just for the graphic illustrations, but also for the text. My method has been to write a rough draft and then ask Claude for improvement suggestions. I will expand this collaboration to other intelligences going forward, including open source models such as Llama and DeepSeek. I will also explore other moda...
Intent-based Collaboration Environments
AI Native IDEs for Code, Engineering, Science
Web3/Crypto: Why Bother?
One thing that keeps surprising me is how quite a few people see absolutely nothing redeeming in web3 (née crypto). Maybe this is their genuine belief. Maybe it is a reaction to the extreme boosterism of some proponents who present web3 as bringing about a libertarian nirvana. From early on I have tried to provide a more rounded perspective, pointing to both the good and the bad that can come from it as in my talks at the Blockstack Summits. Today, however, I want to attempt to provide a coge...
Philosophy Mondays: Human-AI Collaboration
Today's Philosophy Monday is an important interlude. I want to reveal that I have not been writing the posts in this series entirely by myself. Instead I have been working with Claude, not just for the graphic illustrations, but also for the text. My method has been to write a rough draft and then ask Claude for improvement suggestions. I will expand this collaboration to other intelligences going forward, including open source models such as Llama and DeepSeek. I will also explore other moda...
Intent-based Collaboration Environments
AI Native IDEs for Code, Engineering, Science
Web3/Crypto: Why Bother?
One thing that keeps surprising me is how quite a few people see absolutely nothing redeeming in web3 (née crypto). Maybe this is their genuine belief. Maybe it is a reaction to the extreme boosterism of some proponents who present web3 as bringing about a libertarian nirvana. From early on I have tried to provide a more rounded perspective, pointing to both the good and the bad that can come from it as in my talks at the Blockstack Summits. Today, however, I want to attempt to provide a coge...
>400 subscribers
>400 subscribers
Share Dialog
Share Dialog
In January I wrote a post saying that we need a standard for cloud databases. That post is now the #2 search result on google for “cloud database standards” and there are still no results that even hint at emerging standards. So it will be fun today to moderate a panel on this topic at the Glue Conference with Alex Iskold and Stu Charlton. I am planning on a lot of audience participation as there are a lot of technical folks at the conference. Here are some of the questions I am planning to cover:
What exactly is a cloud database?
Do we really need these? There is a recent paper which compares Map Reduce performance with parallel relational databases and finds the latter to perform 3-5x faster and require less code.
What about the approach pursued by Drizzle? Can’t we hang on to SQL that way?
What about key value stores? Those seem all the rage right now.
Is the need for cloud databases all about performance or is it also about ease of development?
Why do we need standards? Is portability really important? Who has migrated their current relational db ever? Is it learning curve?
Is there a native data format for the cloud? Is it XML? Is it JSON? Something else?
In the cloud, how will “things” be identified (certainly not autoincrement ID column)?
Why do we need all these separate query languages? FBQL, YQL, XQuery, SimpleDB queries, …
How does this relate to IP and licensing? SQL was invented by IBM in early 70s and not standardized until the mid 80s.
Any candidates for a cloud database standard?
If anyone has others questions they would like to see discussed (and are not at the conference), just add them as a comment. Also, of course, any answers to the questions above would be great as comments.
In January I wrote a post saying that we need a standard for cloud databases. That post is now the #2 search result on google for “cloud database standards” and there are still no results that even hint at emerging standards. So it will be fun today to moderate a panel on this topic at the Glue Conference with Alex Iskold and Stu Charlton. I am planning on a lot of audience participation as there are a lot of technical folks at the conference. Here are some of the questions I am planning to cover:
What exactly is a cloud database?
Do we really need these? There is a recent paper which compares Map Reduce performance with parallel relational databases and finds the latter to perform 3-5x faster and require less code.
What about the approach pursued by Drizzle? Can’t we hang on to SQL that way?
What about key value stores? Those seem all the rage right now.
Is the need for cloud databases all about performance or is it also about ease of development?
Why do we need standards? Is portability really important? Who has migrated their current relational db ever? Is it learning curve?
Is there a native data format for the cloud? Is it XML? Is it JSON? Something else?
In the cloud, how will “things” be identified (certainly not autoincrement ID column)?
Why do we need all these separate query languages? FBQL, YQL, XQuery, SimpleDB queries, …
How does this relate to IP and licensing? SQL was invented by IBM in early 70s and not standardized until the mid 80s.
Any candidates for a cloud database standard?
If anyone has others questions they would like to see discussed (and are not at the conference), just add them as a comment. Also, of course, any answers to the questions above would be great as comments.
No comments yet