Translator Words App on Javascript
summary
A production translator-words app is implemented with React + Node + GraphQL (Apollo), Mongoose/MongoDB and Docker, deployed across MongoDB on AWS with three instances (client, server, DB). Server uses Koa, resolvers/mutations/queries, auth via tokens in context; client uses Apollo Client with fragments, HTTP/auth links, caching and relay-style pagination. CI (CircleCI), PM2, and email delivery are wired in. The prototype finishes in ≈3 months, costing $65–70/month.
AI-written summary · about
chapters (17)
- 0:00Translator Words App intro
- 1:01Project origin and goals
- 3:32Node.js and React choice
- 6:45Node.js server with MongoDB
- 9:37Apollo Server config
- 11:43Database models and schema
- 13:10Resolvers and GraphQL queries
- 16:49GraphQL schema and client
- 17:53React setup and Apollo Client
- 21:07State management structure
- 24:20Context provider and state
- 25:23Atomic components structure
- 27:09GraphQL fragments in React
- 28:59Tool selection advice
- 31:53Deployment considerations
- 33:19Cost and timeline
- 34:02Conclusion and Q&A
related talks
28mA Real-World GraphQL Application in Production
58mCrafting compelling real-time web experiences with GraphQL and React
34mA real-world Relay application in production
47mReact, Relay and GraphQL — a perfectly normal component approach
24mModern Apollo Client React
41mReasonML: React as a Language and what the Future looks like
38mBuilding Isomorphic Web Applications with React
52mBuilding a Realtime Chat with GraphQL Subscriptions