UPDATE: The entire course was updated to use React Hooks, Async/Await and better overall code. Integrating React with our backend in an elegant way, creating a great workflowīuilding our frontend to work with the APIĬreating reducers and actions for our resourcesĬreating many container components that integrate with ReduxĬreating a build script, securing our keys and deploy to Heroku using Git Protecting routes/endpoints with JWT (JSON Web Tokens) This course includes.īuilding an extensive backend API with Node.js & Express We will start with a blank text editor and end with a deployed full-stack application. In this course, we will build an in-depth full-stack social network application using Node.js, Express, React, Redux and MongoDB along with ES6+. I'd say keep your options open! Learn things outside the JavaScript bubble.Welcome to "MERN Stack Front To Back". Likewise, mongo might be a stellar choice if you need really high throughput, but if you're writing an ecommerce engine, you probably want the ACID guarantees that come with a relational database.
However, if you're building a Kanban app, React or Angular are probably great choices, as maintaining an app that does that in vanilla JS is going to be expensive and error-prone. Blindly picking one stack as best is doing a disservice to your customers.įor example, there's no need to force your users to download react and waste battery life to read a personal blog that's updated once or twice a week. Weighing those is part of being a responsible developer. Every element of your stack comes with pros and cons. Second, engineering is largely about making tradeoffs. Static site generators (whether it's Gatsby or something like Jekyll, that foregoes a JS framework).I think this misses out on a lot of other important aspects, such as: Regarding best or worst, I don't think there is a best here, at all.įirst off, all of these are essentially the same: a NoSQL database, a node JS backend, and either Angular or React on the frontend. Google owns enough of your things already. I really hope firebase isn't taking over. Okay, so perhaps a bit of a rant answer, but:
0 kommentar(er)
