The choice of enterprise database is usually decided by the system architect - the newstack

Forget about the developers , Today's Kingdom creators are called architects , And research continues to show , If you adopt different technologies according to the architect's preferences .

A typical example is a database . according to Percona Of “ 2020 Open source data management software survey ”,41％ The architects in the organization decide how to choose the database technology for the new application . And only 16％ The organization is organized by the database administrator （DBA） be responsible for .

In organizations where database technology is chosen by developers , Rarely used Oracle and Microsoft SQL Server. With DBA The central organization is most likely to use these two non open source options , But many architects also seem to work in places with these traditional resources . Interestingly ,DBA Seems to prefer Cassandra, But it could be due to a lot of Cassandra Open source community participants participated in the results of the survey .

In organizations where technical decisions are made by management , The use of multiple databases is much lower . When selecting a database , These organizations may not consider data storage Redis,Elastic Search and Kafka. Another explanation is that these technologies are not in their radar range .

For developers and Kafka, This may be the case . Even though Kafka In many data stream stacks, it's very Generally , But only 20％ It is used in organizations where database technology is chosen for new applications .

On a broader level ,Lightbend Of “ 2020-2021 Cloud native adoption trend ” Provides information about what the architect is looking for ： Compared to developers , Architects believe that the performance and flexibility of the system take precedence over new application functions . Although they need an interoperable technology framework , But architects are always looking for ways to go through API Services used . by comparison , Two thirds of software and data engineers prefer technologies that can be configured and maintained by themselves .

Data Engineer Is the core of the next generation cloud native data infrastructure . Without trying to define exactly the role needs of the position , Let's see from 50 More than one person with a job role Lightbend Other data points of respondents .55％ The Data Engineer described his cloud native infrastructure strategy as “ Actively adopt ”, The average number of respondents was 39％. Interestingly , Data engineers are also more likely to host most of their major applications or systems in the private cloud -31％, The average number of respondents was 17％.

It seems , Many data engineers are already using Hadoop And other big data systems running in the private cloud . They focus on moving infrastructure to cloud providers ,35％ Thirty percent said it was a move to “ Cloud native ” The most important aspect of , And only 20％ This is the most important aspect .

 

# Occupation planning      # Software architecture      # Data engineering      # database