It’s easy to say, you should always automate everything, monitor everything, and instrument every inch of your data infra. But overengineering in advance of your needs can be just as costly as the reverse, particularly for startups. Engineering cycles are scarce. How do you decide where to spend them?
Enter Maslow’s hierarchy of needs—for databases.
For humans, Maslow’s hierarchy of needs is a pyramid of desires that must be satisfied for us to flourish: survival, safety, love and belonging, esteem, and self-actualization. Each level depends on the preceding ones—we need survival before safety, safety before love and belonging, etc.
Really, databases aren’t so different from you and me. They need:
Charity Majors outlines DevOps/DBA best practices from the earliest seed stages (survival, selecting the right storage layer, etc.) to what you should expect from a mature, self-actualized database tier and offers a roadmap for how practices should evolve alongside the org as it grows up. Along the way, Charity explores how to ensure that your database is a first-class citizen of your engineering and operational processes and dives into some war stories and relevant tooling for MongoDB and MySQL shops in particular.
Charity Majors is the cofounder and CTO of Honeycomb, a new startup focused on mining machine data. Previously, Charity ran infrastructure at Parse and was an engineering manager at Facebook. She also worked with the RocksDB team to build and deploy the world’s first Mongo + Rocks in production. Charity likes single malt scotch.
©2016, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com