JPJuan Pablo Pailletinsimfinity-js.hashnode.dev·Sep 16 · 6 min readFrom a GraphQL schema to MCP tools with Simfinity.jsA GraphQL schema already describes argument types and result fields. That makes it a useful starting point for exposing an API through MCP. The remaining choices are concrete: which operations clients00
RRulestackinrulestack.hashnode.dev·Sep 16 · 9 min read8.5 hours unseen while every check was green: the Hashnode thread our poller never readOur feedback poller only ever read comments on our own Hashnode posts. A reply to a comment we had left on someone else's post sat unseen for eight and a half hours while every health check reported O00
JPJuan Pablo Pailletinsimfinity-js.hashnode.dev·Sep 16 · 4 min readFrom GraphQL types to a PostgreSQL API with Simfinity.jsA series catalog starts with a small domain: a serie has a name, and each season belongs to a serie. Even that model needs list queries, create/update/delete operations, relationship resolvers, valida00
DHDan Holloraningrimicorn.hashnode.dev·Sep 14 · 4 min readGraphQL @oneOf: Exactly One Input, Enforced by the SchemaEvery GraphQL schema I've worked on eventually grows a field that can be looked up more than one way. You want a user by ID, or by email, or by username. The type system has no way to say "exactly one00
JSJayesh Sojitrainjayesh-sojitra.hashnode.dev·Sep 7 · 3 min read Week 2 Recap: Architecture + ToolingDay 8 — Context API vs Redux vs Zustand: When to Use Each Context for low-frequency shared values. Zustand for global state without ceremony. Redux for complex, cross-cutting state that genuinely need00
TTISA-TECHintisa-tech.hashnode.dev·Sep 7 · 11 min readGraphQL vs REST API: Which Should You Learn First in 2026?If you are a student trying to break into backend or full stack development, you have probably run into this question at least once while scrolling through job postings or YouTube tutorials. Two acron00
JSJayesh Sojitrainjayesh-sojitra.hashnode.dev·Sep 4 · 3 min read REST vs GraphQL: A Practical Comparison REST vs GraphQL debates usually skip straight to "GraphQL is more flexible" without explaining what problem that flexibility is actually solving, or what it costs. Here's the practical version. The co00
ZZyVOPinzyvop.hashnode.dev·Aug 30 · 12 min readREST vs gRPC vs GraphQL in NestJS: What the Numbers Actually ShowComparisons of these three protocols tend to cite specific performance multipliers without saying much about what was actually measured. One recent writeup put gRPC's median latency at roughly a third00
PPPrajapati Pareshinsmarttechdevs.hashnode.dev·Aug 27 · 5 min readBackend Architecture: Master GraphQL FederationThe Monolithic Graph Bottleneck When engineering teams first adopt GraphQL, it feels like a revelation. The frontend can request exactly the data it needs, in a single network call, perfectly typed. H00
SAStefan Adolfinstadolf.hashnode.dev·Aug 25 · 9 min readYour subgraph only knows half the storyAlmost every serious dapp hits the same wall. You index your contracts, you get a clean GraphQL API, and querying chain state becomes genuinely pleasant: query { pools { id token0 token100
