6.1 Conclusion

Hi folks, thanks for sticking with me till the end of the course. We've covered a lot of ground in this course, and depending on your background, that may have included a lot of new techniques that you may not have used before. Certainly, if you're coming from front end development. As we have seen however, Sails shield us from a lot of the complexity that goes into making a fully featured app composed of a four stack JavaScript back and front end. And that has a lot of features and functionality, which can be used with simple configuration rather than hard programming. Sails has allowed us to quickly and easily create the models that our app uses to work with data in our application, including event data and user data, and abstracts away the pain of working with a database directly. It has also allowed us to rapidly build the front-end while working with sample API data. And then for us to switch effortlessly back to the back-end to build the rest of our app. We were able to very easily set up and enforce authentication, so that any registered users could sign in and view the dashboard. There's still a lot of Sails JS that we haven't needed to use or haven't had time to cover, and there's still much more that we could do to improve our app. As a challenge, why not see if you can use Sails' built-in real-time capabilities by enabling the dashboard to update the chart using socket.io whenever new events are received by the app. Don't worry if you haven't followed along with the coding. You can download the complete source code from GitHub. Just clone the repo, run an NPM install and you should be good to go. My name is Dan Wellman and from all of us here at Tuts+, thanks for watching.