Repractise Basic article: Web application development 7th Talk

Source: Internet
Author: User

Repractise Basic article: Web application development 7th Talk

The only thought was to draw an example of the following 7th diagram that says Web development. And then I thought about it. This seems to be a great introduction to Web development-related knowledge. Application development is a very interesting cycle, and most of the time we always assume that someone else's code is poorly written. Even if it uses a very good design, we may think that he is very complicated.

And it sums up something that happens in the following seven-day process.

7th talk

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

First day: New Beginning

We have ushered in our new project and it seems that everyone is very excited. It was a very fast day, and it did 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 easy hello,world--that has a tradition in most languages.

This is a Web project. It seems that the hello,world in our chosen frame 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.

By the way, create one or more servers to advertise and build.

At last. This is done by carrying the corresponding pipeline in our continuous build system.

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. To start a real coding job.

We've got a mission. Know what it is to do after that.

We start by stepping into it, what we do first, what we do next, and every step is clear.

Be able to write our first Test. It seems that this test does not seem to be easy to imagine, we need to mock the object.

Ah. This component needs to fake a service. The first task seems to be finished coding, let's simply refactor it.

We already have the unit test and now let's add a functional test. In our example, it also seems to require an integrated test.

can finally commit. and push the code.

Day three: Ready to go online

As we continue to repeat the second step. We also 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. There needs to be a toggle 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. Make visiting the site more and more people.

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

Well! This is a bug!

The performance of the app is much better than ever. One server can top up the previous two. A lot of servers were saved in a sudden.

Looks like. 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. This code is written by WHO.

There needs to be a refactoring here, and there's a need for refactoring here.

What the! No test.

shit!

Day Seventh: summary and plan

Ha! Our competitors are using new technologies. And our system is dead. Let's design a better system out of this component we can use this technology. This component allows us to use that technology.

The future is bright again.

Now. We're back on the first day.

(PS: Temporary advertising area.) Please pay attention to my public number--start!

Search: Phodal. or scan the following QR code)

Repractise Basic article: Web application development 7th Talk

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.