laitimes

A debate about whether DAM should be in the public cloud or privatized

author:Boom|Tezign

This article

It started with a debate from within Tezan

A debate about whether DAM should be in the public cloud or privatized
A debate about whether DAM should be in the public cloud or privatized

"The deployment of public cloud allows users to continue to enjoy the value and convenience brought by product upgrades."

As a SaaS product, DAM should be deployed in the public cloud from several perspectives:

Data perspective: More than 80% of mature DAM products abroad, including Adobe's AEM, Bynder and other mainstream DAM solutions, adopt the deployment method of public cloud, and most of them will not be wrong;

From the perspective of cost, DAM deployed in the public cloud uses a one-to-many model, and the cost is shared by different customers. Therefore, customers do not need to pay for servers, personnel, technology and hardware to support, maintain and manage terminal software solutions, which greatly reduces the cost of using the product, so that more customers can use mature products at a relatively low price, and the deployment cost of product updates and iterations is higher than that of privatized deployment;

From the perspective of efficiency: SaaS, as a public cloud deployment method, can basically be used out of the box, while privatized deployment requires more technical deployment and development cycles, and SaaS has more advantages from the perspective of use efficiency and operation and maintenance.

From the perspective of sustainability: SaaS is a product that is continuously upgraded and iterative, and the deployment of public cloud can allow users to continue to enjoy the value and convenience brought by product upgrades. On the contrary, privatization deployment is a backwater, and there is little room for upgrading. (Clean, clearly stated, give yourself a compliment)

A debate about whether DAM should be in the public cloud or privatized

Speak as a strong proponent of the DAM public cloud

· Those who like it are staunch supporters of DAM's public cloud...

"If the technology is decoupled and componentized enough, private deployments may also be deployed very agile and quickly."

Counter-view: DAM should be completely privatized. Respond to the positive question.

Data perspective: 80% of foreign DAM vendors are providing SaaS services and public deployment, which does not mean that 80% of foreign customers use SaaS public ownership. Many enterprises still choose SaaS private cloud and hybrid cloud deployment.

There is also data that suggests that the current dominant deployment model is private cloud, with just over half (or most likely to adopt) of private clouds (52%) among surveyed organizations. Hybrid cloud is the first choice for 31% of respondents, while another 11% choose public cloud.

Cost perspective: The privatization also provides SaaS services, and the subscription fee is no different from the public cloud, with the only one-time privatization deployment fee added. If the enterprise provides the same cloud environment, the deployment can be completed in 1~2 weeks, and the cost is controllable.

From the perspective of efficiency: SaaS, as a cloud deployment method, can basically be used out of the box; However, private SaaS also has a private cloud environment deployment method, if the technology is decoupled enough and componentized enough, private deployment may also be very agile and rapid deployment.

Sustainability perspective: privatization is also iterative; One of the world's first-class DAM standards is that it can be privatized quickly; Localized deployment is a backwater, but we don't recognize that privatized deployment is a backwater.

Additional takeaway: Security remains the number one priority for any business.

The company's data is more assured in its own hands, and the privatization still provides Saas applications, which do not touch the security of the enterprise's data. All privatized deployments deploy the software directly on servers in the enterprise intranet, and the data is stored within the enterprise. In the process of enterprise operation, a lot of data is related to trade secrets, and most enterprises will choose to have a higher control over confidential data. (Reasonable, yes, give a thumbs up to the opponent's defense friend)

A debate about whether DAM should be in the public cloud or privatized

· The two who were still staunch supporters of the positive side just now quickly switched to support the opposing side...

"At present, the security of the public cloud is not bad at all, and it is even more secure than the private cloud of many enterprises!"

Security: Opposing the opposing viewpoint, many enterprises will be confused by data security in the early stage and choose privatization deployment, and everyone is particularly confident in their server data security. In fact, the security of the current public cloud is not bad at all, and it is even more secure than the private cloud of many enterprises! The security of its own servers is not necessarily better than that of the public cloud (a well-known local large-scale snack industry has a backward level of server and data security, and the network speed is as low as 2G).

From the perspective of sustainability: Tezan is deeply engaged in the industry track, serving leading FMCG, retail, food and beverage, mother and child, beauty and other industries, with continuous insight into the industry, and countless large and small iteration products every month, while the internal project owner of the enterprise is insufficient, and sustainability needs to have clear indicators and motivation to promote product development.

Professional labor cost of the brand: In the public cloud deployment of SaaS services, the software company will have professional personnel to update and maintain the system daily, and the system server deployed by privatization is within the enterprise, so that the enterprise needs to arrange professional personnel to carry out daily maintenance of the system, but for many enterprises, Inhouse's IT role in China Marketing is very small (a well-known food and beverage company said that there is only one), If the managed cloud broker service provider adds an additional layer of risk. In this way, every update or docking will occupy a large amount of technical manpower of the brand, and there will be endless troubles in the future. (Practice brings true knowledge, and the conclusions drawn from practice are the most convincing)

Just when the positive side thought that he had won, a mysterious debater added another dose of fierce medicine:

Security: Kevin Mitnick, the world's number one hacker, said, "The vulnerabilities that are best at finding are not technical problems, but human weaknesses." There are data to show that "people" is the weakest link in the entire network security system; On the contrary, since most of Party A's core business does not aim at IT system services, the human resources invested in related aspects are often not as good as those of professional Party B's IT service providers. The data seems to be kept by itself, but it is as if the money is stored in its own safe instead of choosing to be stored in the bank. (Golden sentences, golden sentences!) )

A debate about whether DAM should be in the public cloud or privatized

Keeping it in your own house or in the bank? More debaters continue to contribute:

Public cloud is cost-effective: Content and market are only part of the overall digital transformation of enterprises, and more basic DX such as financial data, CRM, and OA need to be invested in. Public cloud, cost-effective!

Resource elasticity advantages: SaaS computing resources naturally have the elastic advantages of cloud computing resources, which can be used to cut peaks and fill valleys. In response to special peak periods, resources can be allocated according to professional design in a timely manner. If a single customer deploys on its own, it is often difficult to scale out the scale through temporary budget requisitions when faced with temporary business pressure, which affects the business and user experience.

Public cloud is a better way to manage innovation: ConTech as a whole is still a new industry and in its early stages. It should be started quickly at a lower cost, and it should be practiced on the public cloud. If you choose to build an on-premise on-premise product from scratch, there is a potential risk of uncontrollable budget when encountering challenging technical problems: many parts have already been built, but it is likely to be a little bit close to the closed loop, becoming an unfinished building, and falling into a budget dilemma; It's better to make the simple decision of a trial-buy SaaS. The public cloud allows you to try fast!

Public cloud means industry standards and norms: a good SaaS product can achieve specific industry standards, which means that the cost of interconnection with other systems and the cost of employee training will be reduced. For example, github has defined the specification of collaboration tools for programmers, so it is easier for enterprises to choose such SaaS products to familiarize external professionals with relevant business tools when they are introduced, which will help reduce the overall personnel training cost of the industry and improve the level of management digitalization. Privatized products tend to over-pursue specificity, which is likely to increase the learning cost of software.

There are professional people to cover it: private cloud generates internal personnel dependence; Property losses caused by operational errors have to be carried out by themselves, such as prolonged downtime or data loss. There is a public cloud, someone will help you take care of it! (There is an SLA when something goes wrong)

Security and supervision: The security of the cloud private or public should not be bad, after all, it is all cloud~ In the long run, with the popularity of cloud services, the continuous growth of large cloud providers and the completion of laws and regulations, the state will help enterprises share a large part of the supervision of public clouds. Public cloud is the future! Follow the country! (Wow, star-eyed, follow the macro!) )

Just as we were about to summarize the information and find the boss to make an errand, a picture pulled us back to reality:

A debate about whether DAM should be in the public cloud or privatized

According to Forrester's research, privatization still accounts for a large proportion of the international market, especially for leading enterprises, and there is still a certain rigid demand for private deployment in the short term (most of them are data security issues...). Or...... psychological security needs), in addition to hybrid cloud as an option for the transition phase.

In the long run, the overall market is still optimistic about the public cloud SaaS model, and the market's requirements for the lightness and agility of the system are getting higher and higher, and the advantages of public cloud SaaS will become more and more obvious.

DAM customers want flexible deployment methods, but they prefer cloud services overall!

In fact, public and private deployment methods have always been a hot topic of discussion in the software field, which way is the most suitable for their own enterprise at this stage of the form only the enterprise itself knows best, so we suggest that each enterprise can do its own enterprise analysis and diagnosis, find the most suitable deployment and use mode, in order to maximize the effect.

A debate about whether DAM should be in the public cloud or privatized

More and more data shows that the final choice of customers proves that the deployment advantages of public cloud are becoming more and more obvious, and it has become a trend.