From f99917d5a3742b7e78a5be519500ff4e28c3522e Mon Sep 17 00:00:00 2001 From: Wisam Naji Date: Sun, 3 Jul 2022 03:42:39 +0300 Subject: [PATCH] fixed lesson title --- module6-architecture-and-best-practices/r3-websockets/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/module6-architecture-and-best-practices/r3-websockets/README.md b/module6-architecture-and-best-practices/r3-websockets/README.md index 48ec80b..57e6338 100644 --- a/module6-architecture-and-best-practices/r3-websockets/README.md +++ b/module6-architecture-and-best-practices/r3-websockets/README.md @@ -1,4 +1,4 @@ -# Websockets +# WebSockets We've looked into many architectural concepts such as design patterns, best practices for performance and reliability, and usage of Redis for features like caching, job queues, and session stores, but all are still in the realm of REST APIs. Let us now look a bit beyond REST and explore other architectural choices in backend applications, starting with an interesting concept called WebSockets. The objectives of this lesson are: