Works pretty well for us (twitter.com).
One nit about snowflake in your article (i'm the author of snowflake)– the zookeeper integration is optional and only used for sanity checking the configuration (that the worker ids are distinct, etc).
This wouldn't work for us. We need the ids to sort by time across users, which this wouldn't do.
we've been running snowflake for weeks already
The twitter api includes string representations of the ids already and we encourage everyone to use those rather than the numeric ones.
we don't use incrementing ids, but needed ids that increase over time (so that you can sort tweets by them). hence, snowflake: http://github.com/twitter/snowflake
oh and feel free to contact me directly at ryan@twitter.com
Works pretty well for us (twitter.com).
One nit about snowflake in your article (i'm the author of snowflake)– the zookeeper integration is optional and only used for sanity checking the configuration (that the worker ids are distinct, etc).
This wouldn't work for us. We need the ids to sort by time across users, which this wouldn't do.
we've been running snowflake for weeks already
The twitter api includes string representations of the ids already and we encourage everyone to use those rather than the numeric ones.
we don't use incrementing ids, but needed ids that increase over time (so that you can sort tweets by them). hence, snowflake: http://github.com/twitter/snowflake
oh and feel free to contact me directly at ryan@twitter.com