Generally speaking, I find that it is infinitely preferable to go with the solution proposed by your database system vendor. The situation with respect to implementing RI (Referential Integrity) on the client side springs to mind - and is a recipe for unmitigated disaster - read my answer to a post here about that particular can of worms!
You might might want to look at "Debezium" (a CDC project supported by RedHat, see here and here). Unfortunately, the SQL Server connector is only in alpha, but the last commit to the overall project was only 7 days ago, so it's active - you could always ask.
Having said that, Debezium is supported by RedHat which is always a good sign, however it involves setting up Apache Kafka - a complex system in itself.
If I were you, I would give careful thought to a cost/benefit analysis of going to the trouble (man-hours, potential for bugs even if the SQL Server connector gets out of alpha) of setting up a roll-your-own solution (OK, it's RedHat, but still...) or using an out-of-the-box solution from Microsoft themselves.
An interesting read (about LinkedIn's MySQL solution) here and here The last commit was slightly over a year ago, so I don't know how active the project is and I'm pretty sure that they won't be doing SQL Server anytime soon!