Requirements for DBAs in the internet age

I have been a professional traditional DBA, and the relational database has basically touched. The last two years of part-time management database, now the Internet company infrastructure are on the cloud, there is no traditional sense of DBA.

Compared to the past RDBMS eminence, today's "database" concept has been more extensive, including relational, NoSQL, cache, big data and so on. Therefore, the ability of developers and managers to put forward more comprehensive requirements, even if not door-to-door proficiency, (the business scope of the database) should be exhaustive.

For myself, in addition to the relational type, other familiar or mastered database storage is:

1. Redis: Mostly cache. The advantage is that it supports queue and object storage
2. MongoDB: Primary storage. Ideal for businesses that need information aggregation, such as social
3. Cassandra: Secondary storage, such as storing instant messages. The advantage is written, our peak is up to 6w/s
4. Elasticsearch: Search engine database that synchronizes the required data from primary storage to ES for on-demand searches
5. AWS S3: Amazon Bulk cloud storage. Many advantages, such as globalization across region
6. AWS Redshift: Amazon Big Data Warehouse, providing POSTGRE-compatible SQL syntax. Can be thought of as the hadoop+hive on the cloud, but the powerful multi-

Requirements for DBAs in the internet age