[IT 5-Minute Dictionary] Assignment #06

https://ebook-product.kyobobook.co.kr/dig/epd/ebook/4801163034002

Why Internet Explorer disappeared and its browser engine
Oh, you're saying cookies aren't meant to be eaten?
front end, back end
Still don’t know what a server is?
Only super developers can do this. Full stack?
Does serverless mean there are no servers?

Episode 16. Why Internet Explorer disappeared and the browser engine

Development limited to web development is called ‘front-end web development’.

The core program of a web browser that allows expression according to developer standards is called a 'browser engine' or 'rendering engine'. Firefox uses gecko, Chrome uses blink, etc.

The more the latest technology is supported, the more up-to-date the browser becomes, so the performance of the engine directly determines the performance of the web browser.

Internet Explorer once had a high market share of 95%, but it began to be left behind as issues such as security were not resolved and it underwent late updates. And eventually, support was discontinued.

Microsoft Edge, which was announced later, is a browser that uses ‘Blink’, the engine of Chrome.

Episode 17. Oh, you're saying cookies aren't for eating?

Records kept on your computer by your browser when you visit certain websites

HTTP HyperText Transfer Protocol

A type of protocol for exchanging information between users and servers on the Internet

HTTP has the characteristic of being stateless. The server responds to the user's request, and when the connection is lost, it cannot remember who we are, and cookies are needed to compensate for this. When you connect to the server again, the server can receive cookies and perform functions such as maintaining login.

Cookies are limited to one domain.

Cookies are sent automatically.

Cookies are automatically stored on your computer.

For example, when you click the Facebook Like button on a blog, you are sending a request to Facebook, so Facebook may obtain a cookie from the blog.

Browser extensions every web developer must know

ColorZilla, Momentum, CSS Viewer, JSON Viewer

Episode 18. Front-end, back-end

front end

Screens used by users on the web or in applications

Given the rapid pace of technological change, developer fatigue can be high. (JavaScript fatigue)

Coding can be fun because you can see what is reflected immediately.

backend

Database, router, etc.

The speed of technological change is slower than front-end technology, so the development environment is stable, and the technology is diverse, so there are many options. This is because you can learn Python, C#, etc. instead of Java.

Because it is far from the user, it is difficult to receive recognition, so interest decreases.

In my case, it's the opposite. As a backend developer, it's more important that I did a good job myself, so I don't seem to be very interested in user recognition. The reflection part of the code does not seem to be a major problem as there are parts that can be inferred and confirmed numerically or through debugging. I would say that the front-end is more dramatic, but there are some things like that, but the back-end is also a field that has many advantages, so I think it will differ from person to person.

Episode 19. Still don’t know what a server is?

A server is just a computer

The server waits for address input 24 hours a day.

When an address is entered, the data corresponding to that address is pulled out and displayed.

Episode 20. Only super developers can do this. Full stack?

Full-stack refers to a person who can do everything from front-end and back-end development to DevOps. Anyone can do simple hosting if they learn a little, but the full-stack path to becoming an expert in each field is long and not easy. I was impressed by the article that gave advice on companies that full-stack developers should join. This is really important information. The number of team members is important, but the number of people who will be in charge of the project I am in charge of is the most important.

Episode 21. Serverless means no servers?

Recommended for people doing side projects or companies who want to release a prototype as quickly as possible.

Serverless means that there are no servers, but it does not mean that there are no servers.

Serverless refers to allowing flexible use of servers in a manner such as Amazon EC2 instead of manually managed servers.

Managing an actual server involves many tasks, such as operating system updates, security, failure recovery, and data backup, so building serverless allows developers to focus more on code.

Functions in serverless need time to wake up: cold start

It may be slightly later than the 24-hour online service server. This is because it wakes up and responds only when necessary.

Too dependent on server provider.

If you have built a serverless environment, it is not easy to build it with another company's serverless environment.