Слайд 2

Leonid Nord Software Engineer Mail: leonid_nord@epam.com

Leonid Nord
Software Engineer
Mail: leonid_nord@epam.com

Слайд 3

Regulations 6 lectures 3 homework assignments Questions anytime Initiative and involvement

Regulations

6 lectures
3 homework assignments
Questions anytime
Initiative and involvement (Write to chat

or raise your hand)
Слайд 4

Module overview Node.js Intro, NPM, standard libraries; Express.js framework; Authorization, Authentication;

Module overview

Node.js Intro, NPM, standard libraries;
Express.js framework;
Authorization, Authentication;
Homework assignment №1;
Databases,

MongoDB;
Advanced MongoDB;
Building APIs, REST API, MVC;
Homework assignment №2;
Deploy, Docker;
Testing, code quality;
Files, Streams, 3rd party services, Email;
Socket.IO;
Homework assignment №3.
Слайд 5

Agenda QA Modern WEB overview Web architecture, Http HTTP module Express.js QA

Agenda

QA
Modern WEB overview
Web architecture, Http
HTTP module
Express.js
QA

Слайд 6

Q & A

Q & A

Слайд 7

Client-server architecture Client/server architecture is a producer/ consumer computing architecture where

Client-server architecture

Client/server architecture is a producer/ consumer computing architecture where the

server acts as the producer and the client as a consumer.
The server houses and provides high-end, computing-intensive services to the client on demand.
These services can include application access, storage, file sharing, printer access and/or direct access to the server’s raw computing power.
Слайд 8

Client-server architecture Client/server architecture works when the client computer sends a

Client-server architecture

Client/server architecture works when the client computer sends a resource

or process request to the server over the network connection, which is then processed and delivered to the client.
A server computer can manage several clients simultaneously, whereas one client can be connected to several servers at a time, each providing a different set of services.
In its simplest form, the internet is also based on client/server architecture where web servers serve many simultaneous users with website data.
Слайд 9

Modern web applications

Modern web applications

Слайд 10

MPA vs SPA

MPA vs SPA

Слайд 11

MPA vs SPA

MPA vs SPA

Слайд 12

HTTP The Hypertext Transfer Protocol (HTTP) is an application-level protocol for

HTTP

The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed,

collaborative, hypermedia information systems.
This is the foundation for data communication for the World Wide Web (i.e. internet) since 1990.
HTTP is a generic and stateless protocol which can be used for other purposes as well using extensions of its request
Слайд 13

URI and URL Uniform Resource Identifier AND Uniform Resource Locator (Browser)

URI and URL

Uniform Resource Identifier AND Uniform Resource Locator (Browser)

A

Uniform Resource Identifier (URI) provides a simple and extensible means for identifying a resource (straight from RFC 3986). It’s just an identifier; don’t overthink it.

A URI is an identifier.

A URL is an identifier that tells you how to get to it.

Слайд 14

Mime types .css - text/css .csv - text/csv .gif - image/gif

Mime types

.css - text/css
.csv - text/csv
.gif - image/gif
.html

- text/html
.js - text/javascript
.json - application/json
.txt - text/plain
.xml - application/xml Url encoded - application/x-www-form-urlencoded
Слайд 15

Слайд 16

Слайд 17

Слайд 18

Слайд 19

Слайд 20

Слайд 21

Слайд 22

Слайд 23

Слайд 24

Слайд 25

Слайд 26

Слайд 27

Слайд 28

Слайд 29

Слайд 30

Слайд 31

Слайд 32

Слайд 33

Q & A

Q & A