(Continuation from yesterday)

Even so, the concept of docker technology is amazing.

We IT engineers have long been suffering for a long time due to inconsistencies in program operating environment, even more than program development.

Due to this environmental inconsistencies, we have experienced a lot of "painful scenes" where the program that runs on the developer side does not move on the service provider side either.

In recent years, virtual machines (such as VMware and VirtualBox) have caused this problem for a while.

However, by separately managing independent virtual machines, I also realized that even in the virtual machines, operating environment mismatch would occur.

-----

By contrast, Docker's thinking is quite simple and violent.

- Without virtualization of the entire system, Pack (containerize) only the necessary parts, and delivered to the people you need

- If necessary, you can just put everything into the container, including the database system.

As a result, now in my "d:" now, there are over 30 containers containing PostgreSQL's body.

"Is there something wrong if I make more than 100 DB units and hold them? "

For a senior engineer who has struggled to save one byte of memory, this is a violent idea that they can never be reached.

However, the size of the container is smaller than the movie's video clips. Totally, there is no problem at all.

As a matter of fact, I thought that the era in which 1T-byte HDDs can be purchased by mail order is around the 22nd century (true).

-----

There is no doubt that in the future, new technology of concept beyond this Docker will be born absolutely .

By the time I will finish understand Docker, I have to start studying the new concept technology

And each time, I will use most of the important holidays to understand the technology.

"Barren" It is the highest level of "barren" in my mind.

However, when I ask myself "What is not barren then?", I do not know.