Personal Information
Organization / Workplace
Greater Seattle Area United States
Occupation
Director of Architecture
Industry
Technology / Software / Internet
About
With the advent of enterprise-class non-relational stores like MongoDB, Cassandra, Redis, Solr, and Hadoop, the work of the data architect has become both easier and harder.
It's easier because non-relational stores can be used to take the pressure off of relational stores, as they no longer have to play roles for which they are not well-suited: event-logging, key-value blobs, limited-lifespan token tracking, poly-structured analytics, and context-based personalization.
It's harder because we now have to orchestrate software and data across platforms, tuning for availability, reliability, recovery, stability, security, and consistency. The siren song of NOSQL simplicity tempts our soft...
Likes
(10)Data Architecture Best Practices for Today’s Rapidly Changing Data Landscape
DATAVERSITY
•
5 years ago
The Chief Data Officer - quotes from data & analytics thought leaders
Mario Faria
•
9 years ago
Karen Lopez 10 Physical Data Modeling Blunders
Karen Lopez
•
9 years ago
7 Databases in 70 minutes
Karen Lopez
•
9 years ago
How to Survive as a Data Architect in a Polyglot Database World
Karen Lopez
•
6 years ago
7 Dangerous Myths DBAs Believe about Data Modeling
Embarcadero Technologies
•
8 years ago
Cloud Data Migration Strategies - AWS May 2016 Webinar Series
Amazon Web Services
•
7 years ago
Apache Hadoop In Theory And Practice
Adam Kawa
•
10 years ago
Organizational Structure and roles
jayesh.8486
•
15 years ago
STEM to STEAM: Where Art and Design meet Science, Technology, Engineering and Mathematics
Christine Miller
•
12 years ago
Personal Information
Organization / Workplace
Greater Seattle Area United States
Occupation
Director of Architecture
Industry
Technology / Software / Internet
About
With the advent of enterprise-class non-relational stores like MongoDB, Cassandra, Redis, Solr, and Hadoop, the work of the data architect has become both easier and harder.
It's easier because non-relational stores can be used to take the pressure off of relational stores, as they no longer have to play roles for which they are not well-suited: event-logging, key-value blobs, limited-lifespan token tracking, poly-structured analytics, and context-based personalization.
It's harder because we now have to orchestrate software and data across platforms, tuning for availability, reliability, recovery, stability, security, and consistency. The siren song of NOSQL simplicity tempts our soft...