91.2K
COGraphQL explained by cats 🐈💻. #graphql #cat #software #developer #coding
@coding.kitty
#Graphql
世界中の人々によるGraphqlに関する91K件のリール動画を視聴。
ログインせずに匿名で視聴。
91K posts
NewTrendingViral
関連検索
25トレンドリール
(12)
31.4K
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.8K
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
132.4K
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.9K
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
✨ #Graphql発見ガイド
Instagramには#Graphqlの下に91K件の投稿があり、プラットフォームで最も活気のあるビジュアルエコシステムの1つを作り出しています。
#Graphqlは現在、Instagram で最も注目を集めているトレンドの1つです。このカテゴリーには91K以上の投稿があり、@arjay_the_dev, @tembrasdev and @mission_compileのようなクリエイターがバイラルコンテンツでリードしています。Pictameでこれらの人気動画を匿名で閲覧できます。
#Graphqlで何がトレンドですか？最も視聴されたReels動画とバイラルコンテンツが上部に掲載されています。
人気カテゴリー
📹 ビデオトレンド: 最新のReelsとバイラル動画を発見
📈 ハッシュタグ戦略: コンテンツのトレンドハッシュタグオプションを探索
🌟 注目のクリエイター: @arjay_the_dev, @tembrasdev, @mission_compileなどがコミュニティをリード
#Graphqlについてのよくある質問
Pictameを使用すれば、Instagramにログインせずに#Graphqlのすべてのリールと動画を閲覧できます。あなたの視聴活動は完全にプライベートです。ハッシュタグを検索して、トレンドコンテンツをすぐに探索開始できます。
パフォーマンス分析
12リールの分析
💡 トップ投稿は平均121.0K回の再生（平均の1.9倍）
週3-5回、活動時間に定期的に投稿
コンテンツ作成のヒントと戦略
🔥 #Graphqlは着実な成長を示す - 一貫して投稿してプレゼンスを構築
✍️ ストーリー性のある詳細なキャプションが効果的 - 平均長626文字
✨ 多くの認証済みクリエイターが活動中（50%） - コンテンツスタイルを研究
📹 #Graphqlには高品質な縦型動画（9:16）が最適 - 良い照明とクリアな音声を使用
#Graphql に関連する人気検索
🎬動画愛好家向け
Graphql ReelsGraphql動画を見る
📈戦略探求者向け
Graphqlトレンドハッシュタグ最高のGraphqlハッシュタグ
🌟もっと探索
Graphqlを探索#rest vs graphql#graphql vs rest#msw graphql support#graphql news#strawberry shake compatibility with graphql servers#restful api vs graphql#graphql vs rest api#magezine graphql tutorials on youtube