Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Hands-on JavaScript for Python Developers

You're reading from   Hands-on JavaScript for Python Developers Leverage your Python knowledge to quickly learn JavaScript and advance your web development career

Arrow left icon
Product type Paperback
Published in Sep 2020
Publisher Packt
ISBN-13 9781838648121
Length 410 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Sonyl Nagale Sonyl Nagale
Author Profile Icon Sonyl Nagale
Sonyl Nagale
Arrow right icon
View More author details
Toc

Table of Contents (26) Chapters Close

Preface 1. Section 1 - What is JavaScript? What is it not?
2. The Entrance of JavaScript into Mainstream Programming FREE CHAPTER 3. Can We Use JavaScript Server-Side? Sure! 4. Nitty-Gritty Grammar 5. Data and Your Friend, JSON 6. Section 2 - Using JavaScript on the Front-End
7. Hello World! and Beyond: Your First Application 8. The Document Object Model (DOM) 9. Events, Event-Driven Design, and APIs 10. Working with Frameworks and Libraries 11. Deciphering Error Messages and Performance Leaks 12. JavaScript, Ruler of the Frontend 13. Section 3 - The Back-End: Node.js vs. Python
14. What Is Node.js? 15. Node.js versus Python 16. Using Express 17. React with Django 18. Combining Node.js with the Frontend 19. Enter Webpack 20. Section 4 - Communicating with Databases
21. Security and Keys 22. Node.js and MongoDB 23. Putting It All Together 24. Assessments 25. Other Books You May Enjoy

Models, views, and controllers

The Model-View-Controller (MVC) paradigm is what we're using here within Express. While not really necessary in Express, I find the logical separation of concerns is useful and easier to work with than monolithic types of undifferentiated files. Before we go too far, I will mention that MVC could be considered an outdated pattern, as it does create some additional dependencies between layers. With that being said, the ideas behind an architectural paradigm that separates logic into discrete actors are sound in MVC. You may hear MV* used instead, which basically should be read as "model, view, and whatever that binds them together." MV* is more popularly used these days in certain frameworks.

The MVC construction separates the logic of the program into three parts:

  1. Models deal with data interaction.
  2. Views handle the presentation layer.
  3. Controllers handle data manipulation and serve as the glue between the models and the views.

Here's...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Banner background image