91.2K
COGraphQL explained by cats 🐈💻. #graphql #cat #software #developer #coding
@coding.kitty
#Graphql
Regardez 91K vidéos Reels sur Graphql de personnes du monde entier.
Regardez anonymement sans vous connecter.
91K posts
NewTrendingViral
Recherches Associées
25Reels en Tendance
(12)
31.2K
SAGraphQL clearly explained 🤯
Guys! GraphQL is a query language and runtime for APIs that lets clients request exactly the data they need. Instead of multiple endpoints, it typically uses a single endpoint where clients define the structure of the response. This reduces over-fetching and under-fetching compared to traditional REST APIs. And that’s literally it😁
Follow for more 🤝
#softwareengineering #computerscience
@sayed.developer
78.7K
THComment “blog” & I’ll share the blog link & my notes with you in your DM 🤝🏻
(Make sure to follow else automation won’t work)
Topic: GraphQL API
Save for your future interviews 📩
#dsa #systemdesign #tech #coding #codinglife #restapi #webdev #api #graphql
[dsa, system design, GraphQL API, REST API, tech]
@thatcodergirlie
2.0K
WO✨ #NewEpisodeAlert✨ Tune into this week’s #WomenWhoCode #TalksTech #Podcast with special guest, Nancy Crandall, Digital Dev Engineer III at CVS Health, as she shares about the fundamentals of #GraphQL and expanding full-stack capabilities when pairing #React on the frontend.
🔗 Visit the link to listen now: www.womenwhocode.com/podcast
#WomenInTech
#WWCode
@womenwhocode
144.6K
ARWhy do people hate GraphQL
(I’m people). There might be a time and a place for graphQL, but I haven’t seen it yet. It introduces additional complexity and makes debugging and logging 10x worse. #graphql #csmajors #apis #systemdesign #coding
@arjay_the_dev
16.3K
COREST has powered the web for years.
GraphQL changed how data is fetched, not how backend is built.
Here’s the real difference 👇
🔹 REST
Multiple endpoints
Fixed response structure
Simple, predictable, cache-friendly
Best for CRUD-heavy and stable APIs
🔹 GraphQL
Single endpoint
Client asks exactly what it needs
No over-fetching or under-fetching
Perfect for complex UIs and fast-moving frontends
💡 Industry truth:
Big companies use both.
REST for internal services and simple flows.
GraphQL as an aggregation layer for frontend teams.
Choosing one blindly is a mistake.
Knowing WHEN to use WHAT is a skill.
Save this.
Share this.
Think like a system designer, not a framework fan.
#GraphQL #RESTAPI #APIs #SystemDesign #BackendDevelopment FrontendDevelopment FullStackDeveloper SoftwareEngineering WebDevelopment TechCareers Developers Programming LearnTech
@codewithupasana
7.7K
MODo you know how to connect your applications to MongoDB Atlas? Check out 5 different methods! 👇
⚡️ MongoDB Language Driver
⚡️ HTTPS Endpoints
⚡️ Serverless Function
⚡️ GraphQL Endpoints
⚡️ MongoDB Web SDK
Get started today by visiting the 🔗 link in bio.
@mongodb
81.1K
DEpart-7, graphql vs rest
frontend system design
#frontend #codinglife #systemdesign #leetcode #javascript
@dev.nd.drive
115.7K
MIThe less you hit the database, the faster your app feels.
Unlock 200+ practical problem-solutions just like this one in the Ebook. Link in bio
Here are smart ways to reduce DB calls 👇
1️⃣ Use JOINs to fetch everything at once
Instead of separate queries for user + posts + stats, pull them together in one joined query.
⸻
2️⃣ Batch-fetch instead of looping queries
Instead of hitting the DB 10 times for 10 product IDs, get them all using one bulk SELECT (IN clause).
⸻
3️⃣ Cache data that doesn’t change often
Don’t fetch homepage sections on every request — load trending posts, categories, or banners from Redis.
⸻
4️⃣ Pre-compute expensive data in background jobs
If computing likes count, comments count, followers count takes time, let a worker update it once, not per request.
⸻
5️⃣ Use materialized views for complex calculations
If your homepage needs analytics like top creators, top-selling products, let the DB store a ready-made snapshot.
⸻
6️⃣ Denormalize data that’s read constantly
Instead of joining users + profiles + settings each time, store key fields together for faster reads.
⸻
7️⃣ Move heavy reads to read replicas
If your feed page triggers thousands of reads, send them to replicas, keeping the main DB free for writes.
⸻
8️⃣ Cache API responses at the edge (CDN)
If thousands of people load the same homepage, serve it from Cloudflare/Edge — no DB hit at all.
⸻
9️⃣ Use GraphQL to avoid multiple endpoints
Instead of calling 5 different APIs (user, posts, comments, stats, settings), let GraphQL return exactly what you need in a single query.
#systemdesign #backenddevelopment #backendengineer #webperformance
#databaseoptimization #scalablesystems #highperformanceapps #softwarearchitecture
#programmingtips #techreels #techinstagram #learnsystemdesign #mission_compile
#restapi #graphql #mysql #nosql #engineeringtips #devcommunity
(database optimization, reduce db queries, backend performance, query optimization techniques, system design for beginners, high performance backend, graphql vs rest, caching strategies, backend scaling tips, database joins)
@mission_compile
130.2K
TEWe’ve all heard the term API before, but what does it mean? Why are there so many different types, and what do they all do?
This video seeks to answer those question by diving a little bit deeper into what things like GraphQL, RESTful APIs, Websockets, and Webhooks do.
APIs are extremely important, so it’s crucial to have a high level understanding, so during implementation you know which would be best suited for your needs.
Hopefully this helps you in your journey ✨😊
#computersciencestudent #softwareengineer #careerintech #cs #api
@tembrasdev
55.8K
CHBelow are the Backend system design concepts that we should know💯👇
Comment ‘link’ to get this list.
Learning these backend concepts will help you guys to understand the system designs easily.
Core Concepts
1. What is an API
2. REST vs GraphQL
3. HTTP methods (GET, POST etc)
4. HTTP status codes (2xx, 4xx etc)
5. Stateless vs Stateful APIs
6. Authentication vs Authorization
7. Session-based auth vs JWT
8. OAuth 2.0
9. Rate limiting vs Throttling
10. Idempotency (especially for payments)
⸻
Databases & Data Handling
11. SQL vs NoSQL — when to use what
12. Indexes and how they speed up queries
13. ACID properties
14. Transactions & isolation levels
15. Database normalization vs denormalization
16. Pagination (offset vs cursor-based)
17. Sharding & partitioning
18. Read replicas & write scaling
19. Handling duplicate records
20. Optimistic vs pessimistic locking
⸻
Caching & Performance
21. What is caching and where to cache
22. Cache eviction strategies (TTL, LRU)
23. Cache consistency & stale cache problems
24. CDN and edge caching
25. Why cache can make systems wrong
⸻
Distributed Systems & Scaling
26. Load balancing (round-robin, least connections, hashing)
27. Horizontal vs vertical scaling
28. Microservices vs monoliths (trade-offs)
29. Service-to-service communication (sync vs async)
30. Message queues (Kafka, RabbitMQ, SQS)
⸻
Reliability & Real-World Problems
31. Exactly-once vs at-least-once processing
32. Retries, timeouts, and circuit breakers
33. Handling race conditions
34. Distributed locking
35. Event-driven architecture
36. Saga pattern (distributed transactions)
37. Graceful degradation
38. Observability (logs, metrics, tracing)
39. Deployments (blue-green, rolling)
40. Handling traffic spikes & viral load
#SystemDesign #tech #backenddeveloper #interview #dailypost
(backend interview preparation, system design concepts, software engineering interviews, Roadmap, interviews, career, growth)
@chhavi_maheshwari_
2.1K
EN🔍 Discover the power of the new Enjin Platform's Comprehensive Documentation. Our API offers robust built-in docs, GraphQL playground, config guides, examples, & a handy cheat sheet. Unleash your project's true potential with Enjin! 💪
Explore docs.enjin.io now. 📚
@enjin
✨ Guide de Découverte #Graphql
Instagram héberge 91K publications sous #Graphql, créant l'un des écosystèmes visuels les plus dynamiques de la plateforme.
Découvrez le dernier contenu #Graphql sans vous connecter. Les reels les plus impressionnants sous ce tag, notamment de @arjay_the_dev, @tembrasdev and @mission_compile, attirent une attention massive.
Qu'est-ce qui est tendance dans #Graphql ? Les vidéos Reels les plus regardées et le contenu viral sont présentés ci-dessus.
Catégories Populaires
📹 Tendances Vidéo: Découvrez les derniers Reels et vidéos virales
📈 Stratégie de Hashtag: Explorez les options de hashtags tendance pour votre contenu
🌟 Créateurs en Vedette: @arjay_the_dev, @tembrasdev, @mission_compile et d'autres mènent la communauté
Questions Fréquentes Sur #Graphql
Avec Pictame, vous pouvez parcourir tous les reels et vidéos #Graphql sans vous connecter à Instagram. Aucun compte requis et votre activité reste privée.
Analyse de Performance
Analyse de 12 reels
💡 Posts top moyennent 120.4K vues (1.9x au-dessus moyenne)
Publiez régulièrement 3-5x/semaine aux heures actives
Conseils de Création de Contenu et Stratégie
💡 Le meilleur contenu obtient plus de 10K vues - concentrez-vous sur les 3 premières secondes
📹 Les vidéos verticales de haute qualité (9:16) fonctionnent mieux pour #Graphql - utilisez un bon éclairage et un son clair
✨ Beaucoup de créateurs vérifiés sont actifs (50%) - étudiez leur style de contenu
✍️ Légendes détaillées avec histoire fonctionnent bien - longueur moyenne 626 caractères
Recherches Populaires Liées à #Graphql
🎬Pour les Amateurs de Vidéo
Graphql ReelsRegarder Graphql Vidéos
📈Pour les Chercheurs de Stratégie
Graphql Hashtags TendanceMeilleurs Graphql Hashtags
🌟Explorer Plus
Explorer Graphql#apollo graphql#graphql vs rest#rest vs graphql#msw graphql support#graphql news#strawberry shake compatibility with graphql servers#what is graphql#restful api vs graphql