Shared publicly  - 
Hey #BigData Developers: Google BigQuery is now available to the general public!

#BigQuery is a cloud hosted, massive data analytics service. It's based on Google's internal Dremel technology - the same system that allows us to run queries over our massive log file datasets. BigQuery features a SQL-like query language, scales to terabyte datasets and beyond, and is accessed via a RESTful. See Ju-kay Kwek's blog post about the launch, and what people are already building with BigQuery (

As a developer, here are my favorite things about BigQuery:
• Completely cloud hosted: worry about building your app, not infrastructure
• BigQuery is really really fast: query results over massive datasets come back on the order of seconds, not minutes or hours
• SQL-like query language: Easy to get started if you are familiar with general SQL syntax
My favorite thing about BigQuery: It's a RESTful API! You can work with BigQuery in the language of your choice.. but it's also easy to integrate it with App Engine.

I am really looking forward to seeing what other data developers build with the BigQuery API! Let us know what you are working on.

Google Engineers will be answering your BigQuery development questions at the Stack Overflow tag "google-bigquery":

Also, don't forget to add other Google DevRel staff that are working on data projects... we'd love to hear about your work!
+Ryan Boyd
+Kathryn Hurley
+Shawn Simister
Shawn Hannah (zonatime)'s profile photoyiming sun's profile photoBjörn Böttcher's profile photoBoyuan Guan's profile photo
Can you elaborate on how is big query better than mysql etc?
Good question +Peter George Sideris. In short, BigQuery is designed to allow developers to ask questions about massive datasets (think terabytes and beyond). It uses a SQL-like language, but BigQuery is not designed to be a transactional database. BigQuery works best on really really huge single table datasets (think log files and event history). MySQL is a relational database, very good for transactions. However, when a MySQL dataset gets very large, running a query can take minutes or hours. BigQuery is designed to return query results from really big datasets on the order of seconds.
+Michael Manoochehri So if you start with mysql and your data gets really immense, you have to change the architecture of your db in order to use BQuery?

I mean that if you get unexpected traffic and you need to swap to BQuery you need to change your tables etc to single ones and construct smarter queries? How does this work with PHP?
+Peter George Sideris Well, I would rather say that MySQL and tools like BigQuery serve very different needs. For example, if you are simply building a very massive log data collection system, that needs to be integrated into a web app, BigQuery is the perfect tool. If you are building an ACID transactional database, that provides row level transactions and that is well supported, look into MySQL. By the way, we offer a PHP lib for BigQuery and other Google APIs (see:
Add a comment...