chore: sync content to repo (#10242)

Co-authored-by: nilbuild <4921183+nilbuild@users.noreply.github.com>

roadmaps/api-design/content/resource-modeling@8IDks2DNFZ5nER7wK2Bu4.md

@@ -1,3 +1,5 @@
+# undefined
+
 #Resource Modeling
 
 Resource modeling is the process of deciding what "things" your API exposes and how they map to URLs. A resource is any noun your API manages, like a user, an order, or a product. Modeling it means defining its boundaries, its relationships to other resources, and what data it carries. Good resource modeling done upfront prevents awkward URL structures and inconsistent data shapes that are painful to fix once consumers are depending on your API.

roadmaps/api-design/content/web-sockets@UQ8N7gcVpRLAYXgUNHBt5.md

@@ -4,6 +4,7 @@ Web Sockets provide a long-lived connection between a client and a server over w
 
 Visit the following resources to learn more:
 
+- [@article@WebSocket vs. HTTP: Which protocol should you use?](https://roadmap.sh/network-engineer/websocket-vs-http)
 - [@article@The WebSocket API (WebSockets)](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API)
 - [@article@What are Web Sockets?](https://www.pubnub.com/guides/websockets/)
 - [@video@How Web Sockets Work](https://www.youtube.com/watch?v=pnj3Jbho5Ck)