Frontend: React + Apollo Client + Netlify
Backend: Typescript + Node.js + Apollo Server (graphql-yoga) + Graphcool/Prisma + Apex Up to deploy to AWS Lambda + AWS RDS
31–40 of 58 posts
Frontend: React + Apollo Client + Netlify
Backend: Typescript + Node.js + Apollo Server (graphql-yoga) + Graphcool/Prisma + Apex Up to deploy to AWS Lambda + AWS RDS
I've worked on pure PHP, Flask, Pyramid, Django, Laravel stacks, and I haven't warmed up to any of those. I'm in the vocal minority that says Django made me hate Python.
So here's my stack for 2018: Elixir+Phoenix on the backend, GraphQL as API protocol, React (and Typescript?) on the frontend.
Functional and immutable language on the backend + functionally-inspired data flow on the front end? Yes, please.
Now, if I could have monadic constructs and better typing on Elixir I'd be in heaven.
I’ll throw a hat in the ring for WebGL+WebAssembly and x86 assembly on the server
What does the app do?
Also go through https://www.tipsindeed.net
However, if you don't know any programming languages and plan to do "just" web development, WAMP and MEAN stack is the way to go.
edit: WAMP -> (XAMP)
Cheap, "fresh", and scalable in complexity with too many services to mention.
It's easy, plenty of example code available and will get your feet wet in the hyped secdevops which might land you a nice project sooner or later.
- It depends on what you are trying to build. Basic web app can be anything from a Trello clone to Instagram. Each has it's own limitations.
- Go with what is tried and tested. Pick up something that is supported, where if you get stuck you can reach out to people for a fix. One of the few good things of the clusterfk that the current JS ecosystem is is that many many amazing developers who are extremely responsive to questions are part of it. That makes life just a little bit easier.
- Use what you are comfortable with. Prefer a proper backend and frontend? Go for it. Everything in NodeJS is your cup of tea? Works just fine. In the end happy developer = productive developer. Just because assembly is 1000 times faster than Python does not mean you should code in assembly. Pick your tradeoffs.