Recently, I have been building a development platform for micro-service. Since this is an experimental project, all the work is currently being done by myself.
Today, when summarizing the development of a web service with python, I occasionally gained something, which made my thinking about building a micro-service development platform a lot clearer, at least I think it is still useful for now.
The following list compares demo development and product development.
| Demo development | product development | |
| Business function realization | consider | consider |
| data persistence | don't think about it | consider |
| Automated deployment scripts | don't think about it | consider |
| log | don't think about it | consider |
| Application configuration | don't think about it | consider |
In fact, I usually also write a lot of python code, I think it is relatively good, I think it will be smooth sailing when developing this web service. But that's not the case at all.
The list above shows the reason for this contrast.
I thought of another more appropriate analogy, for example, you will cook the best dish in the world, but this does not mean that you can successfully open a restaurant because, once you decide to open a restaurant Son, you have to consider, store decoration, staff training, industrial and commercial tax and so on.
And this also made me clearly realize that the function provided by the micro-service platform in the future is to allow users to spend more cost and energy on business, and no longer need to worry about data persistence, automated deployment, logging, configuration and other architectural issues.