Repractise Basic article: Web application development 7th Talk

Repractise Basic article: Web application development 7th Talk

All I wanted was to draw one of the following 7th diagram of the Web development, and then think about it seems to be a very good introduction to web development-related knowledge. Application development is a very interesting cycle, and most of the time we always feel that someone else's code is poorly written. Even if it uses a very good design, we may find him very complicated.

And it sums up something that happens in the next seven days.

7th talk

In fact, for web development, the following picture is sufficient.

First day: A New Beginning

We have ushered in our new project and it seems everyone is excited. This day has been very fast and has done a lot of things.

First, we built our own local development environment. We chose a new language and started using the new IDE, a whole new beginning.

Then we started to create a very simple hello,world--that has a tradition in most languages. This is a Web project and it seems that the hello,world in the framework we chose is a todo MVC.

Yes! This frame looks simpler and more straightforward and more usable than the original frame.

Then we started to create our build system. Let's say goodbye to Ant and usher in a new build tool that gradle more powerful than they are. We can use this build tool to do a lot of things--rely on management, compilation and construction, packaging. Gulp looks very popular, let's use Gulp. Create one or more servers for publishing and building by the way.

Finally, the pipeline is carried out in our continuous build system to accomplish these things.

On the first day, it was so exciting to end.

Day two: A new and exciting experience

"There is no way, the first day is to do those things." ”

Now it's time to start working on real coding. We got a task and knew what it was to do.

We began to step into it, what to do in the first step, what to do next, every step is clear. Can write our first test, it seems that this test does not seem to be easy to imagine, we need a mock object.

Ah! This component requires fake a service. The first task seems to be the completion of the code, let's simply refactor it.

Now that we have the unit test, let's add a functional test. In our example, it also seems to require an integration test.

Finally, you can commit and push the code.

Day three: Ready to go online

As we continue to repeat the second step, we have to start thinking about how to go online.

Are we deployed directly in a docker container? Or is it deployed directly on the server? Next, we configured the cache service and the load balancer, and so on.

Hey! This configuration is written to death! A toggle is needed here to control whether the function is online!

Day Fourth: Data analysis

After a few days on the line, some data has been found to have changed. Access to the site has become faster, making it more accessible to people who visit the site.

Wait, this place doesn't seem to have been used!

Well! This is a bug!

The performance of the application is much better than before, a server can top the previous two, save a lot of servers in a sudden.

It seems that users prefer that feature, let's enhance this feature.

Day Fifth: Continuous delivery

A bug was fixed again.

Oh! I don't think this feature users would like.

Ha! This new feature looks good.

Day Sixth: Nightmares

Alas! who wrote this code!

Refactoring is needed here, and it needs to be refactored here.

What the! No Tests!

shit!

Day Seventh: summary and plan

Ha! Our competitors are using new technology, and our system is out of the game. Let's design a better system, this component we can use this technology, this component we can use that technology.

The future is bright again.

Now, we're back on the first day.

(PS: Temporary advertising area, welcome to follow my public number-first!) Search: Phodal, or scan the QR code below)

Repractise Basic article: Web application development 7th Talk