Piwik has the problem that it writes directly to MySQL as the activity happens. If your database is down, you lose data. If you have a spike of traffic above what your DB can handle in writes, you lose data.
Snowplow doesn't have this problem.
Snowplow doesn't have this problem.
tracking -> collection -> enrichment -> storage
Between each step there is typically some kind of persistent queue (mostly S3/Kinesis), and data won't be lost if a downstream component is not operational. Examples:* If your event collector is unavailable, raw events will be cached in the tracker in localStorage, SQLite or similar
* If your Redshift database is read-only for maintenance, enriched events will be held back until Redshift is writeable again
That really doesn't inspire confidence that they know what they're doing. md5 is a canary in the coal mine for me, and I definitely won't use Piwik now.