Create a readme for usage with Change Data Capture

[roee88]

I think that we should describe what one can get when mover is combined with Debezium, along with motivation for why this architecture makes sense, and a step by step guide. Should we do it in this repo?

[SeanRooooney]

I changed the title because actually it is isn't limited to Debezium but any system can create KStreams/KTables from
data stores. We described how we started working with Debezium here: https://debezium.io/documentation/reference/connectors/db2.html and it gives the bigger context.

What format did you have in mind, a blog ?

[roee88]

A blog is an option, @ronenkat what do you think?

[ronenkat]

@roee88 @SeanRooooney there are two things.

1. a technical readme which should be of the git repo or website
2. a blog that describe the motivation and use-cases
   We should prepare both. I expect that we will be starting a blog on the M4D website, and we would need to start generating content, i.e.,. add content every week or two.

[roee88]

How about starting with a technical readme in the git repo? I really think this is needed for users to understand that this option exists.

[SeanRooooney]

The following describes the different combinations possible:
https://github.com/IBM/the-mesh-for-data-mover/blob/master/Mover-matrix.md