From 6ca8cd82902d9f41eea28ead080cf5e88e639f04 Mon Sep 17 00:00:00 2001 From: Anchor Date: Mon, 8 Dec 2014 12:51:00 -0800 Subject: [PATCH] Fix grammar and translations in 12.0.md --- en/eBook/12.0.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/en/eBook/12.0.md b/en/eBook/12.0.md index ca0b2827..67cccc87 100644 --- a/en/eBook/12.0.md +++ b/en/eBook/12.0.md @@ -1,8 +1,6 @@ # 12 Deployment and maintenance -So far, we have already described how to develop programs, debugger, and test procedures, as is often said: the development of the last 10% takes 90% of the time, so this chapter we will emphasize this last part of the 10% to truly become the most trusted and used by outstanding application, you need to consider some of the details of the above-mentioned 10% refers to these small details. - -In this chapter we will be four sections to introduce these small details of the deal, the first section describes how to program production services recorded on the log, how to logging, an error occurs a second section describes how to deal with our program, how to ensure as far as possible less impact to the user's access to, and the third section describes how to deploy Go standalone program, due to the current Go programs that can not be written as C daemon, then the process of how we manage the program running in the background so it? The fourth section describes the application of data backup and recovery, try to ensure that applications crash can maintain data integrity. +So far, we've covered the basics of developing, debugging and testing web applications in Go. As is often said, however: the last 10% of development takes 90% of the time. In this chapter, we will be emphasizing this last 10% of application development in order to truly craft reliable and high quality web applications. In the first section, we will examine how production services generate logs, and the process of logging itself. The second section will describe dealing with runtime errors, and how to manage them when they occur so that the impact on end users is minimized. In the third section, we tackle the subject of deploying standalone Go programs, which can be tricky at first. As you might know, Go programs cannot be written with daemons like you would with a language such as C. We'll discuss how background processes are typically managed in Go. Finally, our fourth and last section will address the process of backing up and recovering application data in Go. We'll take a look at some techniques for ensuring that in the event of a crash, we will be able to maintain the integrity of our data. ## Links