Starting from the 192020 epidemic, it has brought major challenges to the tissue from the sudden changes in the remote office: the amount of data to protect the surge is protected from the vulnerability. As many countries have begun to accept “new velocacy”, organizations face new challenges: protect the data of mixed labor and their stakeholders.


In the past, focusing on code vulnerabilities and access, but in the micro service, distributed systems and online data processing ages, focusing on protecting communication channels, especially because of the “new normal” work. It is expected to see more attention to more secure communication between processes and applications. We must learn how to trust information from the source to ensure that this information is passed to the correct person, ensuring data is safe and passed proper authentication and authorization.

The challenge here is that the database used by many organizations has been established a long time. New versions of these databases in a closed source environment often means that existing versions must continue to work, allowing the product to have a technical mortgage. This may expose data to errors and security leaks. If the technology has not developed for many years, you will eventually get a clumsy, confusing system.

This is the success of the open source database technology such as Postgres. This community is keen to build for strength, and it is not afraid to modify it.

Although the misunderstanding of open source technologies still exists, the challenge of closed source database must also be considered. For example, customers typically take more funds to maintain these databases than open source alternatives. The open source driving force is to ensure that the organization will not be hindered by the function of the value that cannot be returned. Open source allows them to protect the database to ensure that the cluster is highly personal, ensuring that the entire database does not have a vulnerability.

Closed databases are considered safer because it is supported by a very payable of security vendors. If you want to use a closed source database, you may hardly find a vulnerability, and suppliers usually try to patch any vulnerabilities and maintain their security.

However, if anyone can expose open source vulnerabilities, then the same truth, anyone can identify and repair them, so that it can build precautions faster and more secure, without relying on individuals to protect them. With more and more people read source code, more and more people can build patch and repair, making the core code safer.

Although the open source database lacks a specific supplier, business partners providing enterprise software and services can make up for this difference. Open source community can support the implementation of protection measures, and make up for possible gaps, ensure that patch as early as possible, and provide 7 * 24 services, help organizations keep “always online”, protect themselves and stakeholders.

With the beginning of the transition to large-scale mixing, we have not reached the level we need. It is necessary to properly protect the data in the “new normal” environment, and there are still many things to do. However, organizations can protect themselves with their stakeholders through investment open source databases, to ensure the heart.