<commit_before>// Metadata created by nebel
//
// UserStory:

[id="introduction-debezium"]
= Introduction to {prodname}

{prodname} is a distributed platform that turns your existing databases into event streams,
so applications can see and respond immediately to each row-level change in the databases.

{prodname} is built on top of http://kafka.apache.org[Apache Kafka] and provides {link-kafka-docs}.html#connect[Kafka Connect] compatible connectors that monitor specific database management systems.
{prodname} records the history of data changes in Kafka logs, from where your application consumes them.
This makes it possible for your application to easily consume all of the events correctly and completely.
Even if your application stops unexpectedly,
it will not miss anything:
when the application restarts, it will resume consuming the events where it left off.

{prodname} includes multiple connectors.
In this tutorial, you will use the xref:{link-mysql-connector}[MySQL connector].<commit_msg>DBZ-5422 Update link format and multiple edits<commit_after>// Metadata created by nebel
//
// UserStory:

[id="introduction-debezium"]
= Introduction to {prodname}

{prodname} is a distributed platform that converts information from your existing databases into event streams, enabling applications to detect, and immediately respond to row-level changes in the databases.

{prodname} is built on top of http://kafka.apache.org[Apache Kafka] and provides {link-kafka-docs}.html#connect[Kafka Connect] compatible connectors that capture changes from database management systems.
{prodname} records the history of the data changes that occur in a database in Kafka logs.
Consuming applications can then read each change event record from the log, in order.
By taking advantage of Kafka's reliable streaming platform, {prodname} makes it possible for your application to easily consume all of the events that occur in a database correctly and completely.
Even if your application stops unexpectedly, or loses its connection, it does not miss events that occur during the outage.
After the application restarts, it resumes reading from the log from the point where it left off.

{prodname} includes multiple connectors, and each of them share similar capabilities.
The tutorial that follows focuses on the {link-prefix}:{link-mysql-connector}#debezium-connector-for-mysql[MySQL connector].
{'fraction_non_alphanumeric': 0.05889724310776942, 'fraction_numerical': 0.001670843776106934, 'mean_word_length': 5.335978835978836, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7593633', 'n_tokens_mistral': 582, 'n_tokens_neox': 562, 'n_words': 309}