(844) 500 - DATA
10190 Bannock St,
Northglenn, CO, USA
26/3/2, Amruth Nagar,
Bengaluru, India

Partnership with MarkLogic!

Apoorva is very excited to announce a partnership with MarkLogic! So, for our next blog, we’d like to share a little bit about what makes MarkLogic so great, and why we’re thrilled to be partnered with them.


MarkLogic is an enterprise NoSQL (‘Not Only’ SQL, nowadays) database. In the past we’ve mentioned some of the advantages of NoSQL databases over their relational, SQL counterparts. In particular, these benefits include a level of scalability and flexibility not readily available in relational database models. These qualities are particularly relevant to the big data challenges many businesses today face. NoSQL is necessary for companies that require database management systems that can scale and deliver performance across enormous data sets and numbers of users. Think Facebook, Google, Amazon. Of course, nowadays, NoSQL is applied much more extensively than by just the tech behemoths. In fact, most real-time web and cloud applications employ NoSQL databases.


That’s not to say that relational database management systems (RDBMS) don’t still have an important role to play in the IT world -- they do. When you have a known (or mostly known) data model, with centralized applications and structured data, where this is an emphasis on complex querying, analysis and reporting, a RDBMS can still be the best option. But, in an data-intensive environment, where there are decentralized applications receiving structured and unstructured data, which demand continuous availability and horizontal scalability, a NoSQL database is the likely solution.


But saying ‘NoSQL solution’ is about as vague as saying ‘back in the day...’  In truth, NoSQL databases can (and do!) vary a lot from one another, and NoSQL is really not a wholly descriptive term. Unlike SQL relational databases, which are all based upon tables, primary and foreign keys, and their interrelationships, there is no standard architecture for NoSQL databases. They are united simply by the fact that they are not relational databases.


Four main NoSQL database types include document store, key-value, column family store, and graph database. In a document store database each record and its associated data is considered a ‘document.’ All data associated with a particular document object is stored together, allowing unstructured data to be easily stored. We’ll develop document store databases below.


Next, there are key-value databases. These have the simplest data model of the four main NoSQL database types. Good for when most of the access to the data is done using a key, it is generally used for very specific purposes, often for caching website visits, or storing and managing user profiles and preference settings.


Column family databases rely on rows and columns in a fashion similar to a relational database. However, a column family database is capable of scaling to as many rows as necessary, and each row can have any number of columns. Again, fairly specific in its use, this type of NoSQL database is frequently employed for event monitoring and content management systems, as well as blogging platforms.


Graph databases focus on the relationships between the data, relying on nodes, edges and properties. It is fundamentally relationship-oriented and therefore excellent for managing highly connected data, and querying those connections quickly and efficiently. Given even just brief overviews of the main types of NoSQL databases, it is important to understand that NoSQL is by no means a comprehensive term, and there are very real, very appreciable reasons as to why you may select one architecture over another.


For now, we will focus predominantly on document store databases as MarkLogic is, at its core, a document store database. Among the four main NoSQL database types listed, document store databases are the most versatile, and most well-equipped for general purpose use as they are both powerful and flexible. Additionally, document store databases tend to be easy to use, and structure data in an intuitive way. When processing information, humans naturally tend to think in terms of structural hierarchies and groupings, which happens to be the structure of a document. So a document store model tends to coincide well with the human perspective. Also important to note, a document can contain all of the information typically contained in the row of a relational table. Moreover, documents, in the case of MarkLogic, can include XML, JSON, text, and large binaries (such as PDFs and Microsoft Office documents).


Document stores promote easier application development as relational modeling for semi and unstructured or aggregated data can be timely, costly, and insensitive to evolving business needs. Because document store databases don’t rely on a schema as a RDBMS will, it is more flexible and better able to adapt to changing business demands. In the case of MarkLogic, the database is ‘schema agnostic’ but ‘structure-aware’, meaning that while it does not have an established schema, one can be enforced (and quickly changed) when necessary. Also great about document stores is that all data within a document is self-contained. There is no need for foreign keys or normalization or transformation between tiers. Such factors allow this type of NoSQL database to work across a wide variety of industries including media, financial services, and healthcare.


So now you’re feeling comfortable with why you might want to use a document store NoSQL database. But why do you want to use MarkLogic, specifically? There are a number of attributes that we believe make MarkLogic superior to its competitors. To begin with, while a document store database at heart, MarkLogic offers the ability to store and manage RDF (Resource Description Framework) triples, thus incorporating some graph database capabilities. This data model, known as semantics, allows the linking of different entities based on the relationships between them in order to form triples (consisting of subject, predicate, object). Such a data model is very flexible in handling heterogeneous data, and has been leveraged to build smarter applications. MarkLogic uses RDF triples alongside their document stores to link data, provide context, and describe metadata, as well as integrate disparate data without corrupting the original source. What’s more, the use of semantics enhances MarkLogic’s search capabilities, which brings us to our next point.


Compared to many NoSQL database systems, MarkLogic has extremely advanced search capabilities. And, unlike many competitors, MarkLogic’s search is built-in as opposed to add-on. MarkLogic relies on indices to create powerful query capabilities. By indexing the data on load, it immediately becomes searchable, and multiple indices can be used at once to enhance the search. The use of semantics, as aforementioned, further augments MarkLogic’s advanced search.


Finally, for us, what really makes MarkLogic superior is the fact that it affords enterprise capabilities. Where most NoSQL databases forfeit consistency in order to gain high availability, not so with MarkLogic. Instead, MarkLogic boasts all of the features that enterprises demand to run and maintain mission critical applications -- namely ACID transactions (Atomicity, Consistency, Isolation, Durability), disaster recovery, government grade security, performance monitoring tools, and elasticity and scalability -- all without sacrificing high availability. Document store databases may be functionally suitable for a wide range of industries, but without the added enterprise benefits offered by MarkLogic, it may not be an option in areas such as financial services, healthcare, or government. ACID compliance assures that database transactions are, in fact, processed reliably, and is a prerequisite to guard against data corruption, state reads, and inconsistent data. Moreover, we’ve spoken previously to the importance of disaster recover. MarkLogic’s inclusion of enterprise features necessary to ensure maintenance of mission critical activities serve to differentiate it from the competition. Couple that with our personal experience with knowledgeable, productive and friendly team members, and we can’t help but be excited about working with them.


If you’re interested in learning more about MarkLogic, or about our partnership with them, contact us at 844-500-DATA or through our website, apoorva.com. Here at Apoorva, we are looking forward to a long and fruitful partnership!



Contact Us for a Free 3-Hour Data Strategy Consultation

Receive a free data strategy roadmap focusing on data governance, data usage, data integration, data consolidation, data privileges, and data storage.

Partnership with MarkLogic!

Apoorva is very excited to announce a partnership with MarkLogic! So, for our next blog, we’d like to share a little bit about what makes MarkLogic so great, and why we’re thrilled to be partnered with them.

Prioritizing Predictive Analytics

Data scientist, according to Glassdoor, will be the number one job in America in 2016, with over 1,700 job openings and a median base salary of $116,840. This is consistent with Indeed.com, whose 2015 first quarter data saw the number of job postings for data scientist grow 57% as compared to the analogous quarter of the previous year. It’s no surprise then, as we’ve mentioned before, that Data Scientist has been deemed the “sexiest job of the 21st century.” But the term is ambiguous at best. Asking ten different employers how they see the role of data scientist may yield ten different responses.

Disaster Recovery: Preparedness is Paramount

Business Continuity and Disaster Recovery (BCDR) plans are not new concepts. They’ve been around for decades. As their longevity might suggest, they remain extremely relevant today. In fact, having an operative BCDR plan is more pertinent than ever in the cloud-computing era. For a brief review, a business continuity plan is the tailored plan a business creates in order to continue its normal operations should a problem arise. The impending calamities that must be accounted for can be anything from natural disasters to cyber attacks to theft to sabotage.

Transitioning to a Cloud-Based Project Management Tool

Big things are happening at Apoorva! As a company, we are growing, both in employee numbers and in projects undertaken. We have recently brought on new, young blood to the team, reflecting our company’s external growth potential. We find ourselves in an exciting position to extend our unprecedented services to new clients, while expanding upon those relationships and collaborations with already existing clients.   

Apoorva is Volunteering with the Colorado Technology Association!

Apoorva is excited to be volunteering this year for the Colorado Technology Association's annual fundraiser, C-Level @ A Mile High on March 10th. This premier event helps the Colorado Technology Association's mission of fueling Colorado's technology economy and includes a C-Level celebrity auction, silent auction and live auction.

2016 Predictions: Part 3



Finally, we expect to see NoSQL use SQL as its dominant query language. The rise of the aforementioned trends of Big Data, IoT, and cloud computing, has caused NoSQL databases, such as MarkLogic and MongoDB, to gain popularity in many fast-moving technology sectors.

2016 Predictions: Part 2



These technologies aren’t all good either, though. Remember Uncle Ben’s famous advice to Peter Parker, “with great power, comes great responsibility.” With greater dependence on the Internet of Things and subsequent utilization of cloud-based applications, cybersecurity is necessarily on the forefront of many business’ minds (and if it’s not, it should be!).

2016 Predictions: Part 1

Here at Apoorva we understand the importance of staying current in the ever-changing world of Information Technology and Data Management. With that in mind, we’ve compiled a list of relevant trends moving into 2016 and beyond.

5 Essential Tasks of a SQL Server DBA - A Preview into First Week at our Client

At Apoorva, our SQL Server DBAs are trained to do the following five tasks during their first few days of joining a client. These five items are essentials for any SQL Server (or Oracle, or MySQL) DBAs. They protect our clients, they protect our jobs, and they earn client’s trust.