Shulou(Shulou.com)06/01 Report--

Editor to share with you how to self-study the whole stack of web, I believe that most people do not know much about it, so share this article for your reference, I hope you will learn a lot after reading this article, let's go to know it!

First of all, you need to know what web full stack is and what you need to learn about web full stack.

Second, you should know that self-learning web stack is not a simple thing, you need to have enough perseverance to adhere to, but also need you to have the ability to learn efficiently in order to learn it well in as short a time as possible.

A Web development process has three layers of architecture:

Presentation layer: the presentation layer is also known as the front part of a website. It deals with issues related to the user interface of the site.

Business logic layer: the business logic layer, also known as the back-end layer of the website, is responsible for data verification and dynamic processing.

Database layer: finally, there is the data access layer, which uses API to provide data for the website.

The above three layers are collectively known as full-stack web development.

As a web full stack engineer, you need to know the following knowledge:

1. Service management / operation and maintenance

A developer must have a basic knowledge of server management. Including when not limited to the following knowledge:

Remotely connect to the server through a terminal or other environment without a user interface

Can write basic shell scripts

User and group management on the server

Manage server programs like Apache and Nginx to provide applications

Firewall management and rights management

Install and update softwar

In addition to these basic skills, developers must know how to create a good, healthy, separate development environment in Docker or a virtual machine environment like Vagrant. If you are not familiar with all the above technologies, then I must recommend a great book to you and click here to buy it.

Developers must be proficient in version control systems in order to develop reliable production backups and shareable and collaborative code bases that can track code changes over time. No developer workflow is completely out of version control now. We have a great video tutorial on version control, click here to buy.

2. Cloud

Unlike actual management or virtual servers, a developer may want to know about cloud hosting platforms such as Heroku, Google Cloud, Azure, AWS, and so on.

It must be noted that platforms and tools are more about hype than their usefulness. Although there are many platforms and tools that are not as useful as advertised, knowing about the services that everyone is talking about can be useful in the long run-customers may ask for a change of service provider at any time. Fortunately, we have these authoritative guidelines for cloud host deployment.

3. Backend

At the back end, in addition to knowing which language to choose, such as PHP and numerous frameworks and CMSes, a full-stack developer must be familiar with:

Web servers, such as Nginx and Apache, are closely related to operation and maintenance.

Unfortunately, NodeJS has been able to compile JS, CSS, and other resource files into static files that can be easily cached. Fortunately, there are ways to avoid learning NodeJS, and it is possible to use PHP.

PHP like Composer (http://www.ujiuye.com/zt/php/) package management tools) is inseparable from the modern development environment.

Good API design, since most new web pages are based on API and are only for front-end services (described in more detail below)

Search engines like ElasticSearch (introduction here) are very important for improving the performance of websites.

Cronjobs and back-end work, using libraries like Gearman or Crunz

Understand that caching, Varnish, Redis and other tools of Niu B can store data in pieces, so that you can deploy a project on multiple hosts

4. Database

The database is a separate part, because in addition to having a good grasp of the data schema of relational databases (MySQL or PostgreSQL) where there are few structural changes, a full-stack engineer should know something about non-relational databases, such as MongoDB, Redis, or Cassandra, not to mention graphical databases like Neo4j.

Unfortunately, these are all things on the server, under the control of the full stack engineer. There are also several remote solutions similar to Mong, such as RestDB or Google-owned Firebase.

5. Front end

If you want to know what a normal front-end knowledge graph looks like, you can read this excellent article in the JavaScript section. But as a full stack engineer, you need to understand

NodeJS and NPM

Yarn

Preprocessors and compilers (such as Babel) to compile Typescript, ES6, LESS, SCSS, SaSS

Build tools such as Grunt and Gulp

Frameworks such as VueJS, React, Angular

Module packaging tools, such as Webpack, Browserify, Rollup

6. Design

On the design side, full-stack developers need to know how to draw a prototype before a product becomes real HTML and CSS code. Then you can use JS to write interactions, and the back end can use fake data to simulate the production environment. Only when this key prototype is completed and the user experience design and interface design are ready can real development begin. This is a daunting task in itself and requires a special set of tools:

Photoshop and Illustrator or some open source tools such as Gimp/Inkscape. Visit Design channel to learn more about such tools.

A cool, fast editor, such as Atom or Sublime Text (here are ten useful sublime plug-ins)

Background selectors and color selectors like Subtlepatterns can match some colors.

Grid system of CSS

All the knowledge and JS data simulation required by the front end mentioned above

Publish the prototype map on the Internet for everyone to browse and give feedback, Ngrok is very easy to use

7. Log system

In order to effectively monitor the health of the application, full-stack developers must be able to track errors, find the error log and extract useful information from it. Full-stack developers also need to predict some trends from the log, such as the increase in CPU or Imap O occupancy, in case the application dies without knowing when. This part also has something to do with operation and maintenance, but requires some special skills:

Recommend a great ELK stack article, which will help you understand what you need to do a journaling system. It includes ElasticSearch for finding logs, Logstash for collecting logs, Kibana for displaying logs in great charts, and even Logz.io for providing solutions.

8. Mobile terminal

Finally, it's time to talk about mobile. As webview on iOS and Android becomes more efficient, and with the advent of PWA (progressive web applications), native apps are becoming dim because they are so complex to develop. So a full stack engineer must know PWA or React Native, or NativeScript, Tabris, Cordova, Phonegap or other webview to make client applications call API to run.

The above is all the contents of the article "how to learn by yourself in web Stack". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.