:fire: Tracking v1 Deprecation :fire:
Tracking v1 has been around for a long time and accumulate a lot of issues. We redesigned the tracking system and developed Tracking v2 as a replacement. After around one year introducing Tracking v2, more than 80% tracking events have been using Tracking v2.
We are going to deprecate the Tracking v1 by the end of this year. More details will be shared in the next tech talk.
Background
Tracking v1 has many issues:
- No abstraction between backend services and tracking message queue. Any changes on the message queue will be very complex (this happened when we migrate from Kafka to Google Pub/Sub).
- Multiple data format: Avro, Protobuf, JSON
- Different ways to publish the event
- Different ways to register and update the event schema
- No proper monitoring during registering and updating tracking schema
- No proper schema graduation from staging to production, resulting to different schema between staging and production.
- Different architecture for frontend and backend tracking which is hard to maintain and keep them aligned.
- Security issue regarding credentials and access https://tvlk.slack.com/files/T02T3CAFM/F030LPLHUDR
Replacement
- Data Ops Platform v2 for Event Management (docs)
- Tracking Service v2 for Event Publishing (docs)
Timeline
- February 2022: Tracking v2 socialization via monthly tech talk
- 4 January 2023: Turn off tracking v1 data pipeline
- 11 January 2023: Tracking v1 access revocation and tracking v1 pipeline decommission
Migration Guide
Questions
If you have any questions, please discuss in #cde-tracking-support and mention @data-cde.