Dear friends, when I chose the DBA industry, I never thought that one day I would sit in the position of operation holding my notebook and typing this article word by word. The story started a week ago when I was walking to work in the morning sun when I received an email from my company’s official account asking if the DBA industry is going to die. I was at a loss. No one told me I needed to protect my job as well as my data.

However, it is true that with the advent of the era of big data, various automated operation and maintenance platforms born along with the explosion of data volume have greatly encroached on the living space of DBAs, so there are various rumors about it.

As far as I am concerned, DBA is still a profession that cannot be replaced. Although automated operation and maintenance platforms have solved most of the operation and maintenance work, there are still many details that cannot be filled in between the seemingly heavy platforms, and these details are the key to determine the quality of our work.

For development operations personnel, efficiency and safety are the primary issues to face. With the differentiation of database types, each database has its own features and official tools, applications may use 2-3 databases as persistent layer storage, a desktop database visualization tool is difficult to completely cover, while desktop tools do not have security attributes, database plaintext password is easier to pass, Fortnite and other control mechanisms introduced by the enterprise are difficult to reach the data layer, and the previous control loopholes are magnified, but the lack of convenient and transparent rights management system leads to the phenomenon of difficult data governance and control.

CloudQuery, which we are working on, is a tool platform for dbAs and development operations and other data operators. As the platform manages most of the data sources in the market at present, as a DBA, I spend most of my working time dealing with this platform and do not need other desktop visualization tools. I can personally experience the convenience brought by the platform as follows:

– Web access without local installation

CloudQuery itself is deployed on a server in the form of software. It supports private cloud, public cloud, and hybrid cloud deployment. Multiple teams can use only one server in an enterprise. At the same time, the Web-based version does not rely on any operating system and can be accessed as long as there is a browser, which prevents the embarrassing scene that employees need to install a bunch of desktop tools when they enter or transfer jobs.

– Rich managed data sources and wide support for data operations

Just mentioned CloudQuery as the unified access point for data, the scope and depth of database support becomes the basic factor for access and use. CloudQuery already supports most databases in the market and has feature support for managed databases. At the same time, we are still iterating and improving, so if the database fails to meet the situation, please do not worry, you can go to the official website of the future version of the plan, maybe you are interested in the function?

– Convenient DBA toolkit

As a DBA, ALTHOUGH I am writing articles for operation, I should not forget my roots. Initially, I developed this tool because I found that the existing intelligent operation and maintenance platform was too heavy and neglected many details related to work. Therefore, we also brought common tools for our peers in CloudQuery. Such as database terminal support, script upload, file execution, and so on.

– Fine-grained permission control and precise authorization

As we all know, the primary responsibility of dbAs is to protect data security, so we are always responsible for data security problems. Therefore, we have directly introduced security modules in CloudQuery, which is a feature not available in the mainstream operation and maintenance tools on the market.

The permission middleware module developed by CloudQuery divides the database permissions horizontally and vertically, and controls the power to the table level. It supports point-like precise authorization during authorization, and supports more than 30 kinds of authorization actions, such as CRUD, CreateTable and DropTable.

– Detection separation to prevent data leakage

Access only data operation is not enough, in a few years I do the DBA deeply felt as long as the data to the ground, it is impossible to avoid data leakage, so CloudQuery last iteration also increased export authority control, data query and data export separating action, from the source to solve the problems such as data transmission and data leakage.

– Audit traceability, fast and accurate positioning and accountability

So much of what I said before is control and restriction. But if something goes wrong, we still need an audit to help us replay the scene. Having experienced the despair of looking through more than 40 hours of videos only to find one deleted record by mistake, we designed CloudQuery and buried every place involving user operations. Meanwhile, we screened details from different dimensions, such as database elements, data operations, users and operation IP, to quickly locate the responsible person. Pull out to worship heaven.

Good, the number of words I gather full, voluminous, one thousand words just want to tell you that in the Internet industry, every job actually exist within the volume, to be irreplaceable one, must be deep in their own positions and always keep industry dynamic and constantly improve their ability, find their own value, and can not be within the volume. In this way, we encourage each other and hope we can become irreplaceable!

Official website: cloudQuery.club /