It's really quite a good intro to the subject, I think.
Jetpants: a MySQL toolkit for managing billions of rows and hundreds of DBs
11–20 of 28 posts
Re: Jetpants: a MySQL toolkit for managing billions of rows and hundreds of DBs
#12Re: Jetpants: a MySQL toolkit for managing billions of rows and hundreds of DBs
#13Is there a mailing list for jetpants so we can ask questions? For example how should my application connect to mysql? Should it connect directly to mysql or to a jetpants server and how?
re: your immediate question, you still connect to MySQL as normal. Jetpants isn't a server, middleware, framework, or ORM. Rather, it's a toolkit. Jetpants has a command suite that you can use to run its built-in functionality, but it's also a Ruby gem that you can integrate into custom scripts however you'd like.
The functionality is all geared towards managing large DBs (importing/exporting lots of data quickly, copying files quickly, etc) and managing large numbers of servers (promoting/demoting masters and slaves, adding new machines to a pool, rebalancing a shard).
Re: Jetpants: a MySQL toolkit for managing billions of rows and hundreds of DBs
#14Re: Jetpants: a MySQL toolkit for managing billions of rows and hundreds of DBs
#15My quick reading of this is that its suited for databases that don't change much (or at all) once the data is inserted, and not as much for apps that need to keep strong ACID compliance with guaranteed referential integrity.
Definitely please let me know how you got that impression though -- I'm happy to improve confusing things in the docs.
As for ACID compliance: Jetpants is a toolkit for MySQL / InnoDB, and doesn't really impact the referential integrity guarantees of those systems any more or less than other partitioning schemes. MySQL is inherently not a distributed system, for better or worse.
Re: Jetpants: a MySQL toolkit for managing billions of rows and hundreds of DBs
#16Is there a mailing list for jetpants so we can ask questions? For example how should my application connect to mysql? Should it connect directly to mysql or to a jetpants server and how?
Good call -- we'll definitely set one up if there's sufficient need. Until then, feel free to email me; my email address is in the gemspec. I'll write up an FAQ once I have enough questions answered. re: your immediate question, you still connect to MySQL as normal. Jetpants isn't a server, middleware, framework, or ORM. Rather, it's a toolkit. Jetpants has a command suite that you can use to run its built-in functio…
Another question - we are using django so are considering Postgres since there is a python connection pool available. Could Jetpants be potentially used for Postgres? ie how much of the functionality is Mysql specific?
Re: Jetpants: a MySQL toolkit for managing billions of rows and hundreds of DBs
#17Earlier quoted context omitted.
Good call -- we'll definitely set one up if there's sufficient need. Until then, feel free to email me; my email address is in the gemspec. I'll write up an FAQ once I have enough questions answered. re: your immediate question, you still connect to MySQL as normal. Jetpants isn't a server, middleware, framework, or ORM. Rather, it's a toolkit. Jetpants has a command suite that you can use to run its built-in functio…
Thanks! Another question - we are using django so are considering Postgres since there is a python connection pool available. Could Jetpants be potentially used for Postgres? ie how much of the functionality is Mysql specific?
I also made the mistake of putting "mysql" in the names of a few methods. At some point soon I'll change those to more generic names, and alias the old names to the new generic ones.
Re: Jetpants: a MySQL toolkit for managing billions of rows and hundreds of DBs
#18Re: Jetpants: a MySQL toolkit for managing billions of rows and hundreds of DBs
#19Earlier quoted context omitted.
Thanks! Another question - we are using django so are considering Postgres since there is a python connection pool available. Could Jetpants be potentially used for Postgres? ie how much of the functionality is Mysql specific?
The core functionality is currently very MySQL-specific. In theory a plugin could override a bunch of methods to target Postgres, and maybe even Redis or other persistent data stores with replication and import/export functionality. It would be a lot of work though. I also made the mistake of putting "mysql" in the names of a few methods. At some point soon I'll change those to more generic names, and alias the old n…
Thanks very much Evan as well for our chats ages ago (Andrew here), was happy to see you release this tool!
Re: Jetpants: a MySQL toolkit for managing billions of rows and hundreds of DBs
#20[deleted]
jetpants parallelizes many steps of this process allowing for greater throughput than what could be normally achieved by traditional tools.