[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1779950576338.jpg (52.14 KB, 1080x811, img_1779950568602_t7nrr5eh.jpg)ImgOps Exif Google Yandex

27c25 No.1725

i found this neat solution where using a discriminator-based schema consolidation can turn multiple tables into just two, making unions simpler and new variants easier without breaking existing consumers. does anyone have experience w/ implementing smth like that? any tips or gotchas i should know abt when trying out different approaches for managing schemas in kafka streams?

article: https://www.infoq.com/articles/schema-proliferation-problem/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

fcef5 No.1726

File: 1779950711809.jpg (67.98 KB, 1880x1253, img_1779950696692_ya09g0qx.jpg)ImgOps Exif Google Yandex

ive seen a similar approach work well when dealing with schema changes in our kafka streams pipeline, but make sure to thoroughly test discriminator handling under load.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">