Shulou(Shulou.com)05/31 Report--

This article mainly introduces the way enterprises use the database, the article is very detailed, has a certain reference value, interested friends must read it!

Mode 1: commercial database + commercial services

This is a more traditional way. Enterprises purchase large-scale commercial database software and support the purchase of services. In the past 30 or 40 years, this has been a mainstream way of use. It can be said that it also satisfies the rapid development of all kinds of enterprises. However, with the change of the Internet in the past two decades, it has had a great impact on this way.

This method is suitable for traditional enterprises, with high requirements for databases, limited technical capabilities, and relatively fixed future development, and the future development will change with the development of commercial databases. On the whole, the demand for cloud will have a greater impact on it. In addition, under the requirements of localization and self-control, it will also have a great impact on this model.

Cost factor

From the perspective of labor cost, the overall investment is not large, mainly provided by manufacturers. Self-owned personnel mainly complete the audit, evaluation and other work. From the analysis of financial cost, it is the relatively highest one of several schemes. Often see "a state-owned bank, annual database purchase xxxx ten thousand yuan of news" in the newspaper.

Because of the large financial investment, this approach is generally limited to large and medium-sized enterprises or some special industries. In terms of time cost, it is relatively small. Choose commercial database + service, that is, value its years of product research and development technology accumulation and mature commercial delivery capability. Whether it is product maturity, stability, or service support, it can be delivered in a relatively short time.

Risk analysis.

Technical risks: the technology is closed and not open; it does not meet the requirements of self-control.

Political risk: if it is a foreign product, it is also vulnerable to the political environment.

Financial risk: easy to be kidnapped by manufacturers, economic input is not controllable.

Personnel risk: it is greatly influenced by the technical ability level of the manufacturer's technical personnel, which can not be borne by its own personnel and cannot be grown for a long time.

Functional risk: mature commercial products, it is difficult to customize to meet the individual needs of customers; and there is a risk of integration with other components.

Transformation risk: after adopting a commercial product, it is more difficult to transform other products.

Other instructions

Commercial products, including domestic database and emerging database manufacturers. As a good supplement to commercial products, these two kinds of schemes have advantages in comprehensive cost, but they still need to be further strengthened in product functions and service capabilities. After all, similar to foreign commercial products and services, it has been accumulated for 40 to 50 years.

Commercial services, in addition to the original factory services, also include third-party service support companies. In the choice of the latter, there is a big difference between foreign and domestic manufacturers. Recently, we have seen a lot of cooperation between domestic database manufacturers and third-party service companies (including training, certification, delivery, etc.).

Mode 2: commercial database + autonomous service

This way is also more common. In the former way, with the deepening of the use of commercial software by enterprises, the demand for own services becomes urgent. Through the establishment of its own service system, we can better meet the needs of enterprises. This method is suitable for traditional enterprises with certain technology accumulation. The future development changes with the development of commercial databases, and the overall situation is relatively stable.

Cost factor

In terms of labor cost, there is more investment than the former. Commercial database products have been promoted for many years, and there are a large number of relevant talents, so it is generally easy to recruit the needed talents, and the price is often not too high. This is in sharp contrast to the later open source software. The input of financial cost is still relatively large, and the purchase cost of commercial software accounts for the majority of the whole.

In terms of time cost, it has increased compared with the former, but it is still on the low side as a whole. This is mainly because of the mature ecology of commercial databases, it is easy to build an operation and maintenance system, and it is easier to supplement talents.

Risk analysis.

In terms of risk, it is similar to the former. Among them, in terms of technical risks, there is still a gap between the control of commercial products by our own personnel and that of the original factory. Of course, the risk of the corresponding personnel is reduced, and the product is more controlled by its own personnel.

Other instructions

In some key core areas, it is still recommended to use factory support to reduce technical risks.

Mode 3: open source database + commercial services

With the increasing maturity of open source databases, more and more enterprises begin to use open source databases. However, compared with commercial databases, open source solutions require higher technical capabilities of enterprises. As a result, many enterprises that are considering riding the wave of open source adopt this approach. It is suitable for enterprises in transition, from commercial to open source, which can avoid risks to a certain extent. However, it is generally a transitional stage, and in the long run, it is still necessary to cultivate the enterprise's own service ability.

Cost factor

From the point of view of labor cost, it is in the middle level, and its comprehensive labor cost is lower than that of commercial services. The input of financial cost is about medium, but there are great differences among different service manufacturers. The time cost is less, but compared with the business plan, the enterprise needs to do more technical research on the business service. Therefore, in the initial evaluation stage, it often needs to invest more time.

Risk analysis.

Technology risk: open source database technology risk, enterprise technology selection risk and business service capability risk.

Personnel risk: it is greatly affected by the technical ability level of the manufacturer's technical personnel and needs to be carefully evaluated.

Functional risk: in general, open source databases are functionally deficient compared to commercial databases. Therefore, this part should be carefully evaluated.

Other instructions

Different from commercial services, at present, in terms of open source services, the capabilities of various vendors are uneven, and there is no more unified standard. Some open source databases are commercially supported by the so-called "original factory", but they are less popular in China.

Mode 4: open source database + autonomous service

This is a typical "Internet" game, but also a more common way. It is suitable for scenarios with large scale and high requirements for enterprise customization. Mature can consider to the enterprise internal private cloud or database products, solutions direction, or even external empowerment.

Cost factor

The labor cost of this method is relatively high, but it varies greatly according to the scale and difficulty of the enterprise. The development of open source database has also gone through a period of time, and the number of talents in the market is also gradually increasing. But for high-end talent, it is still relatively scarce, and the cost of talent is also high. In terms of finance, it is also mainly reflected in the cost of manpower.

In addition, there needs to be some investment in infrastructure, perhaps even more than in commercial solutions. The time cost is high, and it takes a certain amount of time for enterprises to establish a mature open source database operation and maintenance system.

Risk analysis.

Risk analysis is similar to the above, highlighting personnel risks and requiring long-term training and investment.

Mode 5: open source customized database + commercial services

This is a special case of option 3. Instead of using native open source products, enterprises use third-party companies to customize open source solutions, which may be pure software or hardware and software. In view of the shortcomings of open source software, this kind of approach will make customized improvements to meet the needs of enterprise-level software.

However, in this way, enterprises are generally unable to operate and maintain independently, and need to rely on the commercial support of third-party companies. There are high requirements for the enterprise-level characteristics of the database, but the native open source database can not meet the situation. It is very suitable for scenarios where there is a need to remove commercial databases in the short term. With the deepening of domestic use of open source database, more and more such start-up enterprises appear. I am very optimistic about the future development of this model.

Cost factor

Manpower cost, mainly from third-party services, is not high as a whole. Financial cost, mainly depends on the situation of the plan, there is a big difference. The cost of time can be regarded as a pure business solution.

Risk analysis.

Technical risks: the customized part is not open, and the enterprise cannot control it; in addition, the version changes of the native open source may not be applicable to the solution in the short term.

Personnel risk: it is greatly affected by the technical ability level of the manufacturer's technical personnel and needs to be carefully evaluated.

Transformation risk: limited by the scheme, there is a certain risk of transformation.

Method 6: private cloud + cloud service

The final deployment plan for enterprise privatization is a cloud compromise. Some enterprises cannot directly use the public cloud, but they urgently need platform capabilities similar to the public cloud. As a result, some cloud vendors or database vendors offer a private cloud deployment solution. It can be simply understood as moving the cloud back home.

In the past, there was a saying that private clouds would gradually shrink and public clouds would dominate the world. However, from the development of the domestic cloud market in the past two years, the development speed of private cloud is even faster than that of public cloud. When we now talk about the "toB" market as the next blue ocean, this model is also an important part of the toB services market. This approach is suitable for large enterprises and is bullish for a long time.

Cost factor

From the perspective of cost, the input of manpower cost is not large, which mainly depends on the input of manufacturers' personnel. In terms of financial resources, although compared with large-scale commercial solutions, there are certain cost advantages, but the advantages are not obvious. In terms of time cost, it is also longer than the traditional solution, after all, this is not the replacement of a single technology platform, but involves Iaas, Paas and many other aspects.

Risk analysis.

Its risk point is not only in terms of financial resources, but also in its technological dependence on manufacturers. This approach is even more dependent than traditional schemes. Manufacturers generally provide good private clouds and solutions corresponding to their own public clouds, but it is difficult to get through other public clouds or enterprise-owned platforms.

Mode 7: naked cloud + open source database + autonomous service

This is the initial stage of cloud usage. Enterprises only use the Iaas part of the cloud, and the rest are self-built. This approach can take full advantage of the resilience brought by the public cloud and extend the original technology accumulation of the enterprise to the cloud. For enterprises, this approach is also the most "smooth", even applications can not do more awareness, and still use public cloud resources just like using internal IT resources. It is very suitable for situations with cloudy and cross-cloud requirements. But the disadvantage is that it is unable to take advantage of the added value brought by the technological capabilities of cloud vendors.

Cost factor

From the cost point of view, the enterprise can achieve the "best". In the case of using only bare metal, the choice can be optimized according to the strategy of "the lowest bidder gets". In the case of a certain scale, public cloud still has its price advantage, not to mention that it can make full use of elasticity, dynamically reduce, and adjust IT investment at any time according to the development of the enterprise. In terms of personnel, there is little change with the independent operation and maintenance of the enterprise. In terms of time, there is still a certain improvement because of the improvement of the delivery speed at the bottom.

Risk analysis.

The risk is not great, just rely on the bottom of the public cloud, it is easy to migrate to other cloud vendors or move back to their own.

Method 8: naked cloud + commercial database + third-party service / autonomous service

This is a relatively special case. Enterprises choose to build commercial databases on the public cloud. However, it did not choose what the cloud vendor provided, but built it on its own or chose a third-party vendor to assist in it. These are often small and medium-sized enterprises that are not large enough to support privatized deployments and applications rely on commercial database products. Enterprises want to take full advantage of the resilience of the cloud, so they combine this way of use.

Cost factor

In terms of financial costs, it is mainly targeted at the infrastructure level, which will be more economical than self-construction. In terms of manpower and time, there is little difference.

Risk analysis.

The risk is that some commercial databases are not supported for cloud scenarios, and enterprises have certain technical risks. Either have a strong independent technical capability, or rely on third-party service vendors.

Method 9: cloud database (open source) + cloud platform services

This is the most "traditional" database service launched by cloud manufacturers, and it is also the most popular choice at present. Cloud vendors build their database products based on open source database versions plus their own platform services. Its core database is completely consistent with the open source version, and the competition is more about platform service capabilities. This approach requires very low requirements for enterprise operation and maintenance, and can basically rely on the capabilities provided by cloud vendors (except for individual high availability and disaster recovery requirements). This scheme is more suitable for the initial cloud enterprises, and can gradually explore the difference between the cloud and the original way.

Cost factor

In terms of financial cost, there is no doubt that there is an advantage over commercial solutions, but there is almost no advantage compared with independent open source. It is more in the rapid delivery, expansion and other aspects of product features. In addition, for manpower costs, due to the substantial reduction in operation and maintenance work, it is possible to save a certain amount of manpower and reduce the size of its own personnel. In terms of time cost, it has also increased.

Risk analysis.

The database itself is not risky, after all, it uses the same version as open source and can be technically migrated to other cloud vendors. When the database version is upgraded, you can also enjoy the corresponding technical dividend. However, there is a certain dependence on platform services, and each family has different abilities, so it needs to have an adaptation process. In addition, the operation and maintenance rely on cloud manufacturers, there are also some technical risks. Independent technical ability will be gradually lost. How about Jiaozuo National Medical Hospital? _ _ the effect is reliable. People approve: http://jz.lieju.com/zhuankeyiyuan/37841631.htm

Method 10: cloud database (open source customization) + cloud platform services

In addition to providing the same version as open source, cloud vendors generally provide private customized versions. It is often based on the deep customization of a certain version of an open source database and is enhanced for some features. Of course, some of them give back to open source in the form of feedback to the community (there may be a new version of merge in the future), but many only exist in "cloud private DB". If the enterprise has a strong demand for a particular scenario (such as second kill) or other aspects (such as financial data synchronization), you can consider using this solution. When

However, use also means deep binding with cloud vendors. In addition, in terms of platform services, the situation is similar to the above. This scheme is more suitable for situations where there are certain requirements for the database, but the native open source version does not support it.

Cost factor

Similar to the previous method.

Risk analysis.

The risk lies in binding a single vendor, which is generally difficult to get down. This is similar to the use of large commercial databases. Of course, you can do a design on the application side to minimize the dependence on features. In addition, because it is a custom version, future open source version upgrades may not be supported in a short period of time, or even may not be considered, completely moving towards an independent branch. In view of this, enterprises also need to pay attention to.

Method 11: cloud native database (self-developed) + cloud platform service

In addition to the above two, some large cloud manufacturers can increase the competitiveness of their products in the future by developing their own databases. According to the latest Gather report, more cloud vendors have joined in, which has brought vitality to the overall database market. From the perspective of prediction, they are all optimistic about the future development of cloud native database. Compared with the first two ways, this kind of database is born in the cloud, and takes more into account the characteristics of the cloud environment from the beginning of the design, so it is very competitive.

Of course, from the current point of view, the existing cloud native is still in the "primary" stage, in the future, after solving the larger scale scalability, more reading and writing capabilities, it will really enter the blowout development. The existing major factories have focused on layout and increased investment in this field. For enterprises, there is undoubtedly another choice, especially in some scenarios (such as massive data, etc.), native open source and extended open source products can not be satisfied.

Cost factor

At present, various manufacturers are sparing no effort to promote, so enterprises can still benefit from the cost, but in the long run, further observation is needed. In terms of personnel, enterprises also need a certain amount of investment. after all, this is a new database. Although cloud manufacturers provide a good interactive platform, they still need to make certain technical reserves, so they still need some investment in personnel. In terms of time, more testing and evaluation work needs to be done for this relatively new product, so it also needs more investment.

Risk analysis.

The risk is similar to the above, or even has been there. Enterprise applications will be completely dependent on manufacturers' products. Although many promote compatibility with open source or commercial databases, they are not the same product after all. This still needs to be carefully evaluated by enterprises. In addition, compatibility, backup and recovery, high availability, data synchronization, cross-cloud disaster recovery and so on are all worthy of research.

Method 12: cloud database (self-research) + cloud service + cloud hosting platform

This is a niche solution, and its background is due to the problem of cake division between database vendors and cloud vendors. Some database vendors (such as MongoDB) do not want to make the cloud database market dominated by cloud vendors, but want to be led by themselves and build an independent ecology that does not depend on cloud vendors. At present, this method is rare in China, and I will not comment on it here for the time being.

The above is all the contents of the article "what are the ways in which enterprises use databases?" Thank you for your reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.