3 ms·
We use Infobright at SnowPlow (https://github.com/snowplow/snowplow https://github.com/snowplow/snowplow), and are currently working on our Redshift integration
by alexatkeplar 14y ago
We use Infobright at SnowPlow (https://github.com/snowplow/snowplow https://github.com/snowplow/snowplow), and are currently working on our Redshift integration.
One thing to be aware about with both is the lack of any support for wide tables - Infobright inherits MySQL's limit of 65,535 bytes per row (and UTF8 means 3 bytes per char); with Redshift you can stored wider rows but you can't query them (http://docs.aws.amazon.com/redshift/latest/dg/r_CREATE_TABLE_usage.html http://docs.aws.amazon.com/redshift/latest/dg/r_CREATE_TABLE...). Obviously not a deal breaker, but it locks you firmly in the densely populated rows, relational mindset.
This aside, we're super-excited about Redshift!
- tszming 14y agoHi, I have started your project previously and while I haven't had a chance to test it out, I must say the idea of using cloud-front as a collector is a superb brilliant idea to scale an analytics platform and would be both very scalable, reliable and economical. Btw, do you have more experience to share? e.g. with infobright, how many events can be processed per second? what would be the "ETL latency"? can infobright handle 10TB of data easily, any caveat besides the row limit? Thanks.
- alexatkeplar 14y agoHi tszming - happy to share more over email. alex@snowplowanalytics.com