ATAM for NoSQL Database Selection - SEI Digital Library

1 ATAM for NoSQL Database SelectionUsing Architecture (Not Products) to Guide Database SelectionDan McCrearyKelly-McCreary & AssociatesNew NoSQL databases offer more options to the Database architect. Selecting the right NoSQL Database for your project has become a nontrivial task. Yet selecting the right Database can result in huge cost savings and increased agility. This presentation will show how the Architecture Tradeoff Analysis Method (ATAM) can be applied to objectively select the best Database architecture for a project. We review the core NoSQL Database architecture patterns (key-value stores, column-family stores, graph databases, and document databases) and then present examples of using quality trees to score business problems with alternative architectures.

2 We ll address creative ways to use combinations of NoSQL architectures, cloud Database services, and frameworks such as Hadoop, HDFS, and MapReduce to build back-end solutions that combine low operational costs and horizontal scalability. The presentation includes real-world case studies of this Description2 Kelly-McCreary & Associates How I got into using ATAM for Database Selection Background as of 2006 Worked for Steve Jobs at NeXT Object-oriented development Objective-C, Java Strong focus on object-relational mapping DBKit, WebObjects, Hibernate, Oracle, Sybase, MS-SQL Server 7 years doing XML (CriMNet), Metadata Registries (ISO/IEC 11179) and Semantics (RDF, OWL etc.)

3 My Story3 Kelly-McCreary & Associates4 Kelly-McCreary & Associates5 Kelly-McCreary & Associates6 Kelly-McCreary & Associates7 Kelly-McCreary & Associates8 Kelly-McCreary & AssociatesFour Translations9 Copyright 2010 Dan McCreary & Associates T1 HTML into Java Objects T2 Java Objects into SQL Tables T3 Tables into Objects T4 Objects into HTMLT1T4T2T3 Object MiddleTierRelationalDatabaseWeb BrowserKurt's Suggestionstore($collection, $file-name, $data)10 Copyright 2010 Dan McCreary & AssociatesWeb BrowserSaveWeb FormUse aNative XML Database !Kurt CagleeXist-dbZero Translation XML lives in the web browser (XForms) REST interfaces XML in the Database (Native XML, XQuery) XRXWeb Application Architecture No translation!

4 11 Copyright 2010 Dan McCreary & AssociatesWeb BrowserXML databaseXFormsDatabase Tradeoff AnalysisMy Way 10,000 lines of code to break CRV XML document into Java component and use Hibernate to store each element into columns of tables 45 SQL inserts store 20 joins to extract Six months Four developers (Java, SQL, DBA, Project Manager)Kurt's Way One line of codes to store CRB One day to write One week to test 100x increase in agility12 Kelly-McCreary & AssociatesThe Paradigm Shift13 Kelly-McCreary & Associates2006 RDBMSs are the onlyway to store enterprisedataThere are manyways to store enterprise data and if you pick the right one your agilitycan go up x1.

5 000 Reality Sets InWhat I wanted Objectivearchitecture analysis Fairlyweigh the pros and cons of each alternative Be surrounded by people that know the strengths and weakness of manyalternativesWhat I got Architecture decisions driven by an RDBMS license Architecture decisions made by one person with limited exposure to alternatives Architecture decisions made by lack of knowledge Architecture by fearof the unknown14 Kelly-McCreary & AssociatesEvaluating Software Architectures: Methods and Case Studiesby Paul Clements, Rick Kazman, and Mark Klein Addison-Wesley, 2001 Key Book for ATAM15 Kelly-McCreary & AssociatesHow Important is the Database ?

6 16 Kelly-McCreary & AssociatesDatabaseUser Interface10%-20%80%-90%Reference Utility Tree from Book17 Kelly-McCreary & AssociatesNote: Mostly Database IssuesAnger, Wiki, Conference, Book18 Kelly-McCreary & Associates2011, 2012 NoSQL is real and it s here to stayRDBMS vs. #q= NoSQL %2C%20rdbms&date=1%2F2009%2051m& cmpt=qRDBMSNoSQLG oogle Trends19 Kelly-McCreary & AssociatesBefore NoSQL20 Kelly-McCreary & AssociatesRelationalAnalytical (OLAP)After NoSQLR elationalAnalytical (OLAP)Key-ValueColumn-FamilyDocumentGrap hkeyvaluekeyvaluekeyvaluekeyvalue21 Column-FamilyKelly-McCreary & high level all six major architectures (SQL and NoSQL ) Database architecture products that support the architecture secondSuggested Process22 Kelly-McCreary & AssociatesKey Finding the right tool for the job23 Kelly-McCreary & AssociatesThe Problem.

7 Many possible Solutions:What tool will have the best fit? Multiple tools? One item vs. many?Architecture Selection Don't underestimate the role of marketingto promote good architecture!24 Business UnitDevelopersOperationsMake it easy tocreate and maintain codeMake it easy tomonitor and scaleMake it easy touse and extendArchitecture SelectionTeamProvide long-term competitive advantageMarketingArchitectureKelly-McCr eary & AssociatesSelection ProcessGather AllBusinessRequirementsFind ArchitecturallySignificant RequirementsScore Effort for Each Requirement for Each ArchitectureTotal Effort forEach ArchitectureSelect TopFour ArchitecturesBusiness UnitMarketingArchitecture25 Kelly-McCreary & AssociatesUse Case Driven Difficulty Analysis architecture-score-card.

8 Not a product score card!26 Kelly-McCreary & AssociatesArchitecturally Significant Features27 A requirement that drives overall architecture Requires experts to know when a requirement is significantRRRRRRRRRRRRRRRRRRRRRRA rchitecturallySignificantRequirementRNor malRequirementRRRRRRRRRRRK elly-McCreary & AssociatesQuality Attribute Utility Tree28 Kelly-McCreary & AssociatesVariations Used Change focus from "Performance" to "Scalability" Change "Modifiability" to "Agility" Increased emphasis on: Big Data Searchability Monitorability Supportability Affordability29 Kelly-McCreary & AssociatesATAM Process Flow30 BusinessDriversQualityAttributesUserStor iesAnalysisArchitecturePlanArchitectural ApproachesArchitecturalDecisionsTradeoff sSensitivityPointsNon-RisksRisksRisk ThemesDistilled infoImpactsKelly-McCreary & AssociatesSample Utility Tree Each topic (Quality Attribute) helps focus the discussion of a Selection team The topics vary from project to project Big Data projects focus on "Scalability" and "Findability" etc.

9 Objective ranking of requirements before you begin talking about architecture alternatives31 AvailabilityScalabilityMaintainabilityAf fordabilityInteroperabilitySustainabilit ySecurityPortabilityFindabilityKelly-McC reary & Associates The qualityof the fit is driven by the quality of each finger's fit If one finger doesn t fit the entire glove has a poor fit "Quality trees" help us evaluate the overall fitness of a problem and solution Removes focus on a single dimensionHand in Glove32 Kelly-McCreary & AssociatesFinding the right metaphor33 Customer ACustomer BCustomer CThis customer is running a report that takes a long time to run on a single system.

10 If we used a NoSQL solution the report would be evenly distributed on all servers and runs in 1/12 the is like the situation when many people are forced to go to the longest line even when other agents are not UtilizationAirline CheckinKelly-McCreary & Associates Requirements by threat type (DOS, Injection, Internal, Social Engineering)Change in focus of Security34 Kelly-McCreary & AssociatesSecurityAuthenticationAuthoriz ationAuditEncryptionValidating usersGranting access rights to resourcesWho changed what and whenEncrypting/signing data within a Database The ability to share code between other NoSQL databases (even within the same type) is verylimitedThe Big Problem.