Download "REST API простыми словами. Что такое REST API? | 2022"

"videoThumbnail REST API простыми словами. Что такое REST API? | 2022

0:00

Что такое REST API

1:08

Client-Server

1:30

Stateless

2:10

Cache

2:33

Uniform Interface

2:55

Identification of resources

3:27

Manipulation of resources through representations

3:54

Self-descriptive messages

4:37

Hypermedia as the engine of application state

5:24

Layered System

6:20

Code on Demand

Разбираем микросервис APIGateway на Golang . Учимся разрабатывать на примере реального проекта

Разбираем микросервис APIGateway на Golang . Учимся разрабатывать на примере реального проекта

Channel: The Art of Development

HTTP протокол в 1С для начинающих. Restful api. Postman. Fiddler. БЛОК 1

HTTP протокол в 1С для начинающих. Restful api. Postman. Fiddler. БЛОК 1

Channel: nizamov school

O que é uma API REST? Entenda tudo sobre API, HTTP e RESTful,

O que é uma API REST? Entenda tudo sobre API, HTTP e RESTful,

Channel: Matheus Battisti - Hora de Codar

Самый простой API сервер на PHP

Самый простой API сервер на PHP

Channel: АйТиШтучки

Бекенд на Django, Урок 8: Annotate и агрегация

Бекенд на Django, Урок 8: Annotate и агрегация

Channel: Senior Pomidor Developer

Build a Blog with Next.js and a Headless CMS (Strapi)

Build a Blog with Next.js and a Headless CMS (Strapi)

Channel: NL Tech

Java Spring Boot - Web Service 5: Security CORS configuration - Allow All

Java Spring Boot - Web Service 5: Security CORS configuration - Allow All

Channel: CodeForgeYT

HTTPS для тестировщика. Вопросы с собеседований для QA (API, статус коды, методы)

HTTPS для тестировщика. Вопросы с собеседований для QA (API, статус коды, методы)

Channel: QA Tech

50 - React JS практика - REST API (краткая теория)

50 - React JS практика - REST API (краткая теория)

Channel: IT-KAMASUTRA

APIs Explained | Real World Examples

APIs Explained | Real World Examples

Channel: CertBros

newizze

ньювиз

application programming interface

api простыми словами

rest api

что такое rest api

что такое api

что такое апи

что такое rest api простыми словами

что такое rest api для чайников

rest

api

rest api что это

что такое rest

что такое rest api? просто и понятно

rest api на пальцах

academy nwz

академия нвз

00:00:00

I know why you don’t understand the term

00:00:02

rest API everything I’ve read and heard on

00:00:04

this topic in Russian is complete My

00:00:07

name is holy now everything is fine I’ll explain the

00:00:11

term rest API consists of two parts The

00:00:13

concept API we already know is an interface

00:00:16

for the interaction of two programs with

00:00:17

each other more details I have already talked about it,

00:00:19

but the rest prefix indicates a

00:00:21

specific style. I often see

00:00:24

people mistakenly considering rest to be a standard

00:00:26

or, even worse, a protocol. But this is not the case.

00:00:28

The term rest introduced the role of fielding, his

00:00:30

dissertations on architectural styles on

00:00:32

the network, he describes the test as an architectural

00:00:35

style for distributed hypermedia

00:00:37

systems or humanly for complex

00:00:39

Internet services in the dissertation roi

00:00:41

reflected on how

00:00:43

the Internet developed and what it came to in one of the

00:00:46

chapters he outlined architectural principles

00:00:48

that have the sole goal of

00:00:50

unification and standardization of communication

00:00:52

between computers within a network, this is important

00:00:55

if we we want to build a system that

00:00:57

will be easy to scale and

00:00:59

maintain, agree it’s convenient when we

00:01:01

can disconnect one element like a

00:01:03

Lego cube and put a completely different one in its place

00:01:05

and this whole structure will continue

00:01:08

to work. The rest is a hybrid created on the

00:01:10

basis of three bottom styles that

00:01:12

complement each other but they are

00:01:14

all based on separating the client from the server with

00:01:17

client-server architecture, we are already

00:01:19

familiar from this video and we know that with

00:01:21

this architecture we split our

00:01:23

application into 2 into a client with a user

00:01:26

interface and a server with business logic and a

00:01:28

database from 2 architectural styles,

00:01:31

we will borrow the absence of recording the

00:01:33

state of clients in other words,

00:01:35

the server should not remember what

00:01:37

requests the Client has already made and what

00:01:39

state it is in now; each

00:01:41

new request should be formed as if the

00:01:43

client and the server had not

00:01:46

communicated before and this is their first contact.

00:01:47

Let’s imagine that we have a list of all

00:01:50

countries divided into pages on in the client,

00:01:52

we requested the first page and

00:01:54

rendered the entire necessary interface

00:01:56

to load the Next page, we

00:01:58

must clearly ask for page number

00:02:00

two, we cannot simply request the

00:02:02

Next page because the server does not

00:02:04

remember Which page was the

00:02:06

previous one, there are a lot of clients, and my

00:02:09

mother’s server has one beautiful one, but the list is not that great

00:02:11

the truth changes often, so rest

00:02:14

borrowed from the third style

00:02:15

cacheability, the server marks its response

00:02:17

as cacheable and the client stores it

00:02:20

in its memory the next time when the

00:02:21

client needs this data, instead of

00:02:24

requesting the server, it will take it from

00:02:26

storage This allows you to reduce the total

00:02:28

number of requests reduce load on the

00:02:30

server and, accordingly, increase

00:02:31

the performance of the program, and now we

00:02:33

come to the most key principle rest,

00:02:36

which distinguishes the architectural

00:02:38

style from all others; by this principle, we

00:02:40

introduce restrictions due to which the

00:02:41

communication interface between the client and the

00:02:44

server becomes uniform. And this is

00:02:47

important if we still want to have

00:02:49

the ability to maintain and expand the

00:02:50

system without headaches this principle

00:02:53

is called interface unification the first

00:02:56

limitation is related to the identification of the

00:02:58

resource in the rest terminology the resource

00:03:00

can be anything html document

00:03:02

picture Or for example information on the lake the

00:03:05

most important thing is that each resource must have a

00:03:07

stable unique identifier or in

00:03:10

other words heaven is acceptable we have

00:03:12

articles in the database for the rest, this

00:03:15

entity will be a resource, which

00:03:16

means we need its identifier instead of

00:03:19

four different

00:03:20

uri, we must use one single one. And the

00:03:24

request method will be responsible for data manipulation and the following

00:03:27

limitation since the Client cannot

00:03:28

directly change the data, he must

00:03:30

provide the server with your vision of the data and

00:03:32

how it presents it, that is, instead of

00:03:35

telling you to change such and such a

00:03:37

field in some resource, we send the

00:03:39

changed resource as a whole, as if saying this is how

00:03:41

I would like to see it, and

00:03:44

the server decides whether to change it or not

00:03:46

independently, based on your own

00:03:48

conclusions and business logic, this

00:03:50

limitation is called

00:03:52

resource manipulation through representation; another

00:03:54

important limitation sounds like the

00:03:57

message itself being described; in general, from

00:03:59

the name it is clear that the message must

00:04:01

contain all the necessary

00:04:02

information in order to receive and understand and

00:04:05

interpret it there should not be a

00:04:06

situation when the first message

00:04:08

contains data and the second contains

00:04:10

instructions on how to interact with this data,

00:04:12

for example, when we

00:04:14

enter the browser line the address google.com

00:04:16

browser That is, the client sends

00:04:18

messages to the server with the following

00:04:20

content. So we tell the server that

00:04:22

we want to get the root resource of the site,

00:04:24

this information is enough so that the server

00:04:26

returns to us this message in response, the

00:04:28

server tells us that it understood the request

00:04:31

and successfully processed it, and it also gives

00:04:33

the client clear instructions on how

00:04:35

to interpret the further message. The

00:04:37

last fourth limitation is

00:04:39

hypermedia as an engine of

00:04:41

application state. Most likely you are familiar with the

00:04:43

concept of how a hypermedia hyperlink

00:04:46

can be present as a set of hyperlinks

00:04:48

and This can be either an html document

00:04:50

with links or a Jason object with a

00:04:52

list of available resources for the request. The

00:04:54

main idea of this limitation is

00:04:56

that the server should prompt the client

00:04:58

what next steps it can

00:05:00

take next, using the example of the

00:05:02

previous message, the server clearly

00:05:04

indicates to us what is next our request can

00:05:06

be Google Search with the Q parameter if the

00:05:08

user submits a form or Velcom

00:05:11

Help if the user clicks on the link

00:05:13

need Hub resource identifier

00:05:15

manipulation through presentation

00:05:17

self-describing messages and hypermedia

00:05:19

as a state engine together form the

00:05:21

principle of interface unification.

00:05:23

Most programmers would say that the

00:05:25

principles described above are sufficient and to

00:05:28

some extent we can agree with them,

00:05:29

but this is not the case when the

00:05:32

majority should be trusted because

00:05:34

we still have two more principles; the principle of a

00:05:36

multi-level system tells us that

00:05:39

in a system there can be not only

00:05:40

client and server levels; if we

00:05:43

consider the system as a whole, then it can

00:05:45

have any number of layers, say

00:05:47

between the client and the server there may

00:05:49

be an additional proxy layer

00:05:51

responsible for authorization. However, at

00:05:54

the macro level we still have a simple

00:05:56

client-server architecture and our

00:05:58

proxy server simply turns into a

00:06:00

server in the case when a client accesses it

00:06:02

and vice versa acts as

00:06:04

client roles when accessing the server

00:06:06

further in this way Despite the fact that

00:06:08

we may have dozens of layers in the system,

00:06:10

each component knows only about the

00:06:12

existence of the closest layer to it

00:06:14

by limiting knowledge about the system to just one

00:06:17

layer, we limit the overall complexity of

00:06:19

the system But providing code on

00:06:22

request is really considered an

00:06:23

optional principle, the server in response

00:06:25

can send code to the client for

00:06:27

direct execution, most often

00:06:29

these are pieces of JavaScript code that are

00:06:31

executed in the browser without any problems,

00:06:33

so the overall application code on the client

00:06:35

becomes more complex only if

00:06:37

necessary. If you see in Internet

00:06:39

articles that it is limited only to

00:06:41

resource identification Yes manipulation

00:06:43

through representation or does the

00:06:45

seventh principle appear there first from scratch, then you

00:06:48

should not trust such authors I have

00:06:50

prepared a small cheat sheet in which I

00:06:52

briefly described all six principles and

00:06:54

attached many examples Use

00:06:56

it so that your API can proudly be called

00:06:59

redfil Be sure to check out more videos

00:07:02

on our channel With you was holy See you later

00:07:06

[music]

Description:

REST API на самом деле проще чем кажется. Главное разобраться что же на самом деле такое REST API и что нужно делать чтобы написать полноценный RESTfull API. Шпаргалка REST: https://www.dropbox.com/scl/fi/iayqq2cp85gfzy3258v7k/REST.pdf?rlkey=ifurmqwtgyw8rtfajv761l0yq&dl=0 ⭐️ Бесплатная карьерная консультация https://calendly.com/tomfordrumm/free-20 Записывайся и мы обсудим, куда тебе двигаться дальше, разберем, почему не получается найти работу и как улучшить твое резюме, чтобы тебя приглашали на собеседования! 💡Мысли, опыт и уникальный контент в моем Телеграм канале - https://t.me/svyatamesto 💡Обсудить новые технологии, мемы и новости в сфере IT- https://t.me/+YKgMaur5pIZjZjBi 💡Найти идею для пет-проекта в нашем боте - https://t.me/hub_404_bot 💡Комьюнити нетоксичных айтишников - https://discord.com/invite/Maz5Qhvtwj 💡Тик-ток - https://www.tiktok.com/@svyatamesto 💡Нельзяграм - https://www.facebook.com/unsupportedbrowser ⚡️Поддержать меня: Boosty - https://boosty.to/svyat404 BTC - bc1q4tk6mjxptfdnvcmjahee7q29rh2v5p3uk996qc ETH - 0x2659229d760383AF3C9de3a90457Cd1B190AddFD TON - EQCBtx7lfTymSTlPfuWlZpikGDiJm1fq-7-kTEqYFgMm8WQH API - это просто: https://www.youtube.com/watch?v=vPVAYsc-U60 Клиент-Сервер: https://www.youtube.com/watch?v=JlTQujO6cbA Портфолио за 15 минут: https://www.youtube.com/watch?v=02tJITOqvDU 00:00 - Что такое REST API 01:08 - Client-Server 01:30 - Stateless 02:10 - Cache 02:33 - Uniform Interface 02:55 - Identification of resources 03:27 - Manipulation of resources through representations 03:54 - Self-descriptive messages 04:37 - Hypermedia as the engine of application state 05:24 - Layered System 06:20 - Code on Demand

Preparing download options

Popular

HD video

Only sound

All

* — If the video is playing in a new tab, go to it, then right-click on the video and select "Save video as..."

** — Link intended for online playback in specialized players

Questions about downloading video

How can I download "REST API простыми словами. Что такое REST API? | 2022" video?

http://unidownloader.com/ website is the best way to download a video or a separate audio track if you want to do without installing programs and extensions.
The UDL Helper extension is a convenient button that is seamlessly integrated into YouTube, Instagram and OK.ru sites for fast content download.
UDL Client program (for Windows) is the most powerful solution that supports more than 900 websites, social networks and video hosting sites, as well as any video quality that is available in the source.
UDL Lite is a really convenient way to access a website from your mobile device. With its help, you can easily download videos directly to your smartphone.

Which format of "REST API простыми словами. Что такое REST API? | 2022" video should I choose?

The best quality formats are FullHD (1080p), 2K (1440p), 4K (2160p) and 8K (4320p). The higher the resolution of your screen, the higher the video quality should be. However, there are other factors to consider: download speed, amount of free space, and device performance during playback.

Why does my computer freeze when loading a "REST API простыми словами. Что такое REST API? | 2022" video?

The browser/computer should not freeze completely! If this happens, please report it with a link to the video. Sometimes videos cannot be downloaded directly in a suitable format, so we have added the ability to convert the file to the desired format. In some cases, this process may actively use computer resources.

How can I download "REST API простыми словами. Что такое REST API? | 2022" video to my phone?

You can download a video to your smartphone using the website or the PWA application UDL Lite. It is also possible to send a download link via QR code using the UDL Helper extension.

How can I download an audio track (music) to MP3 "REST API простыми словами. Что такое REST API? | 2022"?

The most convenient way is to use the UDL Client program, which supports converting video to MP3 format. In some cases, MP3 can also be downloaded through the UDL Helper extension.

How can I save a frame from a video "REST API простыми словами. Что такое REST API? | 2022"?

This feature is available in the UDL Helper extension. Make sure that "Show the video snapshot button" is checked in the settings. A camera icon should appear in the lower right corner of the player to the left of the "Settings" icon. When you click on it, the current frame from the video will be saved to your computer in JPEG format.

What's the price of all this stuff?

It costs nothing. Our services are absolutely free for all users. There are no PRO subscriptions, no restrictions on the number or maximum length of downloaded videos.