From e716765f018c8e5c5bd6f01691b09127c8fa348c Mon Sep 17 00:00:00 2001 From: Alan Klimowski Date: Sun, 12 Jan 2025 13:04:53 -0600 Subject: [PATCH] fix: topic content resource issue Fixing visual bug due to a link getting into the main list and not being parsed correctly --- .../content/synchronous-io@Ihnmxo_bVgZABDwg1QGGk.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/data/roadmaps/system-design/content/synchronous-io@Ihnmxo_bVgZABDwg1QGGk.md b/src/data/roadmaps/system-design/content/synchronous-io@Ihnmxo_bVgZABDwg1QGGk.md index ccd462415..366d1ad0a 100644 --- a/src/data/roadmaps/system-design/content/synchronous-io@Ihnmxo_bVgZABDwg1QGGk.md +++ b/src/data/roadmaps/system-design/content/synchronous-io@Ihnmxo_bVgZABDwg1QGGk.md @@ -18,4 +18,6 @@ This antipattern typically occurs because: - The application uses a library that only provides synchronous methods for I/O. - An external library performs synchronous I/O operations internally. A single synchronous I/O call can block an entire call chain. +Visit the following links to learn more: + - [@article@What is Synchronous I/O antipattern?](https://learn.microsoft.com/en-us/azure/architecture/antipatterns/synchronous-io/)