The document discusses MarkLogic, a document-oriented NoSQL database, highlighting its features like a universal index, support for ad hoc queries, and geospatial capabilities. It emphasizes the database's architecture, which includes partitioning for ease of use and scalability, along with its application in managing structured and semi-structured data. The content also touches on MarkLogic's unique security model, durability through journaling, and offers resources for developers and job opportunities.

1. MarkLogic Developer CommunityNoSQL Frankfurt, 2010Awesome document-oriented NoSQL databaseBeyond NoSQLwith MarkLogicThe Universal Indexand

2. nunojobnuno.job@marklogic.com@dscape| nunojob.com

3. how??Ad hocStructurePredefinedIDMSAd hocPredefinedQueries

4. Indexes!indexes!so… filter map reduce !?well… sort of…flickr.com/ayalan

5. divide and conquerlevel of abstraction: ease of usedatabaseconsistent-hashing-like thingypartition2partition3partition1standa group of treesmakes sense to have indexes in the same place

6. 1st index resolution2nd get documentsshared-nothing clusterE Host 1E Host 3E Host 2AppServerSame Code-baseDataD Host 4D Host 5D Host 6D Host kHA&DRpartition1partition2partition3partitionmpartition4

7. universal indexRange IndexesTermTerm List“accelerating”123, 127, 129, 152, 344, 791 . . . “creation”122, 125, 126, 129, 130, 167 . . .“content”123, 126, 130, 142, 143, 167 . . .“application”123, 130, 131, 135, 162, 177 . . . “agility”Document References126, 130, 167, 212, 219, 377 . . .<article>. . . <article> / <title>. . . 126, 130, 167, …product: MarkLogicGeospatial

8. semi structuredarticletitleparagraphget tables from computer science articles that include a title with word “content” but not the word “agility”informationun-ordered listmetadatastructureparentchildparagraphtablefull textfooter

9. universal indexin kelly speak: zippy-ingRange IndexesTermTerm List“accelerating”123, 127, 129, 152, 344, 791 . . . “creation”122, 125, 126, 129, 130, 167 . . .“content”123, 126, 130, 142, 143, 167 . . .“application”123, 130, 131, 135, 162, 177 . . . “agility”Document References126, 130, 167, 212, 219, 377 . . .<article>122, 125, 126, 129, 130, 143, 167<article> / <title>122, 125, 126, 129, 130, 167 . . .126, 130, 167, …product: MarkLogicGeospatial

10. wait a minute…DirectoriesExclusive, hierarchical, analogous to file system, map to URICollectionsSet-based, N:N relationshipSecurityInvisible to your app

11. universal indexRange IndexesTermTerm List“accelerating”123, 127, 129, 152, 344, 791 . . . “creation”122, 125, 126, 129, 130, 167 . . .“content”123, 126, 130, 142, 143, 167 . . .“application”123, 130, 131, 135, 162, 177 . . . “data base”Document References126, 130, 167, 212, 219, 377 . . .<article>. . . <article> / <title>. . . 126, 130, 167, …product: MarkLogicDirectory: /articles/Collection: CSRole:Editor + Action:ReadGeospatial

12. throughputin memory stand(s)durability: journalflickr.com/kt

13. mvccappend only database, use sys-timestampsto know which document is currentlyavailableand the marklogic time machinedeleteupdate(could also be create)createSystemtimestampquery

14. too good to be true?try us out… free version available!developer.marklogic.com/productsmarkmail.orgpairs.demo.marklogic.comheatmap.demo.marklogic.combit.ly/ml-demoflickr.com/nattu

15. questions?Love NoSQLdatabases?Want to change the world?We are hiring!!spkr8.com/t/4590Feedbacknuno.job@marklogic.com

16. Open-source, closed development?RESTMobileXQuery and why it’s awesome!not coveredbut conversations are welcome!App Server + Search + DatabaseScalable ACID transactionsXML vs. JSON ?Merging / CompactionRelevanceMVCCReverse IndexesAlertingHigh Order FunctionsGeospatial queriesCo-occurrenceMeta programmingDocument databases