Skip to content

Commit e1eb024

Browse files
committed
Now with 100% more spell check
1 parent e1c969f commit e1eb024

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

_posts/2020-01-06-zero-data-loss-kafka-migration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ any downtime, and zero data loss. When we were first planning the migration, we
1818
joked that we wanted to avoid a single moment where we would try to swap Kafka
1919
all at once, like Indiana Jones tried in [Raiders of the Lost
2020
Ark](https://www.youtube.com/watch?v=0gU35Tgtlmg). In this post, I will share
21-
more aobut our Kafka migration to AWS MSK, and how we tried to avoid "Indiana
21+
more about our Kafka migration to AWS MSK, and how we tried to avoid "Indiana
2222
Jones moments."
2323

2424

@@ -78,7 +78,7 @@ key-performance indicators (KPIs) of the producer application.
7878

7979
With the test write phase completed, we could finally start the _actual_
8080
migration of data. Although we had done end-to-end testing in our development
81-
environment, the gradual rolover of production was still essential. Therefore
81+
environment, the gradual rollover of production was still essential. Therefore
8282
we continued with the next three phases:
8383

8484
1. Double-writes

0 commit comments

Comments
 (0)