Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

REST API vs WebSocket REST API: - Request–Response model - Client sends request → Server sends response - Stateless (each request is independent) - Best for CRUD operations - Uses HTTP/HTTPS • Example: Fetching user data, submitting forms WebSocket: - Real-time two-way communication - Persistent, full-duplex connection - Stateful...

77,408 Aufrufe • vor 3 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

🔥 🚀 Not All #APIs are Built the Same❗️ 🎯⚡ What are the 🔝6️⃣ Game-changing API Architectures Every #Tech Professional Must Know❓ 🟢 𝗠𝗤𝗧𝗧 (Message Queuing Telemetry Transport) ↳ Best for ➡️ IoT applications ↳ Why❓ Lightweight, designed for low-bandwidth devices. Its publish-subscribe model is perfect for sensor-based systems. 🟣 𝗦𝗢𝗔𝗣 (Simple Object Access Protocol) ↳ Best for ➡️ High-security, enterprise applications ↳ Why❓ XML-based, strict security standards, great for banking & healthcare requiring ACID compliance. 🔵 𝗴𝗥𝗣𝗖 (Google Remote Procedure Call) ↳ Best for ➡️ High-performance, low-latency distributed systems ↳ Why❓ Uses HTTP/2 & Protobufs for faster data transmission. Supports bidirectional streaming—perfect for microservices & mobile apps. 🔴 𝗪𝗲𝗯𝗦𝗼𝗰𝗸𝗲𝘁𝘀 ↳ Best for ➡️ Real-time applications (gaming, chat, live notifications) ↳ Why❓ Enables persistent, two-way communication with ultra-low latency for high-interactivity apps. 🟠𝗚𝗿𝗮𝗽𝗵𝗤𝗟 ↳ Best for ➡️ Flexible, efficient data fetching ↳ Why❓ Clients request only the needed data—no more, no less. Reduces over-fetching & under-fetching, ideal for complex front-end apps. 🟡 𝗥𝗘𝗦𝗧 (Representational State Transfer) ↳ Best for ➡️ Simple, resource-oriented applications ↳ Why❓ Stateless, follows HTTP methods (GET, POST, PUT, DELETE), making it easy to implement & scalable for CRUD operations. ⚡ 𝗪𝗵𝗲𝗻 𝘁𝗼 𝗨𝘀𝗲 𝗪𝗵𝗮𝘁❓ ✅ MQTT → IoT & connected devices ✅ SOAP → Secure, enterprise-grade systems ✅ gRPC → Microservices & real-time communication ✅ WebSockets → Live, interactive applications ✅ GraphQL → Dynamic queries & front-end flexibility ✅ REST → General-purpose web apps 💡 Choosing the right API isn’t just technical ↳ It’s strategic ❗️ The right choice unlocks better performance, enhanced DX & future-proofing. #APIs #Tech Eveline Ruehlin Knut Jägersberg Tyson Lester, MBA, ChHC®, REBC®, RHU® Glen Gilmore Chidambara .ML. Jean CAYEUX 🇫🇷 Olivier Laborde#CES2025 #Peace 🇫🇷🇪🇺🇺🇦 Tony Moroney Dr. Marcell Vollmer 🇺🇦 #StaySafe #CES2025 Nicolas Babin Jean CAYEUX 🇫🇷 Lionel Costes Pinna Pierre Pierre Cappelli 🌏 Pierre Chamard Mack Jérôme MONANGE  Fabrizio Bustamante Mario Dr. Theophano Mitsa ☦️🇬🇷🇺🇸 Dr Stephen Harwood #Tech4Good #SDG🇺🇦#CES2025 Eric Gaubert Anthony Rochand Andrew Neff Nick Bilodeau Sharon Boxer Smaksked Skåne AB 🌐smaksked.bsky.social Dev Khanna @LavaletteAstrid Elitsa Krumova Andres Vilariño 🇪🇦 Franco Ronconi 🇮🇹 LoFrano 🇧🇷 Greg Valancius Heinz V. Hoenen 🌻 BusinessIntelligence Dinis Guarda @fogle_shane Françoise Morvan Nafis Alam MHcommunicate #Mastodon👉@mhcommunicate@social Adel Al Ammadi Jean-Baptiste Lefevre Eduardo Valente Dr.Philippe Vynckier, CISSP - Influencer 🇺🇦 Bruce E. Bailey, CRM/FED (Retired) Anand Narang JC Gaillard

Dr. Khulood Almani | د.خلود المانع

117,178 Aufrufe • vor 1 Jahr

While working on a new video with solutions to the previous one, I found ChatGPT's new UI struggles even more with concurrent updates: entries lose state and stick around for too long (see video). If this was a LiveView app, we would be getting so much flak.😅 --- I believe part of the problem here is having separate mutate and fetch requests on every deletion. The first fetch is cancelled when the second one comes up, causing items to stick around for longer. Many said yesterday that you could do the mutation and fetch as a single request, but that leads to other problems, such zombie entries. For example, imagine you delete link1 and link2 within a brief period of time. There is no guarantee the deletion order in the database will match the order the client receives the response, so you may end up with this: 1. (client) request to delete link1 sent 2. (client) request to delete link2 sent 3. (server) deletes link1 and loads a new list (includes link2) 4. (server) deletes link2 and loads a new list (no link1 or link2) 5. (client) receives link2 response 6. (client) receives link1 response So if you choose to use the latest response (link1), you brought link2 back to life. If you say you will use the response from the last request, events 3-4 can be swapped, and now you bring link1 back to life. Another way to solve this is by basically not allowing concurrent requests at all but that can affect the user experience drastically in other ways. Next week I should publish a video explaining how LiveView tackles this. Stay tuned!

José Valim

22,976 Aufrufe • vor 1 Jahr