DOCSLIB.ORG

Why Enterprise Nosql Matters

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Why Enterprise Nosql Matters White Paper Why Enterprise NoSQL Matters By Evan Quinn, Senior Principal Analyst March 2013 This ESG White Paper was commissioned by MarkLogic and is distributed under license from ESG. © 2013 by The Enterprise Strategy Group, Inc. All Rights Reserved. White Paper: Why Enterprise NoSQL Matters 2 Contents Executive Summary ...................................................................................................................................... 3 The Alternative to Aging Enterprise Relational Databases: NoSQL Databases ............................................ 4 Requirements for Enterprise NoSQL ............................................................................................................ 5 MarkLogic Is a Proven Candidate for Enterprise NoSQL .............................................................................. 7 The Bigger Truth ........................................................................................................................................... 8 All trademark names are property of their respective companies. Information contained in this publication has been obtained by sources The Enterprise Strategy Group (ESG) considers to be reliable but is not warranted by ESG. This publication may contain opinions of ESG, which are subject to change from time to time. This publication is copyrighted by The Enterprise Strategy Group, Inc. Any reproduction or redistribution of this publication, in whole or in part, whether in hard-copy format, electronically, or otherwise to persons not authorized to receive it, without the express consent of The Enterprise Strategy Group, Inc., is in violation of U.S. copyright law and will be subject to an action for civil damages and, if applicable, criminal prosecution. Should you have any questions, please contact ESG Client Relations at 508.482.0188. © 2013 by The Enterprise Strategy Group, Inc. All Rights Reserved. White Paper: Why Enterprise NoSQL Matters 3 Executive Summary The good, old-fashioned relational database, a well-understood technology with a known list of providers for two decades, has faced disruption since the turn of the millennium, and the disruption is peaking now. The rise of cloud applications, big data analytics, mobile computing, sophisticated content and asset management solutions, and social media have pushed the once dependable relational database to the edge of, and sometimes past, its abilities. Because it was originally architected to work with hardware from yesteryear, the older relational database may struggle to take optimal advantage of the dramatic price/performance improvements and innovations found in adjunct technologies like multi-core processors and storage. Add in previously inconceivable requirements for scalability, plus the still substantial margins enjoyed by long-standing enterprise database providers, and modern database buyers have found motivation to look for fresh alternatives. In the vacuum formed between older databases and new use cases, an explosion of roughly 50 new commercial and open source databases, often referred to collectively as “NoSQL databases,” have come to market. ESG prefers to interpret the term “NoSQL” to mean “Not Only SQL” given that many of the new databases do support Structured Query Language (SQL). But suffice it to say that pent-up demand to better address post-2000 use cases has produced a throng of new database choices. Yet therein lies another, ironic, challenge for the database buyer: too much choice. Fortunately, if you require enterprise-class features in a NoSQL database, the number of choices shrinks to a few, and MarkLogic stands out as a clear leader in the “Enterprise NoSQL” category. “Enterprise NoSQL” means a database designed to deal with modern, post-2000 application use cases that also has the features to support enterprise-grade compliance; transaction processing; tools for DBAs and administrators; 24x365 availability; scalability adapting to multiple cost-effective hardware choices; and APIs and connectors for a wide variety of third-party services wanted by developers. The shorter definition: Security, policy management, availability, scalability, ACID, DBA and administrator tools, connectors and APIs. An even shorter definition: Enterprise NoSQL is a NoSQL database you would bet your business on—a database like MarkLogic. The MarkLogic database moves easily between the schema-less approach used for advanced web, rich content, and document solutions, as well as full ACID transaction processing. Its native shared-nothing architecture enables near- linear scalability across a wide variety of hardware choices, including “commodity hardware.” Its government- certified security and policy management enable fine-grained access, data privacy, and retention control. It offers a variety of high availability approaches—versus only one—for both shared disk implementations as well as shared- nothing that includes point-in-time recovery. And MarkLogic’s administration tools are API-based, offering the flexibility to fit into existing workflows and consoles, with prebuilt integration to several popular systems management tools. MarkLogic also offers specific solutions that address multi-national class needs, such as a “big data search” with support for over 200 languages, and metadata repositories used by some of the world’s largest media organizations. In the big data arena, MarkLogic offers optimized connectors to leading big data platform and visualization tools such as Hadoop, Tableau Software, and IBM Cognos. Between its true enterprise-class database capabilities, and its wide range of proven solutions, MarkLogic belongs on the short list of those database buyers who are interested in NoSQL, but not willing to sacrifice the features needed by enterprises. © 2013 by The Enterprise Strategy Group, Inc. All Rights Reserved. White Paper: Why Enterprise NoSQL Matters 4 The Alternative to Aging Enterprise Relational Databases: NoSQL Databases The relational databases enterprises have depended on for over two decades for nearly all applications are being replaced by a newer set of databases that offer data models and features more finely tuned to post-2000 applications. Given the growth of data—managing data growth rated as the number four most important IT priority reported by respondents in ESG’s recent IT spending intention survey—and pressure on costs—cost reduction initiatives rated as the number one business priority for IT cited by organizations in the same survey (see Figure 1)—the well-known lofty prices of enterprise databases have contributed to interest for alternative databases.1 The high cost of classic enterprise databases, however, isn’t just about price. Relational databases were not originally designed for the rich and pervasive content of today’s collaboration, social media, and mobile applications. The older relational model struggles with the complex queries and compute requirements associated with advanced data analytics. Thus, many of the leading business initiatives that need IT’s help today don’t marry well with the long-standing enterprise relational database, and those organizations that choose to stick with older relational models literally pay for their choice by throwing more hardware at the issue, and using workarounds. Figure 1. 2013 Business Initiatives with the Greatest Impact on IT Spending Decisions Which of the following business initiatives do you believe will have the greatest impact on your organization's IT spending decisions over the next 12-18 months? (Percent of respondents, N=540, three responses accepted) Cost reduction initiatives 44% Business process improvement initiatives 31% Security/risk management initiatives 31% Regulatory compliance 25% Providing our employees with the mobile devices and 24% applications they need to maximize productivity 0% 10% 20% 30% 40% 50% Source: Enterprise Strategy Group, 2013 NoSQL databases have stepped in as the alternatives to legacy enterprise databases. While the implication of NoSQL infers a lack of query language or data structure, in fact the dozens of NoSQL databases available in the market cover a wide range of query approaches and data models, thus “NoSQL” really means “not only SQL.” Regardless, most NoSQL databases not only offer data models lined up with more recent application types, but they are also typically designed natively to take advantage of advances in in-memory computing, storage, and virtualized infrastructures including clouds. Speed and scalability, across a variety of deployment choices, are often calling cards of NoSQL databases. 1 Source: ESG Research Report, 2013 IT Spending Intentions Survey, January 2013. © 2013 by The Enterprise Strategy Group, Inc. All Rights Reserved. White Paper: Why Enterprise NoSQL Matters 5 Yet, ESG is not comfortable recommending all NoSQL databases to enterprises and large organizations. Several of the primary reasons for ESG’s reticence are spelled out in Figure 2, which lists the most important IT priorities reported by respondents to ESG’s recent survey. Many priorities are related to security and compliance, and few NoSQL databases measure up to enterprise-class needs, and even fewer meet government required security and compliance requirements. But enterprise-class requirements do not end at security and compliance for NoSQL databases. The interest in virtualization, cloud, and private cloud suggests the need for scalability across variable and elastic infrastructures. Data backup, recovery, and business continuity
Load more

Recommended publications
  • Semantics Developer's Guide
    MarkLogic Server Semantic Graph Developer’s Guide 2 MarkLogic 10 May, 2019 Last Revised: 10.0-8, October, 2021 Copyright © 2021 MarkLogic Corporation. All rights reserved. MarkLogic Server MarkLogic 10—May, 2019 Semantic Graph Developer’s Guide—Page 2 MarkLogic Server Table of Contents Table of Contents Semantic Graph Developer’s Guide 1.0 Introduction to Semantic Graphs in MarkLogic ..........................................11 1.1 Terminology ..........................................................................................................12 1.2 Linked Open Data .................................................................................................13 1.3 RDF Implementation in MarkLogic .....................................................................14 1.3.1 Using RDF in MarkLogic .........................................................................15 1.3.1.1 Storing RDF Triples in MarkLogic ...........................................17 1.3.1.2 Querying Triples .......................................................................18 1.3.2 RDF Data Model .......................................................................................20 1.3.3 Blank Node Identifiers ..............................................................................21 1.3.4 RDF Datatypes ..........................................................................................21 1.3.5 IRIs and Prefixes .......................................................................................22 1.3.5.1 IRIs ............................................................................................22
    [Show full text]
  • Content Processing Framework Guide (PDF)
    MarkLogic Server Content Processing Framework Guide 2 MarkLogic 9 May, 2017 Last Revised: 9.0-7, September 2018 Copyright © 2019 MarkLogic Corporation. All rights reserved. MarkLogic Server Version MarkLogic 9—May, 2017 Page 2—Content Processing Framework Guide MarkLogic Server Table of Contents Table of Contents Content Processing Framework Guide 1.0 Overview of the Content Processing Framework ..........................................7 1.1 Making Content More Useful .................................................................................7 1.1.1 Getting Your Content Into XML Format ....................................................7 1.1.2 Striving For Clean, Well-Structured XML .................................................8 1.1.3 Enriching Content With Semantic Tagging, Metadata, etc. .......................8 1.2 Access Internal and External Web Services ...........................................................8 1.3 Components of the Content Processing Framework ...............................................9 1.3.1 Domains ......................................................................................................9 1.3.2 Pipelines ......................................................................................................9 1.3.3 XQuery Functions and Modules .................................................................9 1.3.4 Pre-Commit and Post-Commit Triggers ...................................................10 1.3.5 Creating Custom Applications With the Content Processing Framework 11 1.4
    [Show full text]
  • Access Control Models for XML
    Access Control Models for XML Abdessamad Imine Lorraine University & INRIA-LORIA Grand-Est Nancy, France [email protected] Outline • Overview on XML • Why XML Security? • Querying Views-based XML Data • Updating Views-based XML Data 2 Outline • Overview on XML • Why XML Security? • Querying Views-based XML Data • Updating Views-based XML Data 3 What is XML? • eXtensible Markup Language [W3C 1998] <files> "<record>! ""<name>Robert</name>! ""<diagnosis>Pneumonia</diagnosis>! "</record>! "<record>! ""<name>Franck</name>! ""<diagnosis>Ulcer</diagnosis>! "</record>! </files>" 4 What is XML? • eXtensible Markup Language [W3C 1998] <files>! <record>! /files" <name>Robert</name>! <diagnosis>! /record" /record" Pneumonia! </diagnosis> ! </record>! /name" /diagnosis" <record …>! …! </record>! Robert" Pneumonia" </files>! 5 XML for Documents • SGML • HTML - hypertext markup language • TEI - Text markup, language technology • DocBook - documents -> html, pdf, ... • SMIL - Multimedia • SVG - Vector graphics • MathML - Mathematical formulas 6 XML for Semi-Structered Data • MusicXML • NewsML • iTunes • DBLP http://dblp.uni-trier.de • CIA World Factbook • IMDB http://www.imdb.com/ • XBEL - bookmark files (in your browser) • KML - geographical annotation (Google Maps) • XACML - XML Access Control Markup Language 7 XML as Description Language • Java servlet config (web.xml) • Apache Tomcat, Google App Engine, ... • Web Services - WSDL, SOAP, XML-RPC • XUL - XML User Interface Language (Mozilla/Firefox) • BPEL - Business process execution language
    [Show full text]
  • Multi-Model Databases: a New Journey to Handle the Variety of Data
    0 Multi-model Databases: A New Journey to Handle the Variety of Data JIAHENG LU, Department of Computer Science, University of Helsinki IRENA HOLUBOVA´ , Department of Software Engineering, Charles University, Prague The variety of data is one of the most challenging issues for the research and practice in data management systems. The data are naturally organized in different formats and models, including structured data, semi- structured data and unstructured data. In this survey, we introduce the area of multi-model DBMSs which build a single database platform to manage multi-model data. Even though multi-model databases are a newly emerging area, in recent years we have witnessed many database systems to embrace this category. We provide a general classification and multi-dimensional comparisons for the most popular multi-model databases. This comprehensive introduction on existing approaches and open problems, from the technique and application perspective, make this survey useful for motivating new multi-model database approaches, as well as serving as a technical reference for developing multi-model database applications. CCS Concepts: Information systems ! Database design and models; Data model extensions; Semi- structured data;r Database query processing; Query languages for non-relational engines; Extraction, trans- formation and loading; Object-relational mapping facilities; Additional Key Words and Phrases: Big Data management, multi-model databases, NoSQL database man- agement systems. ACM Reference Format: Jiaheng Lu and Irena Holubova,´ 2019. Multi-model Databases: A New Journey to Handle the Variety of Data. ACM CSUR 0, 0, Article 0 ( 2019), 38 pages. DOI: http://dx.doi.org/10.1145/0000000.0000000 1.
    [Show full text]
  • Monitoring Marklogic Guide (PDF)
    MarkLogic Server Monitoring MarkLogic Guide 1 MarkLogic 10 May, 2019 Last Revised: 10.0-6, February, 2021 Copyright © 2021 MarkLogic Corporation. All rights reserved. MarkLogic Server Table of Contents Table of Contents Monitoring MarkLogic Guide 1.0 Monitoring MarkLogic Server .......................................................................5 1.1 Overview .................................................................................................................5 1.2 Selecting a Monitoring Tool ...................................................................................5 1.3 Monitoring Architecture, a High-level View ..........................................................6 1.4 Monitoring Tools and Security ...............................................................................6 1.5 Guidelines for Configuring your Monitoring Tools ...............................................7 1.5.1 Establish a Performance Baseline ...............................................................7 1.5.2 Balance Completeness Against Performance .............................................7 1.6 Monitoring Metrics of Interest to MarkLogic Server .............................................8 1.6.1 Does MarkLogic Have Adequate Resources? ............................................8 1.6.2 What is the State of the System Overall? ...................................................9 1.6.3 What is Happening on the MarkLogic Server Cluster Now? .....................9 1.6.4 Are There Signs of a Serious Problem? ...................................................11
    [Show full text]
  • Data Lifecycle and Analytics in the AWS Cloud
    Data Lifecycle and Analytics in the AWS Cloud A Reference Guide for Enabling Data-Driven Decision-Making DATA LIFECYCLE AND ANALYTICS IN THE AWS CLOUD AWS THE IN ANALYTICS AND LIFECYCLE DATA CONTENTS PURPOSE Contents INTRODUCTION Purpose 3 CHALLENGES 1. Introduction 4 2. Common Data Management Challenges 10 3. The Data Lifecycle in Detail 14 LIFECYCLE Stage 1 – Data Ingestion 16 INGESTION Stage 2 – Data Staging 24 Stage 3 – Data Cleansing 31 Stage 4 – Data Analytics and Visualization 34 STAGING Stage 5 – Data Archiving 44 4. Data Security, Privacy, and Compliance 46 CLEANSING 5. Conclusion 49 ANALYTICS 6. Further Reading 51 Appendix 1: AWS GovCloud 53 Appendix 2: A Selection of AWS Data and Analytics Partners 54 Contributors 56 ARCHIVING SECURITY Public Sector Case Studies Financial Industry Regulation Authority (FINRA) 9 CONCLUSION Brain Power 17 READING DigitalGlobe 21 US Department of Veterans Affairs 23 APPENDICES Healthdirect Australia 27 CONTRIBUTORS Ivy Tech Community College 35 UMUC 38 UK Home Office 40 2 © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. DATA LIFECYCLE AND ANALYTICS IN THE AWS CLOUD AWS THE IN ANALYTICS AND LIFECYCLE DATA CONTENTS PURPOSE Purpose of this guide INTRODUCTION Data is an organization’s most valuable asset and the volume and variety of data that organizations amass continues to grow. The demand for simpler data analytics, cheaper data storage, advanced predictive tools CHALLENGES like artificial intelligence (AI), and data visualization is necessary for better data-driven decisions. LIFECYCLE INGESTION The Data Lifecycle and Analytics in the AWS Cloud guide helps organizations of all sizes better understand the data lifecycle so they can optimize or establish an advanced data analytics practice in their STAGING organization.
    [Show full text]
  • BEYOND the RDBMS: WORKING with RELATIONAL DATA in MARKLOGIC Ken Tune, Senior Principal Consultant, Marklogic
    BEYOND THE RDBMS: WORKING WITH RELATIONAL DATA IN MARKLOGIC Ken Tune, Senior Principal Consultant, MarkLogic © COPYRIGHT 2016 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Agenda . Personal introduction . Motivation – the Operational Data Hub . Modeling data in MarkLogic . Three worked examples demonstrating different migration patterns . BI Tool integration . Wrap Up & Q&A SLIDE: 2 © COPYRIGHT 2016 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Introduction . Ken Tune . Senior Principal Consultant at MarkLogic for ~5 years . Background : dev lead / system architecture and design . Strong background in relational technology . Source code for this talk - https://github.com/rjrudin/marklogic-sakila-demo SLIDE: 3 © COPYRIGHT 2016 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. OVERVIEW MarkLogic as an Operational Data Hub . Integrate data from multiple heterogeneous stand-alone sources . Do more with that data in aggregate . Use extensive MarkLogic feature set . Some of those silos will be RDBMSs SLIDE: 4 © COPYRIGHT 2016 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Tables and Documents . Tables – Tabular! Document . Documents – Tree Structures – hierarchical & nested Title . Higher dimension implies greater representative power Metadata Author Section . We can intuitively transform tables into documents . Documents offer additional possibilities First Last Section Section Section Section SLIDE: 5 © COPYRIGHT 2016 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Entities and relationships . Our applications have conceptual models Association . A conceptual model has entities with different Person Person kinds of relationships Aggregation . Relational forces us to break up our model into separate tables for every 1:many relation Person Car . Sometimes makes sense, but not always Composition . We never have a choice Person Alias SLIDE: 6 © COPYRIGHT 2016 MARKLOGIC CORPORATION. ALL RIGHTS RESERVED. Documents – greater flexibility . Choose how you model relationships Person • Name .
    [Show full text]
  • Master Thesis
    Version Control of structured data: A study on different approaches in XML Master Thesis in Software Engineering ERIK AXELSSON SE´RGIO BATISTA Department of Computer Science and Engineering Division of Software Engineering Chalmers University of Technology Gothenburg, Sweden 2015 Abstract The structured authoring environment has been changing towards a decentralised form of authoring. Existing version control systems do not handle these documents ade- quately, making it very difficult to have parallel authoring in a structured environment. This study attempts to find better alternatives to the existing paradigms and tools for versioning XML documents. To achieve this, the DESMET methodology for evaluating software engineering meth- ods and tools was applied, with both a Feature Analysis and a Benchmark Analysis being performed. Concerning the feature analysis, the results demonstrate that the XML-aware tools are, as expected, better at XML specific concerns, such as considering the history of a specific node. Conversely, the non-XML-aware ones are not able to achieve good results in the XML specific concerns, but do achieve a high score when considering project maturity or general repository management features. Regarding performance, this study concludes that XML-aware tools bring a considerable overhead when compared to the non-XML-aware tools. This study concludes that the selection of an approach to versioning XML should be dependent of the priorities of the documentation project. Keywords: Structured documentation, XML, Version Control, distributed collaboration, Git, Sirix, XChronicler, temporal databases, DESMET. Acknowledgements The authors would like to thank both the academic supervisor Morgan Ericsson and examiner Matthias Tichy for their feedback and support throughout this thesis work.
    [Show full text]
  • Xquery 1 Xquery
    XQuery 1 XQuery XQuery Examples Collection Welcome to the XQuery Examples Collection Wikibook! XQuery is a World Wide Web Consortium recommendation for selecting data from documents and databases. Current Status A new release of eXist (1.4) is currently installed and under test. Please note any problems with these examples in the discussion. Recent Changes About this Project This is a collaborative project and we encourage everyone who is using XQuery to contribute their XQuery examples. All example programs must conform to the creative-commons-2.5 share-alike with attribution license agreement [1]. Execution of examples use an eXist demo server. 1. Instructors: please sign our Guest Registry if you are using this book for learning or teaching XQuery 2. Contributors: please see our Naming Conventions to ensure your examples are consistent with the textbook 3. Learners: If you are looking for an example of a specific XQuery language construct, technique or problem but can't find an example, please add a suggestion to the Examples Wanted section. Introduction 1. Background - A brief history and motivation for the XQuery standard. 2. Benefits - Why use XQuery? 3. Installing and Testing - How to install an XQuery server on your . 4. Naming Conventions - Naming standards used throughout this book. Example Scripts Beginning Examples Examples that do not assume knowledge of functions and modules. 1. HelloWorld - A simple test to see if XQuery is installed correctly. 2. FLWOR Expression - A basic example of how XQuery FLWOR statements work. 3. Sequences - Working with sequences is central to XQuery. 4. XPath examples - Sample XPath samples for people new to XML and XPath 5.
    [Show full text]
  • REST Application Developer's Guide
    MarkLogic Server REST Application Developer’s Guide 2 MarkLogic 9 May, 2017 Last Revised: 9.0-8, December 2018 Copyright © 2019 MarkLogic Corporation. All rights reserved. MarkLogic Server Version MarkLogic 9—May, 2017 Page 2—REST Application Developer’s Guide MarkLogic Server Table of Contents Table of Contents REST Application Developer’s Guide 1.0 Introduction to the MarkLogic REST API ...................................................13 1.1 Capabilities of the REST Client API ....................................................................13 1.2 Getting Started with the MarkLogic REST API ...................................................14 1.2.1 Preparation ................................................................................................14 1.2.2 Choose a REST API Instance ...................................................................15 1.2.3 Load Documents Into the Database ..........................................................15 1.2.4 Search the Database ..................................................................................16 1.2.5 Tear Down the REST API Instance ..........................................................18 1.3 REST Client API Service Summary .....................................................................18 1.4 Security Requirements ..........................................................................................21 1.4.1 Basic Security Requirements ....................................................................21 1.4.2 Controlling Access to Documents and
    [Show full text]
  • The Nosql Generation: Embracing the Document Model
    The NoSQL Generation: Embracing the Document Model May 2014 Table of Contents Introduction _______________________________________________________________ 3 The History of “NoSQL” _______________________________________________________ 3 Types of NoSQL Databases ____________________________________________________ 4 Embracing the Document Model ________________________________________________ 7 Defining Enterprise NoSQL ___________________________________________________ 10 Introduction NoSQL databases are a new generation of databases that have gained significant market traction because they solve major challenges with the volume, variety, and velocity of big data. NoSQL represents a fundamental change in thinking about how data is stored and managed that is counter to the relational database approach used for Oracle Database 12c, Oracle MySQL, Microsoft SQL Server, IBM DB2, Postgres, and many others. 1 The term “NoSQL” is a broad descriptor covering a wide range of new databases, generally broken down into four main categories: document, key-value, column-family, and graph databases. Among these categories, document databases are the best general purpose databases. Document databases have a more logical, human approach to modeling data, are generally the most flexible and easy to use, and are the most popular. Among document databases, MarkLogic differentiates itself as an “Enterprise NoSQL” database because in addition to qualifying as a NoSQL database, it has all of the critical features that enterprises need to run mission-critical applications. This means ACID transactions, high availability, disaster recovery, government grade security, elasticity and scalability, and performance monitoring tools. With MarkLogic, enterprises can embrace the document model and securely move forward into the next era of databases. The History of “NoSQL” MarkLogic is now known as an Enterprise NoSQL database, but was originally known mostly for its ability to store and search XML.
    [Show full text]
  • Marklogic® Developer Training and Support
    MarkLogic® Developer Training and Support The Developer Training and Support package is a combination • Administering MarkLogic Server – a seat for your of pre-production training and support to help you and your database administrator at a hands-on course team get the most out of MarkLogic, getting you that much that will teach you about installing, deploying, monitoring, and maintaining your MarkLogic closer to a live application. database • Six months of email and web support for two named Overview contacts in your organization. With the release of the free Developer License for MarkLogic Enterprise Edition, developers can now begin Getting Started building pre-production applications without waiting Download a free Developer License for MarkLogic for funds to be allocated for production software Enterprise Edition and begin developing and testing an licenses. The Developer Training and Support package application on the only Enterprise NoSQL database. You is a cost-effective way to help your team become more can use the software for six months, giving you plenty proficient using MarkLogic, so you can reach your goals of time to get ready before your organization needs to even sooner. buy production licenses. The Developer License includes nearly all features of Enterprise Edition and can be used Details for databases up to 1TB, which makes it easy for you to The Developer Training and Support package includes try out MarkLogic for real problems you need to solve. a full-day MarkLogic Fundamentals workshop, a seat If you’ve already started working with MongoDB, use our in two of our public training courses, and six months of MarkLogic Converter for MongoDB to move your data support, as described below.
    [Show full text]