<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by SlicingDice Team on Medium]]></title>
        <description><![CDATA[Stories by SlicingDice Team on Medium]]></description>
        <link>https://medium.com/@slicingdice?source=rss-45dd2f3ce3c0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*akpFuD9Oa2KoNbiaCuwKvQ.png</url>
            <title>Stories by SlicingDice Team on Medium</title>
            <link>https://medium.com/@slicingdice?source=rss-45dd2f3ce3c0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 05:11:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@slicingdice/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Concepts, techniques and papers to build a time-series database.]]></title>
            <link>https://medium.com/slicingdice-com-blog/want-to-build-a-new-time-series-database-start-here-d4c3fd1517b1?source=rss-45dd2f3ce3c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4c3fd1517b1</guid>
            <category><![CDATA[slicingdice]]></category>
            <category><![CDATA[timeseries]]></category>
            <category><![CDATA[big-data]]></category>
            <category><![CDATA[data-warehouse]]></category>
            <category><![CDATA[database]]></category>
            <dc:creator><![CDATA[SlicingDice Team]]></dc:creator>
            <pubDate>Sat, 29 Apr 2017 18:55:16 GMT</pubDate>
            <atom:updated>2018-05-23T12:03:34.614Z</atom:updated>
            <content:encoded><![CDATA[<p>Below is a list of many concepts, books and techniques that helped us learn when developing <a href="https://blog.slicingdice.com/slicingdice-uncovered-part-2-s1search-33d2240a96c1">S1search</a>, the database engine that powers <a href="https://www.slicingdice.com/">SlicingDice</a>.</p><p>We all know that developing a database is one of the craziest things to do nowadays (although <a href="https://medium.com/@otoolep/what-i-learned-from-programming-databases-bb7f650079bb#.hcyz0eeit">highly talented developers that have done it before recommend the experience</a>). This happens as not only there are <a href="http://db-engines.com/en/ranking">plenty of well established solutions</a> in the market, but also because it’s really challenging technically speaking. So we are trying to give a little help here.</p><h3>Important Concepts</h3><p>Here we list some important topics about database architecture, consistency concepts and compression techniques. They aren’t ranked nor ordered in any kind of importance or priority.</p><h4>— <strong>Architecture concepts</strong></h4><ul><li><a href="https://en.wikipedia.org/wiki/Client%E2%80%93server_model">Client-Server Architecture</a></li><li><a href="https://en.wikipedia.org/wiki/Shared_nothing_architecture">Shared-nothing Architecture</a></li><li><a href="https://people.eecs.berkeley.edu/~rcs/research/interactive_latency.html">Computation Latency Numbers</a></li></ul><h4><strong>— Database-related concepts</strong></h4><ul><li><a href="https://en.wikipedia.org/wiki/Column-oriented_DBMS">Column-oriented database</a></li><li><a href="https://en.wikipedia.org/wiki/Eventual_consistency">Eventual Consistency</a></li><li><a href="https://en.wikipedia.org/wiki/ACID">ACID</a></li><li><a href="https://en.wikipedia.org/wiki/Shard_(database_architecture)">Shard</a></li><li><a href="https://en.wikipedia.org/wiki/Inverted_index">Inverted Index and Posting Lists</a></li><li><a href="https://en.wikipedia.org/wiki/Bitwise_operation">Bitwise Operations</a></li><li><a href="https://en.wikipedia.org/wiki/Linked_data_structure">Linked Data Structure</a></li><li><a href="https://en.wikipedia.org/wiki/Binary_tree">Binary Tree</a></li><li><a href="https://en.wikipedia.org/wiki/Bitmap_index">Bitmap Index</a></li><li><a href="https://en.wikipedia.org/wiki/Skip_list">Skip Lists</a></li><li><a href="https://en.wikipedia.org/wiki/Consistent_hashing">Consistent Hashing</a></li></ul><h4><strong>— Database compression concepts/techniques</strong></h4><ul><li><a href="https://en.wikipedia.org/wiki/Run-length_encoding">Run-length Encoding</a></li><li><a href="https://en.wikipedia.org/wiki/Dictionary_coder">Dictionary Encoding</a></li><li><a href="https://en.wikipedia.org/wiki/Delta_encoding">Delta Encoding</a></li><li><a href="https://en.wikipedia.org/wiki/Bitmap_index#Compression">Bitmap Encoding</a></li><li><a href="http://roaringbitmap.org/">Roaring Bitmap</a></li></ul><h3>Courses, Books and others</h3><p>Below are some courses, books, videos and conferences related to database development (mostly time-series). They aren’t ranked nor ordered in any kind of importance or priority.</p><h4><strong>— Courses</strong></h4><ul><li><a href="https://lagunita.stanford.edu/courses/DB/2014/SelfPaced/about">Stanford SQL Course</a></li><li><a href="https://open.hpi.de/courses/imdb2017">In-Memory Data Management 2017</a></li><li><a href="https://15721.courses.cs.cmu.edu/spring2018/schedule.html">CMU course on Advanced Database Systems</a></li><li><a href="https://www.youtube.com/watch?v=2SUBRE6wGiA&amp;list=PLSE8ODhjZXjY0GMWN4X8FIkYNfiu8_Wl9&amp;index=1">CMU Time Series Database Lectures</a></li><li><a href="https://www.youtube.com/watch?v=GkgDDs9EJUw&amp;list=PLSE8ODhjZXjakeQR57ZdN5slUu2oPUr1Y">CMU The Databaseology Lectures</a></li><li><a href="https://www.youtube.com/playlist?list=PLdQddgMBv5zHcEN9RrhADq3CBColhY2hl">Principles of Database Management</a></li></ul><h4><strong>— Books</strong></h4><ul><li><a href="http://www.pdbmbook.com/">Principles of Database Management</a></li><li><a href="http://nlp.stanford.edu/IR-book/html/htmledition/irbook.html">Introduction to Information Retrieval</a></li><li><a href="https://www.amazon.com/Refactoring-Databases-Evolutionary-Database-Design/dp/0321293533/">Refactoring Databases: Evolutionary Database Design</a></li><li><a href="https://www.amazon.com/dp/1558609202/">Joe Celko’s Trees and Hierarchies in SQL for Smarties</a></li><li><a href="https://www.amazon.com/Data-Structures-Algorithms-Java-2nd/dp/0672324539">Data Structures and Algorithms in Java</a></li><li><a href="https://www.amazon.com/Database-System-Concepts-Abraham-Silberschatz/dp/0073523321">Database System Concepts</a></li><li><a href="https://www.amazon.com/Data-Warehouse-Toolkit-Complete-Dimensional/dp/0471200247/">The Data Warehouse Toolkit</a></li></ul><h4><strong>— Database related Videos</strong></h4><ul><li><a href="https://www.youtube.com/user/jensdit/videos">Jens Dittrich Videos</a></li><li><a href="https://www.youtube.com/watch?v=hwHpd20NciE">The Architecture of a Distributed Analytics and Storage Engine for Massive Time-Series Data</a></li></ul><h4><strong>— Conferences</strong></h4><ul><li><a href="http://www.vldb.org/conference.html">Very Large Databases</a></li><li><a href="https://imcsummit.org/">The In-Memory Computing Summits</a></li></ul><h3>Papers, lots of great papers</h3><p>Below are some database architecture and compression papers. They aren’t ranked nor ordered in any kind of importance or priority.</p><h4><strong>— Some Interesting Database Papers</strong></h4><ul><li><a href="https://www.usenix.org/system/files/conference/fast16/fast16-papers-andersen.pdf">Optimizing Storage System Design for Timeseries Processing</a> [PDF]</li><li><a href="http://db.csail.mit.edu/pubs/abadi-column-stores.pdf">The Design and Implementation of Modern Column-Oriented Database Systems</a> [PDF]</li><li><a href="https://arxiv.org/pdf/1209.6495.pdf">Comparison of Advance Tree Data Structures</a> [PDF]</li><li><a href="http://dl.acm.org/citation.cfm?doid=2043652.2043655">Designing Fast Architecture-Sensitive Tree Search on Modern Multicore/Many-Core Processors</a></li><li><a href="http://static.druid.io/docs/druid.pdf">Druid — A Real-time Analytical Data Store</a> [PDF]</li><li><a href="http://www.vldb.org/pvldb/vol8/p1816-teller.pdf">Gorilla: A Fast, Scalable, In-Memory Time Series Database</a> [PDF]</li><li><a href="https://research.fb.com/wp-content/uploads/2016/11/scuba-diving-into-data-at-facebook.pdf">Scuba: Diving into Data at Facebook</a> [PDF]</li><li><a href="http://www.vldb.org/pvldb/vol9/p1401-chen.pdf">The MemSQL Query Optimizer: A modern optimizer for real-time analytics in a distributed database</a> [PDF]</li><li><a href="http://www.vldb.org/pvldb/vol9/p1413-lakshman.pdf">Nitro: A Fast, Scalable In-Memory Storage Engine for NoSQL Global Secondary Index</a> [PDF]</li><li><a href="http://www.vldb.org/pvldb/vol9/p1437-mishra.pdf">Accelerating Analytics with Dynamic In-Memory Expressions</a> [PDF]</li><li><a href="https://sdm.lbl.gov/~kewu/ps/LBNL-48975.pdf">A Performance Comparison of bitmap indexes</a> [PDF]</li><li><a href="https://wiki.apache.org/lucene-java/LucenePapers">Check Lucene design papers too</a></li></ul><h4><strong>— Some Interesting Data Compression Papers</strong></h4><ul><li><a href="http://dl.acm.org/citation.cfm?id=1142548">Integrating Compression and Execution in Column-Oriented Database Systems</a></li><li><a href="http://dl.acm.org/citation.cfm?id=2685297">Optimal Space-time Tradeoffs for Inverted Indexes</a></li><li><a href="http://userpages.umbc.edu/~zhchen/papers/sigmod01-camera.pdf">Query Optimization In Compressed Database Systems</a> [PDF]</li><li><a href="http://dl.acm.org/citation.cfm?id=357174">Compact Storage of Binary Trees</a></li><li><a href="http://www.vldb.org/conf/2006/p846-apaydin.pdf">Approximate Encoding for Direct Access and Query Processing over Compressed Bitmaps</a> [PDF]</li><li><a href="http://dl.acm.org/citation.cfm?id=1141398">An Accuracy-Aware Compression Technique for Multidimensional Data Cubes</a></li><li><a href="http://dl.acm.org/citation.cfm?id=2628252">Optimizing Query Execution for Variable-Aligned Length Compression of Bitmap Indices</a></li><li><a href="http://dl.acm.org/citation.cfm?id=1367550">Performance of Compressed Inverted List Caching in Search Engines</a></li><li><a href="http://dl.acm.org/citation.cfm?id=2484079">Document Identifier Reassignment and Run-Length-Compressed Inverted Indexes for Improved Search Performance</a></li><li><a href="http://dl.acm.org/citation.cfm?id=2063628">Factorization-based Lossless Compression of Inverted Indices</a></li><li><a href="http://dl.acm.org/citation.cfm?id=564416">Compression of Inverted Indexes For Fast Query Evaluation</a></li><li><a href="https://wiki.apache.org/lucene-java/LucenePapers">Check Lucene compression papers too</a></li></ul><h3>Other databases to look for inspiration</h3><ul><li><a href="https://github.com/apache/arrow/">Apache Arrow</a></li><li><a href="https://drill.apache.org/">Apache Drill</a></li><li><a href="https://lucene.apache.org/core/">Apache Lucene</a> (not a database per se, but great inspiration)</li><li><a href="https://parquet.apache.org/">Apache Parquet</a></li><li><a href="https://www.usenix.org/system/files/conference/fast16/fast16-papers-andersen.pdf">BTrDB paper</a></li><li><a href="http://www.cityzendata.com/">Cityzen Data</a></li><li><a href="http://druid.io/">Druid</a></li><li><a href="https://www.elastic.co/guide/en/elasticsearch/guide/current/index.html">ElasticSearch</a></li><li><a href="http://infiniflux.com/">Infiniflux</a></li><li><a href="https://kx.com/products.php">kdb+</a></li><li><a href="https://github.com/linkedin/pinot/wiki">Pinot</a></li><li><a href="http://gopulsar.io/">Pulsar</a></li><li><a href="https://www.rocana.com/">Rocana</a></li><li><a href="http://www.snappydata.io/">SnappyData</a></li><li><a href="https://www.tempoiq.com/">TempoIQ</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4c3fd1517b1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slicingdice-com-blog/want-to-build-a-new-time-series-database-start-here-d4c3fd1517b1">Concepts, techniques and papers to build a time-series database.</a> was originally published in <a href="https://medium.com/slicingdice-com-blog">SlicingDice.com Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Challenges on Build vs. Manage vs. Use]]></title>
            <link>https://medium.com/slicingdice-com-blog/challenges-on-build-vs-manage-vs-use-2b20edeb077c?source=rss-45dd2f3ce3c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b20edeb077c</guid>
            <category><![CDATA[big-data]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[data-warehouse]]></category>
            <category><![CDATA[big-data-analytics]]></category>
            <dc:creator><![CDATA[SlicingDice Team]]></dc:creator>
            <pubDate>Fri, 28 Apr 2017 15:34:26 GMT</pubDate>
            <atom:updated>2017-05-29T18:29:12.487Z</atom:updated>
            <content:encoded><![CDATA[<p>There are many technical and business challenges when building and managing a data warehouse. Below we address in a more conceptual way some of the challenges we usually see inside corporations (of all sizes).</p><p>At <a href="https://www.slicingdice.com/">SlicingDice</a> we divide our potential customers for the data warehouse and analytics database into four main market segments:</p><ul><li>Companies that prefer (or like) to <strong>build their own solutions</strong>;</li><li>Companies that choose (or like) to <strong>manage 3rd party solutions</strong>;</li><li>Companies that <strong>have to build their own solutions (core business)</strong>;</li><li>Companies that <strong>want to use 3rd party solutions that simply works</strong>;</li></ul><p>Excluding companies that have their core business around data collection and processing, our daily interactions with the market indicates that the majority of the companies are still stuck on the first two segments, although the fourth group is growing really fast.</p><p>We noticed that most of the companies that are still on the first two segments are there because they were so focused on their day to day tasks that they never stopped to review this paradigm and to make this question: “<strong>do we really want to spend our company resources and our team’s time building, managing or tuning a data warehouse? Is this our core business?</strong>”</p><p>Once they ask this question, most of them realizes that, unless you are a very large corporation like Twitter or Google with a lot of resources or you have a very specific necessity/use case (core business), nowadays it doesn’t make so much sense to reinvent the wheel inside each company.</p><p>There are plenty of data warehouse as a service platforms like <a href="https://blog.slicingdice.com/r/?url=https%3A%2F%2Fwww.slicingdice.com">SlicingDice</a> and <a href="https://blog.slicingdice.com/r/?url=https%3A%2F%2Fcloud.google.com%2Fbigquery%2F">Google BigQuery</a> where you simply need to send your data and later make your queries, very fast and in a cost-effective way, so why build everything internally or even manage servers like Amazon Redshift?</p><h4>What do you expect for your company / team future?</h4><p>As the <a href="https://blog.slicingdice.com/r/?url=https%3A%2F%2Fwww.information-management.com%2Fnews%2Finfrastructure-scaling-and-staffing-top-barriers-to-analytics-success">recent study from 451 Research</a> on machine data analytics shows:</p><blockquote>“When asked what challenges they have faced with achieving hoped-for results with analytics projects, respondents cited <strong>infrastructure requirements (cited by 36 percent)</strong>, <strong>scaling challenges (cited by 33 percent)</strong>, <strong>staffing requirements (cited by 33 percent)</strong>, slow analytics (cited by 32 percent), expense (cited by 31 percent) and <strong>technical challenges (cited by 30 percent)</strong>.”<br><strong><em>Source: </em></strong><a href="https://blog.slicingdice.com/r/?url=https%3A%2F%2Fwww.information-management.com%2Fnews%2Finfrastructure-scaling-and-staffing-top-barriers-to-analytics-success"><em>Information Management</em></a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*z4KsfzLT1nxMYSKP4-XuBA.png" /></figure><p>On top that, the <strong>IT talent shortage is a global reality and will continue to be</strong>, so specialized professionals that can build or even manage a data warehouse will become increasingly difficult to find, hire and retain.</p><h4>What are the companies from the fourth segment doing?</h4><p>They are the ones that “<strong>want to use 3rd party solutions that simply works</strong>”, so they can focus on their core business.</p><p>Their movement are totally aligned to <strong>Gartner’s</strong> vision published on their latest<strong> </strong><a href="https://blog.slicingdice.com/r/?url=https%3A%2F%2Fwww.gartner.com%2Fdoc%2F3614317%2Fmagic-quadrant-data-management-solutions"><strong>Magic Quadrant for Data Management Solutions for Analytics</strong></a><strong> (February 2017):</strong></p><blockquote>“More organizations <strong>are considering cloud IaaS or PaaS as the means of deploying their analytical environments.</strong> […] <strong>Cloud solutions are also challenging the traditional positioning of appliances</strong>, which is causing further disruption for traditional data warehouse vendors.”</blockquote><h4>What the future looks like for companies of the first two segments?</h4><p>From a technical standpoint, we believe that platforms like <a href="https://www.slicingdice.com/">SlicingDice</a> and BigQuery will continue to become more flexible in terms of data types and analysis it can support, while still getting faster, easier and cheaper.</p><p>As stated before, considering that the <strong>IT talent shortage is a global reality and will continue to be</strong>, from a market and business standpoint we believe companies from all sizes will continue to <em>“outsource”</em> their data warehouse operation to specialized providers like SlicingDice. That way their teams can focus entirely on extracting value and insights out of the data, instead of spending time building or managing a data warehouse technology.</p><h4>Not sure if you should Build, Manage or simply Use a data warehouse?</h4><p><a href="https://blog.slicingdice.com/r/?url=https%3A%2F%2Fcalendly.com%2Fslicingdice%2Fdev15min%2F"><strong>Click here and schedule</strong></a> a 15-minute talk with our <strong>developers</strong>, so we can evaluate your case together or <a href="https://blog.slicingdice.com/r/?url=https%3A%2F%2Fwww.slicingdice.com%2Ffaq-and-contact">let’s chat online now</a>.</p><h4>Why SlicingDice?</h4><p>Developers want to store and query their data, but they hate having to manage complex data infrastructure, so <strong>we do it for them</strong>.<br>All they have to do is simply store and query billions of <strong>real-time and historical data,</strong> <strong>without managing any infrastructure</strong>.</p><p>Store your data and make <strong>fast queries</strong> using our <a href="https://docs.slicingdice.com/docs/quickstart-guide"><strong>simple API</strong></a> or any of our clients available in <a href="https://github.com/SlicingDice/slicingdice-python"><strong>Python</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-ruby"><strong>Ruby</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-javascript"><strong>JavaScript</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-go"><strong>Go</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-java"><strong>Java</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-dot-net"><strong>.NET/C#</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-php"><strong>PHP</strong></a>, and <a href="https://github.com/SlicingDice/slicingdice-arduino"><strong>Arduino</strong></a>.</p><p><strong>High availability?</strong><br>You don’t need to worry. We always replicate and backup your data <strong>on three different datacenters</strong>, located in <strong>France, Canada</strong> and <strong>Germany</strong>.</p><p><strong>Query speed?</strong><br>If any query takes <strong>longer than 10 seconds to complete</strong>, no matter its complexity or data size, you receive a <strong>10¢ discount</strong> on your account for each one. We believe ensuring fast queries is <strong>our responsibility, not yours</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b20edeb077c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slicingdice-com-blog/challenges-on-build-vs-manage-vs-use-2b20edeb077c">Challenges on Build vs. Manage vs. Use</a> was originally published in <a href="https://medium.com/slicingdice-com-blog">SlicingDice.com Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why build a “Serverless” Data Warehouse?]]></title>
            <link>https://medium.com/slicingdice-com-blog/why-a-serverless-data-warehouse-ae3b00146c26?source=rss-45dd2f3ce3c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae3b00146c26</guid>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[slicingdice]]></category>
            <category><![CDATA[serverless-architecture]]></category>
            <category><![CDATA[big-data-analytics]]></category>
            <category><![CDATA[data-warehouse]]></category>
            <dc:creator><![CDATA[SlicingDice Team]]></dc:creator>
            <pubDate>Tue, 25 Apr 2017 00:52:59 GMT</pubDate>
            <atom:updated>2017-05-29T18:27:47.703Z</atom:updated>
            <content:encoded><![CDATA[<p>Is “serverless” just a temporary trend or companies are really adopting it?</p><h4>What does “serverless” actually means?</h4><blockquote>“The name “serverless computing” is used because the business or person that owns the system does not have to purchase, rent or provision servers or virtual machines for the back-end code to run on.”<br><strong><em>Source:</em></strong><em> </em><a href="https://en.wikipedia.org/wiki/Serverless_computing"><em>Wikipedia</em></a></blockquote><p>In the context of a data warehouse, serverless means being able to <strong>simply store and query your data,</strong> without having to purchase, rent, provision or manage<strong> any infrastructure or software licensing.</strong></p><h3>So, should you use a Serverless Data Warehouse?</h3><h4>Is your company Google or Twitter?</h4><p>Unless you are a very large corporation like Twitter or Google with a lot of resources or you have a very specific necessity/use case, nowadays it doesn’t make so much sense to reinvent the wheel inside each company.</p><p>So the main reason for a “serverless” data warehouse is actually the answer to this question: “<strong>do you really want to spend your company resources and your team’s time building, managing or tuning a data warehouse?</strong>”</p><p>You don’t really have to, there are plenty of data warehouse as a service platforms like <a href="https://www.slicingdice.com/">SlicingDice</a> and <a href="https://cloud.google.com/bigquery/">Google BigQuery</a> where you simply need to send your data and later make your queries, very fast and in a cost-effective way, so why build internally or even manage servers like Amazon Redshift?</p><h4>Is your team ready to build or manage it?</h4><p>As the <a href="https://www.information-management.com/news/infrastructure-scaling-and-staffing-top-barriers-to-analytics-success">recent study from 451 Research</a> on machine data analytics shows:</p><blockquote>“When asked what challenges they have faced with achieving hoped-for results with analytics projects, respondents cited <strong>infrastructure requirements (cited by 36 percent)</strong>, <strong>scaling challenges (cited by 33 percent)</strong>, <strong>staffing requirements (cited by 33 percent)</strong>, slow analytics (cited by 32 percent), expense (cited by 31 percent) and <strong>technical challenges (cited by 30 percent)</strong>.”<br><strong><em>Source: </em></strong><a href="https://www.information-management.com/news/infrastructure-scaling-and-staffing-top-barriers-to-analytics-success"><em>Information Management</em></a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*z4KsfzLT1nxMYSKP4-XuBA.png" /></figure><p>On top that, the <strong>IT talent shortage is a global reality and will continue to be</strong>, so specialized professionals that can build or even manage a data warehouse will become increasingly difficult to find, hire and retain.</p><h4>Is anybody really adopting it?</h4><p>As you can see in the <a href="https://g.co/trends/b4jpq">Google Trends graph</a> below, the “serverless” concept is growing really fast and in parallel with serverless data warehouse solutions like Google BigQuery.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*ZJNd0F2AP4lU3W-l2RbFPw.png" /></figure><p>Also, as <strong>Gartner</strong> states on their latest<strong> </strong><a href="https://www.gartner.com/doc/3614317/magic-quadrant-data-management-solutions"><strong>Magic Quadrant for Data Management Solutions for Analytics</strong></a><strong> (February 2017):</strong></p><blockquote>“More organizations <strong>are considering cloud IaaS or PaaS as the means of deploying their analytical environments.</strong> […] <strong>Cloud solutions are also challenging the traditional positioning of appliances</strong>, which is causing further disruption for traditional data warehouse vendors.”</blockquote><h4>What the future looks like?</h4><p>From a technical standpoint, we believe that platforms like <a href="https://www.slicingdice.com/">SlicingDice</a> and BigQuery will continue to become more flexible in terms of data types and analysis it can support, while still getting faster, easier and cheaper.</p><p>As stated before, considering that the <strong>IT talent shortage is a global reality and will continue to be</strong>, from a market and business standpoint we believe companies from all sizes will continue to “outsource” their data warehouse operation to specialized providers like SlicingDice. That way their teams can focus entirely on extracting value and insights out of the data, instead of spending time building or managing a data warehouse technology.</p><h4>Not sure if a serverless platform can support your needs?</h4><p><a href="https://blog.slicingdice.com/r/?url=https%3A%2F%2Fcalendly.com%2Fslicingdice%2Fdev15min%2F"><strong>Click here and schedule</strong></a> a 15-minute talk with our <strong>developers</strong>, so we can evaluate your case together or <a href="https://blog.slicingdice.com/r/?url=https%3A%2F%2Fwww.slicingdice.com%2Ffaq-and-contact">let’s chat online now</a>.</p><h4>Why SlicingDice?</h4><p>Developers want to store and query their data, but they hate having to manage complex data infrastructure, so <strong>we do it for them</strong>.<br>All they have to do is simply store and query billions of <strong>real-time and historical data,</strong> <strong>without managing any infrastructure</strong>.</p><p>Store your data and make <strong>fast queries</strong> using our <a href="https://docs.slicingdice.com/docs/quickstart-guide"><strong>simple API</strong></a> or any of our clients available in <a href="https://github.com/SlicingDice/slicingdice-python"><strong>Python</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-ruby"><strong>Ruby</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-javascript"><strong>JavaScript</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-go"><strong>Go</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-java"><strong>Java</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-dot-net"><strong>.NET/C#</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-php"><strong>PHP</strong></a>, and <a href="https://github.com/SlicingDice/slicingdice-arduino"><strong>Arduino</strong></a>.</p><p><strong>High availability?</strong><br>You don’t need to worry. We always replicate and backup your data <strong>on three different datacenters</strong>, located in <strong>France, Canada</strong> and <strong>Germany</strong>.</p><p><strong>Query speed?</strong><br>If any query takes <strong>longer than 10 seconds to complete</strong>, no matter its complexity or data size, you receive a <strong>10¢ discount</strong> on your account for each one. We believe ensuring fast queries is <strong>our responsibility, not yours</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae3b00146c26" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slicingdice-com-blog/why-a-serverless-data-warehouse-ae3b00146c26">Why build a “Serverless” Data Warehouse?</a> was originally published in <a href="https://medium.com/slicingdice-com-blog">SlicingDice.com Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Games Analytics in 10 minutes]]></title>
            <link>https://medium.com/slicingdice-com-blog/games-analytics-in-10-minutes-a210aaefa634?source=rss-45dd2f3ce3c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/a210aaefa634</guid>
            <category><![CDATA[big-data-analytics]]></category>
            <category><![CDATA[in-app-purchase]]></category>
            <category><![CDATA[slicingdice]]></category>
            <category><![CDATA[game-analytics]]></category>
            <category><![CDATA[game-development]]></category>
            <dc:creator><![CDATA[SlicingDice Team]]></dc:creator>
            <pubDate>Sun, 23 Apr 2017 20:46:02 GMT</pubDate>
            <atom:updated>2017-05-29T19:27:04.611Z</atom:updated>
            <content:encoded><![CDATA[<p>Go <strong>from zero to game analytics hero in less than 10 minutes</strong>, without managing any infrastructure or worrying about data modeling and size.</p><p>This guide will show how to use <a href="http://www.slicingdice.com/">SlicingDice</a> for game analytics, a <strong>Serverless Data Warehouse and Analytics Database as a Service</strong>.</p><p>Everyday SlicingDice receives <strong>more than 1.1 billion data inserts</strong> and <strong>millions of queries</strong> from multiple indie devs and companies, many of them doing <strong>analytics on top of gaming data</strong>, such as profiles and purchases.</p><h4>Scenario description</h4><p>Let’s imagine you collect data from users playing your games and want to define strategies based on the collected data.</p><h4>Example of game analytics questions we want to answer:</h4><ol><li>What is the average cash spent per age in the past 6 months?</li><li>How many users have spent more than $ 25 in the past 30 days?</li></ol><h3>Sending your user’s gaming data to SlicingDice</h3><p>Sending data to SlicingDice is <strong>very simple and fast</strong>. You can use our <a href="https://docs.slicingdice.com/docs/quickstart-guide"><strong>easy-to-use API</strong></a> or any of our clients available in <a href="https://docs.slicingdice.com/docs/python-client-sdk"><strong>Python</strong></a>, <a href="https://docs.slicingdice.com/docs/ruby-client-sdk"><strong>Ruby</strong></a>, <a href="https://docs.slicingdice.com/docs/javascript-client-sdk"><strong>JavaScript</strong></a>, <a href="https://docs.slicingdice.com/docs/java-client-sdk"><strong>Java</strong></a>, <a href="https://docs.slicingdice.com/docs/net-csharp-client-sdk"><strong>.NET/C#</strong></a>, <a href="https://docs.slicingdice.com/docs/php-client-sdk"><strong>PHP</strong></a>, <a href="https://docs.slicingdice.com/docs/go-client-sdk"><strong>Go</strong></a> and <a href="https://docs.slicingdice.com/docs/arduino-client-sdk"><strong>Arduino</strong></a>.</p><p>In order to send your data, first you simply need to:<br>1. Define what your entity is going to be. We consider an entity to be like a user, a customer, a person and so on. That’s basically a way of saying: who owns the data? So looking both questions above, the data is clearly produced by a user/person, that we will consider to be our entity.</p><p>2. Once you know what is your entity, you simply need to specify the columns and values you want to associate to your entities.</p><h4>Check this data insertion example below</h4><blockquote><strong><em>Pro Tip:</em></strong><em> </em><a href="https://panel.slicingdice.com/generate-demo-key"><em>Click here to generate a </em><strong><em>personal free demo API Key</em></strong></a><em>, so you can copy &amp; paste all the cURL command examples below on your own terminal and </em><strong><em>play with it live</em></strong><em> using our </em><a href="https://docs.slicingdice.com/docs/api-keys#section-demo-api-key"><em>/test endpoint</em></a><em>.</em></blockquote><p>In this example below our entities are <strong>users</strong> and we will insert their profile’s data on SlicingDice, such as age and also all their in-app purchases.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/775556efa81a68a04622688d602a4b31/href">https://medium.com/media/775556efa81a68a04622688d602a4b31/href</a></iframe><p>Looking this data insertion command above, we can clearly see that we have three <strong>user </strong>entities: <strong>user-01</strong>, <strong>user-02</strong> and <strong>user-03</strong>.</p><p>For these three entities we associated three columns: <strong>age</strong>, <strong>email</strong> and <strong>in-app-purchases</strong>.</p><p>As you can see, all entities <strong>user-01</strong>, <strong>user-02</strong> and <strong>user-03</strong> have the same columns <strong>age</strong>, <strong>email</strong> and <strong>in-app-purchases</strong>, but each with different values.</p><p>What is happening here is that you are telling SlicingDice that the <strong>age</strong> of the entity <strong>user-01</strong> is “27”, the <strong>email</strong> is “user1@slicingdice.com” and that the <strong>in-app-purchase</strong> value that happened on “2016–xx–xxT05:52:38Z” is “30.1” , the value that happened on “2016–xx–xxT04:26:20Z” is “50.3” and so on.</p><p>The exactly same thing is happening for the entities <strong>user-02</strong> and <strong>user-03</strong>, but with different values.</p><p>That’s it. Simple like that. As we now have some data stored, let’s answer the questions we defined in the beginning of this post:</p><ol><li>What is the average cash spent per age in the past 6 months?</li><li>How many users have spent more than $ 25 in the past 30 days?</li></ol><h3>Querying your data</h3><p>Making queries on SlicingDice is simple and easy. It’s possible to do <a href="https://docs.slicingdice.com/docs/how-to-make-queries"><strong>multiple types of analysis using our API</strong></a><strong> </strong>and you can get to speed by seeing all the ready-to-use query examples we have on our Github clients repositories for <a href="https://github.com/SlicingDice/slicingdice-python/tree/master/tests_and_examples"><strong>Python</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-ruby/tree/master/tests_and_examples"><strong>Ruby</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-javascript/tree/master/tests_and_examples"><strong>JavaScript</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-java/tree/master/src/test/java/com/slicingdice/jslicer"><strong>Java</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-dot-net/tree/master/TestsAndExamples"><strong>.NET/C#</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-php/tree/master/tests_and_examples"><strong>PHP</strong></a>, and <a href="https://github.com/SlicingDice/slicingdice-go/tree/master/tests_and_examples"><strong>Go</strong></a>.</p><p>In order to answer the question <em>“</em><strong><em>What is the average cash spent per age in the past 6 months?</em></strong><em>”</em> we will be making an <a href="https://docs.slicingdice.com/docs/aggregations">aggregation analysis</a>.</p><p><a href="https://docs.slicingdice.com/docs/aggregations">Aggregation</a> is a powerful way to cross data in order to find insights and unexpected patterns. You can think about it like being an Excel <a href="https://en.wikipedia.org/wiki/Pivot_table">Pivot Table</a>.</p><p>What is happening under the hood on this simple aggregation query below is that we are asking SlicingDice to: <br>1. first retrieve all users having the Top 5 most common values for the “age” column;<br>2. then for each of the five “age” values, make an average on the values of the “in-app-purchase” column that happened within the past 6 months;</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b85281938fa4c11a5aeeadab010878db/href">https://medium.com/media/b85281938fa4c11a5aeeadab010878db/href</a></iframe><p>Based on the data we inserted before, if you run this query above on your own terminal, you should be able to see these results below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/84f5009cdc7776b3e0f826f728ba9b0b/href">https://medium.com/media/84f5009cdc7776b3e0f826f728ba9b0b/href</a></iframe><p>As you can see, results are basically showing the average of in-app purchases by age in the past 6 months. You can answer a lot of questions using aggregations and more importantly, discover insights out of your data.</p><p>Now let’s answer the second question we have: <em>“</em><strong><em>How many users have spent more than $ 25 in the past 30 days?</em></strong><em>”</em>. We can easily answer this question by using the <a href="https://docs.slicingdice.com/docs/count-entities">count entities analysis</a>.</p><p><a href="https://docs.slicingdice.com/docs/count-entities">Count entities</a> is a simply and fast way to know how many unique entities (players) you have that satisfies some set of conditions you define.</p><p>Let’s take as example our query below, what is happening here is that we want to know how many unique users (entities) have values higher than “25” for the “in-app-purchase” column in the “past 30 days”.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bbd06fe5674ffdb1d2e90aaee3351cf5/href">https://medium.com/media/bbd06fe5674ffdb1d2e90aaee3351cf5/href</a></iframe><p>Based on the data we inserted before, if you run this query above on your own terminal, you should be able to see these results below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1adc8b62589e4709c5303d261eca8043/href">https://medium.com/media/1adc8b62589e4709c5303d261eca8043/href</a></iframe><p>As you can see, the results are basically showing the quantity of users (entities) satisfying all conditions of the query.</p><p>Now, if you want to know the email address of these users (entities), you can simply make this <a href="https://docs.slicingdice.com/docs/result-extraction">result data extraction</a> query below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0fd2b22a8414e74eb532e2f8a5d6039d/href">https://medium.com/media/0fd2b22a8414e74eb532e2f8a5d6039d/href</a></iframe><p>As you can see below, it’s showing that the <strong>user-01</strong> and <strong>user-03</strong> are the users and their emails are “user1@slicingdice.com” and “user3@slicingdice.com”.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/66a9bafeeb4c72673dfa5647be209fd5/href">https://medium.com/media/66a9bafeeb4c72673dfa5647be209fd5/href</a></iframe><h3>What other questions and analysis can I make?</h3><p>SlicingDice supports <a href="https://docs.slicingdice.com/docs/how-to-make-queries">multiple types of data analysis</a>, so you can basically answer any kind of question you may need for analytics purposes, for example:</p><ul><li>How many new users in the past 7 days came back to play my game, broken down by age, per day?</li><li>How many plays did the users have on average before making the first purchase?</li></ul><h3>You nailed it, hero! — Next steps</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*2l2udxr7w9iiH6yLfvV-_A.gif" /></figure><p><strong>That’s it.</strong> You are now ready to start making as much game analysis as you want.<br>If you are inclined to think that SlicingDice might work for you, we suggest you take a look on <a href="https://docs.slicingdice.com/">our documentation</a> and at least follow our <a href="https://docs.slicingdice.com/docs/quickstart-guide">quickstart guide</a>.</p><p>Please, don’t hesitate to contact our <a href="https://www.slicingdice.com/faq-and-contact"><strong>developer support team</strong></a> <strong>at any time, for any reason</strong>. We are here to support your needs.</p><h3>Loved it… but, how much does it cost?</h3><p><a href="https://blog.slicingdice.com/slicingdice-pricing-model-and-competitors-comparison-31f1c9f0f076">Our price is really innovative and cheap</a>. We charge based on the <strong>quantity of columns</strong> you have, doesn’t matter how many rows you store for them.</p><p>So for example you can store <strong>unlimited data</strong> on SlicingDice for these two use cases presented above (game users, for example) <strong>for less $ 10.00 per month</strong>. It’s true. <a href="https://www.slicingdice.com/pricing">Check our website pricing page</a>.</p><h3>Why SlicingDice?</h3><p>Developers want to store and query their data, but they hate having to manage complex data infrastructure, so <strong>we do it for them</strong>.<br>All they have to do is simply store and query billions of <strong>real-time and historical data,</strong> <strong>without managing any infrastructure</strong>.</p><p><strong>High availability?</strong><br>You don’t need to worry. We always replicate and backup your data <strong>on three different datacenters</strong>, located in <strong>France, Canada</strong> and <strong>Germany</strong>.</p><p><strong>Query speed?</strong><br>If any query takes <strong>longer than 10 seconds to complete</strong>, no matter the query complexity or data size, you receive a <strong>10¢ discount</strong> for each query. We believe ensuring fast queries is <strong>our responsibility, not yours</strong>.</p><h3>Not sure if we can support your needs?</h3><p><a href="https://calendly.com/slicingdice/dev15min/"><strong>Click here and schedule</strong></a> a 15-minute talk with <strong>our developers</strong>, totally free of charge, so we can evaluate your case together.</p><p>Don’t know how to model your data in order to send it to SlicingDice? <br>No problem at all, <a href="https://calendly.com/slicingdice/dev15min/"><strong>schedule a time</strong></a> so we can talk or <a href="https://www.slicingdice.com/faq-and-contact"><strong>let’s chat online now</strong></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a210aaefa634" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slicingdice-com-blog/games-analytics-in-10-minutes-a210aaefa634">Games Analytics in 10 minutes</a> was originally published in <a href="https://medium.com/slicingdice-com-blog">SlicingDice.com Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Social Media Analytics in 10 minutes]]></title>
            <link>https://medium.com/slicingdice-com-blog/social-media-analytics-in-10-minutes-9ebadaad41a4?source=rss-45dd2f3ce3c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ebadaad41a4</guid>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[social-media-analysis]]></category>
            <category><![CDATA[slicingdice]]></category>
            <category><![CDATA[social-media-analytics]]></category>
            <category><![CDATA[big-data-analytics]]></category>
            <dc:creator><![CDATA[SlicingDice Team]]></dc:creator>
            <pubDate>Sun, 23 Apr 2017 20:12:49 GMT</pubDate>
            <atom:updated>2017-05-29T19:23:59.113Z</atom:updated>
            <content:encoded><![CDATA[<p>Go <strong>from zero to social media analytics hero in less than 10 minutes</strong>, without managing any infrastructure or worrying about data size.</p><p>This guide will show how to use <a href="http://www.slicingdice.com/">SlicingDice</a> for social media analytics, a <strong>Serverless Data Warehouse and Analytics Database as a Service</strong>.</p><p>Everyday SlicingDice receives <strong>more than 1.1 billion data inserts</strong> and <strong>millions of queries</strong> from multiple indie devs and companies, many of them doing <strong>analytics on top of social media data</strong>, such as Twitter’s data.</p><h4>Scenario description</h4><p>Let’s imagine you collect social media data and want to use them to find the most relevant users or to understand the user’s behaviors.</p><h4>Example of social media analytics questions we want to answer:</h4><ol><li>What are the most used hashtags last week among the followers of famous Twitter accounts?</li><li>How many users twitted the hashtag #slicingdice in the past 24 hours and follow @SlicingDice?</li></ol><h3>Sending your social media data to SlicingDice</h3><p>Sending data to SlicingDice is <strong>very simple and fast</strong>. You can use our <a href="https://docs.slicingdice.com/docs/quickstart-guide"><strong>easy-to-use API</strong></a> or any of our clients available in <a href="https://docs.slicingdice.com/docs/python-client-sdk"><strong>Python</strong></a>, <a href="https://docs.slicingdice.com/docs/ruby-client-sdk"><strong>Ruby</strong></a>, <a href="https://docs.slicingdice.com/docs/javascript-client-sdk"><strong>JavaScript</strong></a>, <a href="https://docs.slicingdice.com/docs/java-client-sdk"><strong>Java</strong></a>, <a href="https://docs.slicingdice.com/docs/net-csharp-client-sdk"><strong>.NET/C#</strong></a>, <a href="https://docs.slicingdice.com/docs/php-client-sdk"><strong>PHP</strong></a>, <a href="https://docs.slicingdice.com/docs/go-client-sdk"><strong>Go</strong></a> and <a href="https://docs.slicingdice.com/docs/arduino-client-sdk"><strong>Arduino</strong></a>.</p><p>In order to send your data, first you simply need to:<br>1. Define what your entity is going to be. We consider an entity to be like a user, a customer, a person and so on. That’s basically a way of saying: who owns the data? So looking both questions above, the data is clearly produced by a Twitter user, that we will consider to be our entity.</p><p>2. Once you know what is your entity, you simply need to specify the columns and values you want to associate to your entities.</p><h4>Check this data insertion example below</h4><blockquote><strong><em>Pro Tip:</em></strong><em> </em><a href="https://panel.slicingdice.com/generate-demo-key"><em>Click here to generate a </em><strong><em>personal free demo API Key</em></strong></a><em>, so you can copy &amp; paste all the cURL command examples below on your own terminal and </em><strong><em>play with it live</em></strong><em> using our </em><a href="https://docs.slicingdice.com/docs/api-keys#section-demo-api-key"><em>/test endpoint</em></a><em>.</em></blockquote><p>In this example below our entities are <strong>Twitter users</strong> and we will insert some of their data on SlicingDice, such as hashtags used and the users they follow.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/389c79350d989526f123ce78b361ec27/href">https://medium.com/media/389c79350d989526f123ce78b361ec27/href</a></iframe><p>Looking this data insertion command above, we can clearly see that we have three <strong>user </strong>entities: <strong>@user1</strong>, <strong>@user2</strong> and <strong>@user3</strong>.</p><p>For these three entities we associated two columns: <strong>following</strong> and <strong>hashtags</strong>.</p><p>As you can see, all entities <strong>@user1</strong>, <strong>@user2</strong> and <strong>@user3</strong> have the same columns <strong>following</strong> and <strong>hashtags</strong>, but each with different values.</p><p>What is happening here is that you are telling SlicingDice that the <strong>following</strong> values of the entity <strong>@user1</strong> are [“@user3” and “@SlicingDice”], and that the <strong>hashtags</strong> value “#123” was used on “2017–xx–xxT05:52:38Z” , the “#abc” values was used on “2017–xx–xxT05:26:20Z” and so on.</p><p>The exactly same thing is happening for the entities <strong>@user2</strong> and <strong>@user3</strong>, but with different values.</p><p>That’s it. Simple like that. As we now have some data stored, let’s answer the questions we defined in the beginning of this post:</p><ol><li>What are the most used hashtags last week among the followers of famous Twitter accounts?</li><li>How many users twitted the hashtag #slicingdice in the past 24 hours and follow @SlicingDice?</li></ol><h3>Querying your data</h3><p>Making queries on SlicingDice is simple and easy. It’s possible to do <a href="https://docs.slicingdice.com/docs/how-to-make-queries"><strong>multiple types of analysis using our API</strong></a><strong> </strong>and you can get to speed by seeing all the ready-to-use query examples we have on our Github clients repositories for <a href="https://github.com/SlicingDice/slicingdice-python/tree/master/tests_and_examples"><strong>Python</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-ruby/tree/master/tests_and_examples"><strong>Ruby</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-javascript/tree/master/tests_and_examples"><strong>JavaScript</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-java/tree/master/src/test/java/com/slicingdice/jslicer"><strong>Java</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-dot-net/tree/master/TestsAndExamples"><strong>.NET/C#</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-php/tree/master/tests_and_examples"><strong>PHP</strong></a>, and <a href="https://github.com/SlicingDice/slicingdice-go/tree/master/tests_and_examples"><strong>Go</strong></a>.</p><p>In order to answer the question <em>“</em><strong><em>What are the most used hashtags last week among the followers of famous Twitter accounts?</em></strong><em>”</em> we will be making an <a href="https://docs.slicingdice.com/docs/aggregations">aggregation analysis</a>.</p><p><a href="https://docs.slicingdice.com/docs/aggregations">Aggregation</a> is a powerful way to cross data in order to find insights and unexpected patterns. You can think about it like being an Excel <a href="https://en.wikipedia.org/wiki/Pivot_table">Pivot Table</a>.</p><p>What is happening under the hood on this simple aggregation query below is that we are asking SlicingDice to: <br>1. first retrieve all users having the Top 5 most common values for the “following” column;<br>2. then for each of the five “following” values, make an intersection of these users with all the users having the “hashtags” column, finally selecting the Top 5 results of the intersection to show.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/af4d1ec8a7447ba1893f620bf94dad8d/href">https://medium.com/media/af4d1ec8a7447ba1893f620bf94dad8d/href</a></iframe><p>Based on the data we inserted before, if you run this query above on your own terminal, you should be able to see these results below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/77defd5d08085c47b8e7bdca3ef413bd/href">https://medium.com/media/77defd5d08085c47b8e7bdca3ef413bd/href</a></iframe><p>As you can see, results are basically showing the most used hashtags for each famous Twitter accounts followed. You can answer a lot of questions using aggregations and more importantly, discover insights out of your data.</p><p>Now let’s answer the second question we have: <em>“</em><strong><em>How many users twitted the hashtag #slicingdice in the past 24 hours and follow @SlicingDice?</em></strong><em>”</em>. We can easily answer this question by using the <a href="https://docs.slicingdice.com/docs/count-entities">count entities analysis</a>.</p><p><a href="https://docs.slicingdice.com/docs/count-entities">Count entities</a> is a simply and fast way to know how many unique entities (cookies) you have that satisfies some set of conditions you define.</p><p>Let’s take as example our query below, what is happening here is that we want to know how many Twitter users (entities) have the “#slicingdice” value added for the “hashtag” column in the “last 24 hours” AND also have the “@SlicingDice” value for the “following” column.</p><p>Note that we are putting a name for this query (number-of-twitter-users) because our API accepts making multiple count queries in a single request.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/84f2dd481abfd46fb145249d56f47529/href">https://medium.com/media/84f2dd481abfd46fb145249d56f47529/href</a></iframe><p>Based on the data we inserted before, if you run this query above on your own terminal, you should be able to see these results below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e3cc39a41ec6d36459e3804be998bec5/href">https://medium.com/media/e3cc39a41ec6d36459e3804be998bec5/href</a></iframe><p>As you can see, the results are basically showing there is <strong>1 Twitter user (entity)</strong> satisfying all conditions of the query.</p><p>Now, if you want to know who are these users (entities), you can simply make this <a href="https://docs.slicingdice.com/docs/result-extraction">result data extraction</a> query below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/47ff30a682e778dcd2af1d0d2d2c2750/href">https://medium.com/media/47ff30a682e778dcd2af1d0d2d2c2750/href</a></iframe><p>As you can see below, it’s showing that the <strong>@user3</strong> is the one that used the “#slicingdice” hashtag in the last 24 hours and is also following “@SlicingDice”.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/18275fd7ae26a952b5b9f9f457d6825e/href">https://medium.com/media/18275fd7ae26a952b5b9f9f457d6825e/href</a></iframe><h3>What other questions and analysis can I make?</h3><p>SlicingDice supports <a href="https://docs.slicingdice.com/docs/how-to-make-queries">multiple types of data analysis</a>, so you can basically answer any kind of question you may need for analytics purposes, for example:</p><ul><li>How many “@SlicingDice” followers are also following “@Google” and “@Facebook” but not “@Amazon”?</li><li>How many times the hashtag #slicingdice was twitted in the past 24 hours?</li></ul><h3>You nailed it, hero! — Next steps</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*2l2udxr7w9iiH6yLfvV-_A.gif" /></figure><p><strong>That’s it.</strong> You are now ready to start making as much social media analysis as you want.<br>If you are inclined to think that SlicingDice might work for you, we suggest you take a look on <a href="https://docs.slicingdice.com/">our documentation</a> and at least follow our <a href="https://docs.slicingdice.com/docs/quickstart-guide">quickstart guide</a>.</p><p>Please, don’t hesitate to contact our <a href="https://www.slicingdice.com/faq-and-contact"><strong>developer support team</strong></a> <strong>at any time, for any reason</strong>. We are here to support your needs.</p><h3>Loved it… but, how much does it cost?</h3><p><a href="https://blog.slicingdice.com/slicingdice-pricing-model-and-competitors-comparison-31f1c9f0f076">Our price is really innovative and cheap</a>. We charge based on the <strong>quantity of columns</strong> you have, doesn’t matter how many rows you store for them.</p><p>So for example you can store <strong>unlimited data</strong> on SlicingDice for this use case presented above (Twitter users, for example) <strong>for less $ 10.00 per month</strong>. It’s true. <a href="https://www.slicingdice.com/pricing">Check our website pricing page</a>.</p><h3>Why SlicingDice?</h3><p>Developers want to store and query their data, but they hate having to manage complex data infrastructure, so <strong>we do it for them</strong>.<br>All they have to do is simply store and query billions of <strong>real-time and historical data,</strong> <strong>without managing any infrastructure</strong>.</p><p><strong>High availability?</strong><br>You don’t need to worry. We always replicate and backup your data <strong>on three different datacenters</strong>, located in <strong>France, Canada</strong> and <strong>Germany</strong>.</p><p><strong>Query speed?</strong><br>If any query takes <strong>longer than 10 seconds to complete</strong>, no matter the query complexity or data size, you receive a <strong>10¢ discount</strong> for each query. We believe ensuring fast queries is <strong>our responsibility, not yours</strong>.</p><h3>Not sure if we can support your needs?</h3><p><a href="https://calendly.com/slicingdice/dev15min/"><strong>Click here and schedule</strong></a> a 15-minute talk with <strong>our developers</strong>, totally free of charge, so we can evaluate your case together.</p><p>Don’t know how to model your data in order to send it to SlicingDice? <br>No problem at all, <a href="https://calendly.com/slicingdice/dev15min/"><strong>schedule a time</strong></a> so we can talk or <a href="https://www.slicingdice.com/faq-and-contact"><strong>let’s chat online now</strong></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ebadaad41a4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slicingdice-com-blog/social-media-analytics-in-10-minutes-9ebadaad41a4">Social Media Analytics in 10 minutes</a> was originally published in <a href="https://medium.com/slicingdice-com-blog">SlicingDice.com Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Call Center Analytics in 10 minutes]]></title>
            <link>https://medium.com/slicingdice-com-blog/call-center-analytics-in-10-minutes-b38a24fe68e8?source=rss-45dd2f3ce3c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/b38a24fe68e8</guid>
            <category><![CDATA[call-center]]></category>
            <category><![CDATA[big-data-analytics]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[contact-center]]></category>
            <category><![CDATA[slicingdice]]></category>
            <dc:creator><![CDATA[SlicingDice Team]]></dc:creator>
            <pubDate>Sun, 23 Apr 2017 19:31:44 GMT</pubDate>
            <atom:updated>2017-05-29T19:19:34.672Z</atom:updated>
            <content:encoded><![CDATA[<p>Go <strong>from zero to call center analytics hero in less than 10 minutes</strong>, without managing any infrastructure or worrying about data size.</p><p>This guide will show how to use <a href="http://www.slicingdice.com/">SlicingDice</a> for call center analytics, a <strong>Serverless Data Warehouse and Analytics Database as a Service</strong>.</p><p>Everyday SlicingDice receives <strong>more than 1.1 billion data inserts</strong> and <strong>millions of queries</strong> from multiple indie devs and companies, many of them doing <strong>analytics on top of call center data</strong>, such as average call durations.</p><h4>Scenario description</h4><p>Let’s imagine you collect call information from call center agents and want to assess their performance in order to develop strategies based on data.</p><h4>Example of call center analytics questions we want to answer:</h4><ol><li>What is the total number of calls per agent done in the last quarter grouped per week?</li><li>What is the average duration for the calls in the last month?</li></ol><h3>Sending your call center data to SlicingDice</h3><p>Sending data to SlicingDice is <strong>very simple and fast</strong>. You can use our <a href="https://docs.slicingdice.com/docs/quickstart-guide"><strong>easy-to-use API</strong></a> or any of our clients available in <a href="https://docs.slicingdice.com/docs/python-client-sdk"><strong>Python</strong></a>, <a href="https://docs.slicingdice.com/docs/ruby-client-sdk"><strong>Ruby</strong></a>, <a href="https://docs.slicingdice.com/docs/javascript-client-sdk"><strong>JavaScript</strong></a>, <a href="https://docs.slicingdice.com/docs/java-client-sdk"><strong>Java</strong></a>, <a href="https://docs.slicingdice.com/docs/net-csharp-client-sdk"><strong>.NET/C#</strong></a>, <a href="https://docs.slicingdice.com/docs/php-client-sdk"><strong>PHP</strong></a>, <a href="https://docs.slicingdice.com/docs/go-client-sdk"><strong>Go</strong></a> and <a href="https://docs.slicingdice.com/docs/arduino-client-sdk"><strong>Arduino</strong></a>.</p><p>In order to send your data, first you simply need to:<br>1. Define what your entity is going to be. We consider an entity to be like a car, a user, a server and so on. That’s basically a way of saying: who owns the data? So looking both questions above, the data is clearly produced by a call center agent, that we will consider to be our entity.</p><p>2. Once you know what is your entity, you simply need to specify the columns and values you want to associate to your entities.</p><h4>Check this data insertion example below</h4><blockquote><strong><em>Pro Tip:</em></strong><em> </em><a href="https://panel.slicingdice.com/generate-demo-key"><em>Click here to generate a </em><strong><em>personal free demo API Key</em></strong></a><em>, so you can copy &amp; paste all the cURL command examples below on your own terminal and </em><strong><em>play with it live</em></strong><em> using our </em><a href="https://docs.slicingdice.com/docs/api-keys#section-demo-api-key"><em>/test endpoint</em></a><em>.</em></blockquote><p>In this example below our entities are <strong>call center agents </strong>and we will be inserting all calls made by each agent.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9f4ae22b9edd58c384a6619445297c48/href">https://medium.com/media/9f4ae22b9edd58c384a6619445297c48/href</a></iframe><p>Looking this data insertion command above, we can clearly see that we have three <strong>agent </strong>entities: <strong>callcenter-agent-01</strong>, <strong>callcenter-agent-02</strong> and <strong>callcenter-agent-03</strong>.</p><p>For these three entities we associated one column: <strong>agent-action</strong>.</p><p>As you can see, all entities <strong>callcenter-agent-01</strong>, <strong>callcenter-agent-02</strong> and <strong>callcenter-agent-03</strong> have the same column <strong>agent-action</strong>, but each with different values.</p><p>What is happening here is that you are telling SlicingDice that the <strong>callcenter-agent-01</strong> made a “call” <strong>agent-action</strong> on “2017–xx–xxT05:33:09Z”, the <strong>callcenter-agent-02</strong> made a “call” <strong>agent-action</strong> on “2017–xx–xxT09:30:18Z” and so on.</p><p>The exactly same thing is happening for the entity <strong>callcenter-agent-03</strong>, but with different value for the <strong>agent-action</strong> column.</p><p>Before starting to query this data, <strong>let’s see another insertion example:</strong><br><strong><em>Again:</em></strong><em> if you paste your </em><a href="https://panel.slicingdice.com/generate-demo-key/"><strong><em>personal demo API key</em></strong></a><em> on this cURL command below and execute it on your terminal, it will really work. Go ahead and try yourself.</em></p><p>In this example below our entities are still <strong>call center agents </strong>and we will be inserting the call time durations for each call made by each agent.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ae56a6788f67125e21925709cec9fe62/href">https://medium.com/media/ae56a6788f67125e21925709cec9fe62/href</a></iframe><p>Again, we can clearly see that we have three <strong>agent </strong>entities: <strong>callcenter-agent-01</strong>, <strong>callcenter-agent-02</strong> and <strong>callcenter-agent-03</strong>.</p><p>Coincidentally all entities are sharing the same column, <strong>call-duration</strong>, although each entity has its own values associated to the columns. It’s important to note that not all entities have to have the same columns.</p><p>What is happening here is that you are telling SlicingDice to store that the <strong>call-duration</strong> made by <strong>callcenter-agent-01</strong> on “2017–xx–xxT02:33:09Z” was “3.51”, and the <strong>call-duration</strong> made by <strong>callcenter-agent-02</strong> on “2017–xx–xxT12:30:18Z” was “2.72” and so on.</p><p>That’s it. Simple like that. As we now have some data stored, let’s answer the questions we defined in the beginning of this post:</p><ol><li>What is the total number of calls per agent done in the last quarter grouped per week?</li><li>What is the average duration for the calls in the last month?</li></ol><h3>Querying your data</h3><p>Making queries on SlicingDice is simple and easy. It’s possible to do <a href="https://docs.slicingdice.com/docs/how-to-make-queries"><strong>multiple types of analysis using our API</strong></a><strong> </strong>and you can get to speed by seeing all the ready-to-use query examples we have on our Github clients repositories for <a href="https://github.com/SlicingDice/slicingdice-python/tree/master/tests_and_examples"><strong>Python</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-ruby/tree/master/tests_and_examples"><strong>Ruby</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-javascript/tree/master/tests_and_examples"><strong>JavaScript</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-java/tree/master/src/test/java/com/slicingdice/jslicer"><strong>Java</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-dot-net/tree/master/TestsAndExamples"><strong>.NET/C#</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-php/tree/master/tests_and_examples"><strong>PHP</strong></a>, and <a href="https://github.com/SlicingDice/slicingdice-go/tree/master/tests_and_examples"><strong>Go</strong></a>.</p><p>In order to answer the question <em>“</em><strong><em>What is the total number of calls per agent done in the last quarter grouped per week?</em></strong><em>”</em> we will be making a <a href="https://docs.slicingdice.com/docs/aggregations">histogram aggregations analysis</a>.</p><p><a href="https://docs.slicingdice.com/docs/aggregations">Histogram aggregations</a> are great to understand how a determined metric on a event column (like “action”) is distributed along a time interval.</p><p>What is happening under the hood on this aggregation query below is that we are asking SlicingDice to: <br>1. select the top 10 call center agents;<br>2. for each one of them make a count of events that happened for the “action” column between “now” and the “last 3 months”;<br>3. finally group the quantity of call events per agent, per week.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/49fce8567c3aee852e1aa3b6aec7c4ac/href">https://medium.com/media/49fce8567c3aee852e1aa3b6aec7c4ac/href</a></iframe><p>Based on the data we inserted before, if you run this query above on your own terminal, you should be able to see these results below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/99356475f6f829679ac19011794226e4/href">https://medium.com/media/99356475f6f829679ac19011794226e4/href</a></iframe><p>As you can see, the results are basically showing the quantity of calls in the past 3 months for each call center agent, grouped by week. You can answer a lot of questions using aggregations and more importantly, discover insights out of your data.</p><p>Now let’s answer the second question we have: <em>“</em><strong><em>What is the average duration for the calls in the last month?</em></strong><em>”</em>. We can easily answer this question by making a <a href="https://docs.slicingdice.com/docs/aggregations">metrics aggregation</a>.</p><p><a href="https://docs.slicingdice.com/docs/aggregations">Aggregation</a> is a powerful way to cross data in order to find insights and unexpected patterns. You can think about it like being an Excel <a href="https://en.wikipedia.org/wiki/Pivot_table">Pivot Table</a>.</p><p>Let’s take as example our query below, we are asking SlicingDice to make an average operation on all the values of the “call-duration” column between “now” and “last 1 month”.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bb00a80ae7185f29f6d899b5a78cdb0b/href">https://medium.com/media/bb00a80ae7185f29f6d899b5a78cdb0b/href</a></iframe><p>Based on the data we inserted before, if you run this query above on your own terminal, you should be able to see these results below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/59a77b324112f9bfc7e8ccfa4177bf34/href">https://medium.com/media/59a77b324112f9bfc7e8ccfa4177bf34/href</a></iframe><p>As you can see, the result is basically showing the average call duration from all agent’s calls that happened in the last month.</p><h3>What other questions and analysis can I make?</h3><p>SlicingDice supports <a href="https://docs.slicingdice.com/docs/how-to-make-queries">multiple types of data analysis</a>, so you can basically answer any kind of question you may need for analytics purposes, for example:</p><ul><li>What is the call time average for the calls that converted into sales, by each agent?</li><li>How many calls each call center agent had to make before doing its first successful sales conversion?</li></ul><h3>You nailed it, hero! — Next steps</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*2l2udxr7w9iiH6yLfvV-_A.gif" /></figure><p><strong>That’s it.</strong> You are now ready to start making as much call center analysis as you want.<br>If you are inclined to think that SlicingDice might work for you, we suggest you take a look on <a href="https://docs.slicingdice.com/">our documentation</a> and at least follow our <a href="https://docs.slicingdice.com/docs/quickstart-guide">quickstart guide</a>.</p><p>Please, don’t hesitate to contact our <a href="https://www.slicingdice.com/faq-and-contact"><strong>developer support team</strong></a> <strong>at any time, for any reason</strong>. We are here to support your needs.</p><h3>Loved it… but, how much does it cost?</h3><p><a href="https://blog.slicingdice.com/slicingdice-pricing-model-and-competitors-comparison-31f1c9f0f076">Our price is really innovative and cheap</a>. We charge based on the <strong>quantity of columns</strong> you have, doesn’t matter how many rows you store for them.</p><p>So for example you can store <strong>unlimited data</strong> on SlicingDice for these two use cases presented above (call center agents, for example) <strong>for less $ 10.00 per month</strong>. It’s true. <a href="https://www.slicingdice.com/pricing">Check our website pricing page</a>.</p><h3>Why SlicingDice?</h3><p>Developers want to store and query their data, but they hate having to manage complex data infrastructure, so <strong>we do it for them</strong>.<br>All they have to do is simply store and query billions of <strong>real-time and historical data,</strong> <strong>without managing any infrastructure</strong>.</p><p><strong>High availability?</strong><br>You don’t need to worry. We always replicate and backup your data <strong>on three different datacenters</strong>, located in <strong>France, Canada</strong> and <strong>Germany</strong>.</p><p><strong>Query speed?</strong><br>If any query takes <strong>longer than 10 seconds to complete</strong>, no matter the query complexity or data size, you receive a <strong>10¢ discount</strong> for each query. We believe ensuring fast queries is <strong>our responsibility, not yours</strong>.</p><h3>Not sure if we can support your needs?</h3><p><a href="https://calendly.com/slicingdice/dev15min/"><strong>Click here and schedule</strong></a> a 15-minute talk with <strong>our developers</strong>, totally free of charge, so we can evaluate your case together.</p><p>Don’t know how to model your data in order to send it to SlicingDice? <br>No problem at all, <a href="https://calendly.com/slicingdice/dev15min/"><strong>schedule a time</strong></a> so we can talk or <a href="https://www.slicingdice.com/faq-and-contact"><strong>let’s chat online now</strong></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b38a24fe68e8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slicingdice-com-blog/call-center-analytics-in-10-minutes-b38a24fe68e8">Call Center Analytics in 10 minutes</a> was originally published in <a href="https://medium.com/slicingdice-com-blog">SlicingDice.com Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CRM Analytics in 10 minutes]]></title>
            <link>https://medium.com/slicingdice-com-blog/crm-analytics-in-10-minutes-482b00eec2c2?source=rss-45dd2f3ce3c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/482b00eec2c2</guid>
            <category><![CDATA[slicingdice]]></category>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[crm]]></category>
            <category><![CDATA[crm-data-migration]]></category>
            <category><![CDATA[customer-analytics]]></category>
            <dc:creator><![CDATA[SlicingDice Team]]></dc:creator>
            <pubDate>Sun, 23 Apr 2017 18:26:30 GMT</pubDate>
            <atom:updated>2017-05-29T19:14:40.750Z</atom:updated>
            <content:encoded><![CDATA[<p>Go <strong>from zero to CRM analytics hero in less than 10 minutes</strong>, without managing any infrastructure or worrying about data size.</p><p>This guide will show how to use <a href="http://www.slicingdice.com/">SlicingDice</a> for CRM analytics, a <strong>Serverless Data Warehouse and Analytics Database as a Service</strong>.</p><p>Everyday SlicingDice receives <strong>more than 1.1 billion data inserts</strong> and <strong>millions of queries</strong> from multiple indie devs and companies, many of them doing <strong>analytics on top of CRM data</strong>, such as customers and transactions.</p><h4>Scenario description</h4><p>Let’s imagine you have customers and transactions data from your company CRM and want to use it to run analytics and make data-oriented decisions.</p><h4>Example of sales and business questions we want to answer:</h4><ol><li>What is the average lead monetary value by status by salesperson in the last 48 hours?</li><li>How many purchases by day were originated by people who bought at least 2 times in the past 30 days and are from “New York” or “San Francisco”?</li></ol><h3>Sending your CRM data to SlicingDice</h3><p>Sending data to SlicingDice is <strong>very simple and fast</strong>. You can use our <a href="https://docs.slicingdice.com/docs/quickstart-guide"><strong>easy-to-use API</strong></a> or any of our clients available in <a href="https://docs.slicingdice.com/docs/python-client-sdk"><strong>Python</strong></a>, <a href="https://docs.slicingdice.com/docs/ruby-client-sdk"><strong>Ruby</strong></a>, <a href="https://docs.slicingdice.com/docs/javascript-client-sdk"><strong>JavaScript</strong></a>, <a href="https://docs.slicingdice.com/docs/java-client-sdk"><strong>Java</strong></a>, <a href="https://docs.slicingdice.com/docs/net-csharp-client-sdk"><strong>.NET/C#</strong></a>, <a href="https://docs.slicingdice.com/docs/php-client-sdk"><strong>PHP</strong></a>, <a href="https://docs.slicingdice.com/docs/go-client-sdk"><strong>Go</strong></a> and <a href="https://docs.slicingdice.com/docs/arduino-client-sdk"><strong>Arduino</strong></a>.</p><p>In order to send your data, first you simply need to:<br>1. Define what your entity is going to be. We consider an entity to be like a car, a user, a server and so on. That’s basically a way of saying: who owns the data? So looking the first question above, the data is clearly produced by sales leads, and on the second, each entity could be a customer.</p><p>2. Once you know what is your entity, you simply need to specify the columns and values you want to associate to your entities.</p><h4>Check this data insertion example below</h4><blockquote><strong><em>Pro Tip:</em></strong><em> </em><a href="https://panel.slicingdice.com/generate-demo-key"><em>Click here to generate a </em><strong><em>personal free demo API Key</em></strong></a><em>, so you can copy &amp; paste all the cURL command examples below on your own terminal and </em><strong><em>play with it live</em></strong><em> using our </em><a href="https://docs.slicingdice.com/docs/api-keys#section-demo-api-key"><em>/test endpoint</em></a><em>.</em></blockquote><p>In this example our entities are <strong>sales leads </strong>and we will be inserting all the lead details, such as ticket size, salesperson and status.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8a47c0b75de162488200a5f468e596fa/href">https://medium.com/media/8a47c0b75de162488200a5f468e596fa/href</a></iframe><p>Looking this data insertion command above, we can clearly see that we have three <strong>sales lead </strong>entities: <strong>lead-01</strong>, <strong>lead-02</strong> and <strong>lead-03</strong>.</p><p>For these three entities we associated three columns: <strong>ticket</strong>, <strong>salesperson</strong> and <strong>lead-status</strong>.</p><p>As you can see, all entities <strong>lead-01</strong>, <strong>lead-02</strong> and <strong>lead-03</strong> have the same columns <strong>ticket</strong>, <strong>salesperson</strong> and <strong>lead-status</strong>, but each with different values.</p><p>What is happening here is that you are telling SlicingDice that the <strong>ticket</strong> of the entity <strong>lead-01</strong> was “489745.12”, the <strong>salesperson</strong> is “Glenna” and also that <strong>lead-status</strong> was “first-contact” for the date “2017–xx–xxT00:33:09Z”, “negotiating” on “2017–xx–xxT04:30:18Z” and so on.</p><p>The exactly same thing is happening for the entities <strong>lead-02</strong> and <strong>lead-03</strong>, but with different values for the columns.</p><p>Before starting to query this data, <strong>let’s see another insertion example:</strong><br><strong><em>Again:</em></strong><em> if you paste your </em><a href="https://panel.slicingdice.com/generate-demo-key/"><strong><em>personal demo API key</em></strong></a><em> on this cURL command below and execute it on your terminal, it will really work. Go ahead and try yourself.</em></p><p>In this example below our entities are <strong>customers</strong> and we will be inserting the city, actions and purchases for each of them.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0391518b7674b190269e1ef2ba8f7f4f/href">https://medium.com/media/0391518b7674b190269e1ef2ba8f7f4f/href</a></iframe><p>Again, we can clearly see that we have four <strong>customers</strong> entities: <strong>customer-01</strong>, <strong>customer-02</strong>, <strong>customer-03</strong> and <strong>customer-04</strong>.</p><p>Coincidentally all entities are sharing the same columns, <strong>city</strong>, <strong>actions</strong> and <strong>purchases</strong>, although each entity has its own values associated to the columns. It’s important to note that not all entities have to have the same columns.</p><p>What is happening here is that you are telling SlicingDice to store that the <strong>city</strong> of the <strong>customer-01</strong> is “New York”, that he made multiple <strong>actions</strong>, such as “purchase” on “2017–xx–xxT06:42:42Z”, and also made multiple <strong>purchases</strong>, such as “600.00” on “2017–xx–xxT06:42:42Z”.</p><p>That’s it. Simple like that. As we now have some data stored, let’s answer the questions we defined in the beginning of this post:</p><ol><li>What is the average lead monetary value by status by salesperson in the last 48 hours?</li><li>How many purchases by day were originated by people who bought at least 2 times in the past 30 days and are from “New York” or “San Francisco”?</li></ol><h3>Querying your data</h3><p>Making queries on SlicingDice is simple and easy. It’s possible to do <a href="https://docs.slicingdice.com/docs/how-to-make-queries"><strong>multiple types of analysis using our API</strong></a><strong> </strong>and you can get to speed by seeing all the ready-to-use query examples we have on our Github clients repositories for <a href="https://github.com/SlicingDice/slicingdice-python/tree/master/tests_and_examples"><strong>Python</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-ruby/tree/master/tests_and_examples"><strong>Ruby</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-javascript/tree/master/tests_and_examples"><strong>JavaScript</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-java/tree/master/src/test/java/com/slicingdice/jslicer"><strong>Java</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-dot-net/tree/master/TestsAndExamples"><strong>.NET/C#</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-php/tree/master/tests_and_examples"><strong>PHP</strong></a>, and <a href="https://github.com/SlicingDice/slicingdice-go/tree/master/tests_and_examples"><strong>Go</strong></a>.</p><p>In order to answer the question <em>“</em><strong><em>What is the average lead monetary value by status by salesperson in the last 48 hours?</em></strong><em>”</em> we will be making a <a href="https://docs.slicingdice.com/docs/aggregations">filtered aggregation analysis</a>.</p><p><a href="https://docs.slicingdice.com/docs/aggregations">Aggregation</a> is a powerful way to cross data in order to find insights and unexpected patterns. You can think about it like being an Excel <a href="https://en.wikipedia.org/wiki/Pivot_table">Pivot Table</a>.</p><p>What is happening under the hood on this aggregation query below is that we are asking SlicingDice to: <br>1. first filter just the sales leads that has “status” equals to “first-contact” between “now” and the “last 48 hours”.<br>2. next retrieve the all sales leads from the Top 20 most common values for the “salesperson” column;<br>2. then for the leads of each “salesperson”, make an intersection with the most common values for the “status” column values;<br>3. finally take the previous group of leads and make an average on the values of the “ticket” column of these leads.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5ecbc49d637f918e1f2ebe7ca9fb208d/href">https://medium.com/media/5ecbc49d637f918e1f2ebe7ca9fb208d/href</a></iframe><p>Based on the data we inserted before, if you run this query above on your own terminal, you should be able to see these results below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f882fe47cc2ff0cc2397d166d01b8335/href">https://medium.com/media/f882fe47cc2ff0cc2397d166d01b8335/href</a></iframe><p>As you can see, the results are basically showing the average ticket value per lead status and salesperson. You can answer a lot of questions using aggregations and more importantly, discover insights out of your data.</p><p>Now let’s answer the second question we have: <em>“</em><strong><em>How many purchases by day were originated by people who bought at least 2 times in the past 30 days and are from “New York” or “San Francisco”?</em></strong><em>”</em>. We can easily answer this question by another filtered histogram aggregation.</p><p><a href="https://docs.slicingdice.com/docs/aggregations">Histogram aggregations</a> are great to understand how a determined metric on a event column (like purchases) is distributed along a time interval.</p><p>Let’s take as example our query below, that we are asking SlicingDice to: <br>1. first filter just the customers that has “actions” column value equals to “purchase” between “now” and the “last 30 days” AND has “New York” or “San Francisco” as “city” values.<br>2. next make a count of events that happened for the “purchase” column between “now” and the “last 30 days”;<br>3. finally group the quantity of purchases per day.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0bf6d03a8ad5df914d0fd6c40badd266/href">https://medium.com/media/0bf6d03a8ad5df914d0fd6c40badd266/href</a></iframe><p>Based on the data we inserted before, if you run this query above on your own terminal, you should be able to see these results below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/adc618d955145e413f1888ebecd36763/href">https://medium.com/media/adc618d955145e413f1888ebecd36763/href</a></iframe><p>As you can see, the results are basically showing the quantity of purchases per day that were originated by customers that made at least two purchases in the past 30 days and that are from “New York” or “San Francisco”.</p><p>Now, if you want to know who these customers are, you can simply make this <a href="https://docs.slicingdice.com/docs/result-extraction">result data extraction</a> query below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/909c1c83b431bd37cd6b4e20fc3aee9b/href">https://medium.com/media/909c1c83b431bd37cd6b4e20fc3aee9b/href</a></iframe><p>As you can see below, the result is showing that the <strong>customer-01</strong> and <strong>customer-03</strong> are the ones that made more than two purchases in the past 30 days and are from “New York” or “San Francisco”.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ce55d747d40daf128b0366023a93a9eb/href">https://medium.com/media/ce55d747d40daf128b0366023a93a9eb/href</a></iframe><h3>What other questions and analysis can I make?</h3><p>SlicingDice supports <a href="https://docs.slicingdice.com/docs/how-to-make-queries">multiple types of data analysis</a>, so you can basically answer any kind of question you may need for analytics purposes, for example:</p><ul><li>What number of customers reached each sales funnel step?</li><li>What is the average revenue per customer in the past 30 days from customers that bought “product A“ and “product B” ?</li></ul><h3>You nailed it, hero! — Next steps</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*2l2udxr7w9iiH6yLfvV-_A.gif" /></figure><p><strong>That’s it.</strong> You are now ready to start making as much CRM analysis as you want.<br>If you are inclined to think that SlicingDice might work for you, we suggest you take a look on <a href="https://docs.slicingdice.com/">our documentation</a> and at least follow our <a href="https://docs.slicingdice.com/docs/quickstart-guide">quickstart guide</a>.</p><p>Please, don’t hesitate to contact our <a href="https://www.slicingdice.com/faq-and-contact"><strong>developer support team</strong></a> <strong>at any time, for any reason</strong>. We are here to support your needs.</p><h3>Loved it… but, how much does it cost?</h3><p><a href="https://blog.slicingdice.com/slicingdice-pricing-model-and-competitors-comparison-31f1c9f0f076">Our price is really innovative and cheap</a>. We charge based on the <strong>quantity of columns</strong> you have, doesn’t matter how many rows you store for them.</p><p>So for example you can store <strong>unlimited data</strong> on SlicingDice for these two use cases presented above (customers, for example) <strong>for less $ 10.00 per month</strong>. It’s true. <a href="https://www.slicingdice.com/pricing">Check our website pricing page</a>.</p><h3>Why SlicingDice?</h3><p>Developers want to store and query their data, but they hate having to manage complex data infrastructure, so <strong>we do it for them</strong>.<br>All they have to do is simply store and query billions of <strong>real-time and historical data,</strong> <strong>without managing any infrastructure</strong>.</p><p><strong>High availability?</strong><br>You don’t need to worry. We always replicate and backup your data <strong>on three different datacenters</strong>, located in <strong>France, Canada</strong> and <strong>Germany</strong>.</p><p><strong>Query speed?</strong><br>If any query takes <strong>longer than 10 seconds to complete</strong>, no matter the query complexity or data size, you receive a <strong>10¢ discount</strong> for each query. We believe ensuring fast queries is <strong>our responsibility, not yours</strong>.</p><h3>Not sure if we can support your needs?</h3><p><a href="https://calendly.com/slicingdice/dev15min/"><strong>Click here and schedule</strong></a> a 15-minute talk with <strong>our developers</strong>, totally free of charge, so we can evaluate your case together.</p><p>Don’t know how to model your data in order to send it to SlicingDice? <br>No problem at all, <a href="https://calendly.com/slicingdice/dev15min/"><strong>schedule a time</strong></a> so we can talk or <a href="https://www.slicingdice.com/faq-and-contact"><strong>let’s chat online now</strong></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=482b00eec2c2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slicingdice-com-blog/crm-analytics-in-10-minutes-482b00eec2c2">CRM Analytics in 10 minutes</a> was originally published in <a href="https://medium.com/slicingdice-com-blog">SlicingDice.com Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Server Monitoring and Log Analysis in 10 minutes]]></title>
            <link>https://medium.com/slicingdice-com-blog/server-monitoring-and-log-analysis-in-10-minutes-115252690b6c?source=rss-45dd2f3ce3c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/115252690b6c</guid>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[network-monitoring]]></category>
            <category><![CDATA[log-analysis]]></category>
            <category><![CDATA[slicingdice]]></category>
            <dc:creator><![CDATA[SlicingDice Team]]></dc:creator>
            <pubDate>Sun, 23 Apr 2017 18:18:14 GMT</pubDate>
            <atom:updated>2017-05-29T19:09:28.608Z</atom:updated>
            <content:encoded><![CDATA[<h3>Server and Log Monitoring in 10 minutes</h3><p>Go <strong>from zero to server and log monitoring analysis hero in less than 10 minutes</strong>, without managing any infrastructure or worrying about data size.</p><p>This guide will show how to use <a href="http://www.slicingdice.com/">SlicingDice</a> for server monitoring and log analysis, a <strong>Serverless Data Warehouse and Analytics Database</strong>.</p><p>Everyday SlicingDice receives <strong>more than 1.1 billion data inserts</strong> and <strong>millions of queries</strong> from multiple indie devs and companies, many of them doing <strong>analytics on top of server monitoring data</strong>, such as disk usage.</p><h4>Scenario description</h4><p>Let’s imagine you collect data from the servers hosting your apps and want to verify their usage and stability.</p><h4>Example of server monitoring questions we want to answer:</h4><ol><li>What was the average available disk space from Data Center 1 servers yesterday?</li><li>How many servers presented some instability in the past 24 hours?</li></ol><h3>Sending your server monitoring data to SlicingDice</h3><p>Sending data to SlicingDice is <strong>very simple and fast</strong>. You can use our <a href="https://docs.slicingdice.com/docs/quickstart-guide"><strong>easy-to-use API</strong></a> or any of our clients available in <a href="https://docs.slicingdice.com/docs/python-client-sdk"><strong>Python</strong></a>, <a href="https://docs.slicingdice.com/docs/ruby-client-sdk"><strong>Ruby</strong></a>, <a href="https://docs.slicingdice.com/docs/javascript-client-sdk"><strong>JavaScript</strong></a>, <a href="https://docs.slicingdice.com/docs/java-client-sdk"><strong>Java</strong></a>, <a href="https://docs.slicingdice.com/docs/net-csharp-client-sdk"><strong>.NET/C#</strong></a>, <a href="https://docs.slicingdice.com/docs/php-client-sdk"><strong>PHP</strong></a>, <a href="https://docs.slicingdice.com/docs/go-client-sdk"><strong>Go</strong></a> and <a href="https://docs.slicingdice.com/docs/arduino-client-sdk"><strong>Arduino</strong></a>.</p><p>In order to send your data, first you simply need to:<br>1. Define what your entity is going to be. We consider an entity to be like a car, a sensor, a server and so on. That’s basically a way of saying: who owns the data? So looking the questions above, the data is clearly produced by a server, so each server would be an entity.</p><p>2. Once you know what is your entity, you simply need to specify the columns and values you want to associate to your entities.</p><h4>Check this data insertion example below</h4><blockquote><strong><em>Pro Tip:</em></strong><em> </em><a href="https://panel.slicingdice.com/generate-demo-key"><em>Click here to generate a </em><strong><em>personal free demo API Key</em></strong></a><em>, so you can copy &amp; paste all the cURL command examples below on your own terminal and </em><strong><em>play with it live</em></strong><em> using our </em><a href="https://docs.slicingdice.com/docs/api-keys#section-demo-api-key"><em>/test endpoint</em></a><em>.</em></blockquote><p>In this example our entities are <strong>servers</strong> and we will be inserting the data center they belong and the disk space usage.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/df2269b3360dc21e20f3fcbb3b7057e0/href">https://medium.com/media/df2269b3360dc21e20f3fcbb3b7057e0/href</a></iframe><p>Looking this data insertion command above, we can clearly see that we have three <strong>server</strong> entities: <strong>server-01</strong>, <strong>server-02</strong> and <strong>server-03</strong>.</p><p>For these two entities we associated two columns: <strong>datacenter</strong> and <strong>disk-space</strong>.</p><p>As you can see, all entities <strong>server-01</strong>, <strong>server-02</strong> and <strong>server-03</strong> have the same columns <strong>datacenter</strong> and <strong>disk-space</strong>, but each with different values.</p><p>What is happening here is that you are telling SlicingDice that the <strong>datacenter</strong> of the entity <strong>server-01</strong> is “1” and also that the <strong>disk-space</strong> was “0.73” for the date “2017–xx–xxT00:00:00Z”, “0.69” on “2017–xx–xxT06:00:00Z” and so on.</p><p>The exactly same thing is happening for the entities <strong>server-02</strong> and <strong>server-03</strong>, but in a different datacenter and with different disk usage values.</p><p>Before starting to query this data, <strong>let’s see another insertion example:</strong><br><strong><em>Again:</em></strong><em> if you paste your </em><a href="https://panel.slicingdice.com/generate-demo-key/"><strong><em>personal demo API key</em></strong></a><em> on this cURL command below and execute it on your terminal, it will really work. Go ahead and try yourself.</em></p><p>In this example below our entities are still <strong>servers</strong> and we will be inserting the server name and its current status.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/78c66e1c966e3a12f32deee8ca744f92/href">https://medium.com/media/78c66e1c966e3a12f32deee8ca744f92/href</a></iframe><p>Again, can clearly see that we have three <strong>server</strong> entities: <strong>server-01</strong>, <strong>server-02</strong> and <strong>server-03</strong>.</p><p>All entities are sharing the same columns called <strong>server-name</strong> and <strong>status</strong>, although each entity has its own values associated to the columns.</p><p>What is happening here is that you are telling SlicingDice to store that the entity <strong>server-01</strong> has the <strong>server-name</strong> “Server 1 — Data Center 1” and that its <strong>status</strong> on date “2017–xx–xxT01:26:20Z” was “stable”, but that on “2017–xx–xxT11:52:38Z” is was “unstable”.</p><p>That’s it. Simple like that. As we now have some data stored, let’s answer the questions we defined in the beginning of this post:</p><ol><li>What was the average available disk space from Data Center 1 servers yesterday?</li><li>How many servers presented some instability in the past 24 hours?</li></ol><h3>Querying your data</h3><p>Making queries on SlicingDice is simple and easy. It’s possible to do <a href="https://docs.slicingdice.com/docs/how-to-make-queries"><strong>multiple types of analysis using our API</strong></a><strong> </strong>and you can get to speed by seeing all the ready-to-use query examples we have on our Github clients repositories for <a href="https://github.com/SlicingDice/slicingdice-python/tree/master/tests_and_examples"><strong>Python</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-ruby/tree/master/tests_and_examples"><strong>Ruby</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-javascript/tree/master/tests_and_examples"><strong>JavaScript</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-java/tree/master/src/test/java/com/slicingdice/jslicer"><strong>Java</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-dot-net/tree/master/TestsAndExamples"><strong>.NET/C#</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-php/tree/master/tests_and_examples"><strong>PHP</strong></a>, and <a href="https://github.com/SlicingDice/slicingdice-go/tree/master/tests_and_examples"><strong>Go</strong></a>.</p><p>In order to answer the question <em>“</em><strong><em>What was the average available disk space from Data Center 1 servers yesterday?</em></strong><em>”</em> we will be making an <a href="https://docs.slicingdice.com/docs/aggregations">aggregation analysis</a>.</p><p><a href="https://docs.slicingdice.com/docs/aggregations">Aggregation</a> is a powerful way to cross data in order to find insights and unexpected patterns. You can think about it like being an Excel <a href="https://en.wikipedia.org/wiki/Pivot_table">Pivot Table</a>.</p><p>What is happening on this aggregation query below is that we are asking SlicingDice to first filter all servers (entities) from the “datacenter 1” and then make an average on all the values for the “disk-space” column that were generated “yesterday”.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9360c90a71a013b6937c266c62a2c503/href">https://medium.com/media/9360c90a71a013b6937c266c62a2c503/href</a></iframe><p>Based on the data we inserted before, if you run this query above on your own terminal, you should be able to see these results below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/97d40e42eed3e0be0a5320b60627637b/href">https://medium.com/media/97d40e42eed3e0be0a5320b60627637b/href</a></iframe><p>As you can see, the result is basically showing the yesterday’s average of disk utilization from the data center 1 servers. You can answer a lot of questions using aggregations and more importantly, discover insights out of your data.</p><p>Now let’s answer the second question we have: <em>“</em><strong><em>How many servers presented some instability in the past 24 hours?</em></strong><em>”</em>. We can easily answer this question by using the <a href="https://docs.slicingdice.com/docs/count-entities">count entities analysis</a>.</p><p><a href="https://docs.slicingdice.com/docs/count-entities">Count entities</a> is a simply and fast way to know how many unique entities (servers) you have that satisfies some set of conditions you define.</p><p>Let’s take as example our query below, what is happening here is that we want to know how many unique servers (entities) have the “status” value as “unstable” in the “last 24 hours”.</p><p>Note that we are putting a name for this query (number-of-unstable-servers) because our API accepts making multiple count queries in a single request.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/05bc7b0aae4f0631344399c534cabe80/href">https://medium.com/media/05bc7b0aae4f0631344399c534cabe80/href</a></iframe><p>Based on the data we inserted before, if you run this query above on your own terminal, you should be able to see these results below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/fcd867eba33450e9aefd38820d625df5/href">https://medium.com/media/fcd867eba33450e9aefd38820d625df5/href</a></iframe><p>As you can see, the results are basically showing the <strong>1 server (entity)</strong> presented some instability in the last 24 hours.</p><p>Now, if you want to know what server exactly was unstable, you can simply make this <a href="https://docs.slicingdice.com/docs/result-extraction">result data extraction</a> query below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b76ef76bd90fcef22119081dc9f67ce8/href">https://medium.com/media/b76ef76bd90fcef22119081dc9f67ce8/href</a></iframe><p>As you can see below, it’s showing that the server <strong>server-02</strong> was the one unstable.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/eec49d6588f27082a05f36bb5db6557e/href">https://medium.com/media/eec49d6588f27082a05f36bb5db6557e/href</a></iframe><h3>What other questions and analysis can I make?</h3><p>SlicingDice supports <a href="https://docs.slicingdice.com/docs/how-to-make-queries">multiple types of data analysis</a>, so you can basically answer any kind of question you may need for analytics purposes, for example:</p><ul><li>What is the distribution of server disk availability from datacenter 2, per server per day in the past 24 hours?</li><li>How many log errors happened in the past 5 minutes?</li></ul><h3>You nailed it, hero! — Next steps</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*2l2udxr7w9iiH6yLfvV-_A.gif" /></figure><p><strong>That’s it.</strong> You are now ready to start making as much server and log analysis as you want.<br>If you are inclined to think that SlicingDice might work for you, we suggest you take a look on <a href="https://docs.slicingdice.com/">our documentation</a> and at least follow our <a href="https://docs.slicingdice.com/docs/quickstart-guide">quickstart guide</a>.</p><p>Please, don’t hesitate to contact our <a href="https://www.slicingdice.com/faq-and-contact"><strong>developer support team</strong></a> <strong>at any time, for any reason</strong>. We are here to support your needs.</p><h3>Loved it… but, how much does it cost?</h3><p><a href="https://blog.slicingdice.com/slicingdice-pricing-model-and-competitors-comparison-31f1c9f0f076">Our price is really innovative and cheap</a>. We charge based on the <strong>quantity of columns</strong> you have, doesn’t matter how many rows you store for them.</p><p>So for example you can store <strong>unlimited data</strong> on SlicingDice for these two use cases presented above (server, for example) <strong>for less $ 10.00 per month</strong>. It’s true. <a href="https://www.slicingdice.com/pricing">Check our website pricing page</a>.</p><h3>Why SlicingDice?</h3><p>Developers want to store and query their data, but they hate having to manage complex data infrastructure, so <strong>we do it for them</strong>.<br>All they have to do is simply store and query billions of <strong>real-time and historical data,</strong> <strong>without managing any infrastructure</strong>.</p><p><strong>High availability?</strong><br>You don’t need to worry. We always replicate and backup your data <strong>on three different datacenters</strong>, located in <strong>France, Canada</strong> and <strong>Germany</strong>.</p><p><strong>Query speed?</strong><br>If any query takes <strong>longer than 10 seconds to complete</strong>, no matter the query complexity or data size, you receive a <strong>10¢ discount</strong> for each query. We believe ensuring fast queries is <strong>our responsibility, not yours</strong>.</p><h3>Not sure if we can support your needs?</h3><p><a href="https://calendly.com/slicingdice/dev15min/"><strong>Click here and schedule</strong></a> a 15-minute talk with <strong>our developers</strong>, totally free of charge, so we can evaluate your case together.</p><p>Don’t know how to model your data in order to send it to SlicingDice? <br>No problem at all, <a href="https://calendly.com/slicingdice/dev15min/"><strong>schedule a time</strong></a> so we can talk or <a href="https://www.slicingdice.com/faq-and-contact"><strong>let’s chat online now</strong></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=115252690b6c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slicingdice-com-blog/server-monitoring-and-log-analysis-in-10-minutes-115252690b6c">Server Monitoring and Log Analysis in 10 minutes</a> was originally published in <a href="https://medium.com/slicingdice-com-blog">SlicingDice.com Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Analytics in 10 minutes]]></title>
            <link>https://medium.com/slicingdice-com-blog/web-analytics-in-10-minutes-4184999c310b?source=rss-45dd2f3ce3c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/4184999c310b</guid>
            <category><![CDATA[slicingdice]]></category>
            <category><![CDATA[web-analytics]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[big-data-analytics]]></category>
            <category><![CDATA[web-analytics-tool]]></category>
            <dc:creator><![CDATA[SlicingDice Team]]></dc:creator>
            <pubDate>Sun, 23 Apr 2017 17:24:58 GMT</pubDate>
            <atom:updated>2017-05-29T19:05:29.655Z</atom:updated>
            <content:encoded><![CDATA[<p>Go <strong>from zero to web analytics hero in less than 10 minutes</strong>, without managing any infrastructure or worrying about data modeling and size.</p><p>This guide will show how to use <a href="http://www.slicingdice.com/">SlicingDice</a> for web analytics, a <strong>Serverless Data Warehouse and Analytics Database as a Service</strong>.</p><p>Everyday SlicingDice receives <strong>more than 1.1 billion data inserts</strong> and <strong>millions of queries</strong> from multiple indie devs and companies, many of them doing <strong>analytics on top of website data</strong>, such as visits and page views.</p><h4>Scenario description</h4><p>Let’s imagine you collect web page access data for web analytics purposes in order to understand how your website is being used and to collect information on its pages contents.</p><h4>Example of web analytics questions we want to answer:</h4><ol><li>What was the average load time of our webpages in the past week?</li><li>How many webpages from our website containing the words “love” and “peace” were accessed more than 3 times in the past 7 days?</li></ol><h3>Sending your web page access data to SlicingDice</h3><p>Sending data to SlicingDice is <strong>very simple and fast</strong>. You can use our <a href="https://docs.slicingdice.com/docs/quickstart-guide"><strong>easy-to-use API</strong></a> or any of our clients available in <a href="https://docs.slicingdice.com/docs/python-client-sdk"><strong>Python</strong></a>, <a href="https://docs.slicingdice.com/docs/ruby-client-sdk"><strong>Ruby</strong></a>, <a href="https://docs.slicingdice.com/docs/javascript-client-sdk"><strong>JavaScript</strong></a>, <a href="https://docs.slicingdice.com/docs/java-client-sdk"><strong>Java</strong></a>, <a href="https://docs.slicingdice.com/docs/net-csharp-client-sdk"><strong>.NET/C#</strong></a>, <a href="https://docs.slicingdice.com/docs/php-client-sdk"><strong>PHP</strong></a>, <a href="https://docs.slicingdice.com/docs/go-client-sdk"><strong>Go</strong></a> and <a href="https://docs.slicingdice.com/docs/arduino-client-sdk"><strong>Arduino</strong></a>.</p><p>In order to send your data, first you simply need to:<br>1. Define what your entity is going to be. We consider an entity to be like a user, a page, a server and so on. That’s basically a way of saying: who owns the data? So looking both questions above, the data is clearly produced by a web page, so we can consider each web page to be an entity.</p><p>2. Once you know what is your entity, you simply need to specify the columns and values you want to associate to your entities.</p><h4>Check this data insertion example below</h4><blockquote><strong><em>Pro Tip:</em></strong><em> </em><a href="https://panel.slicingdice.com/generate-demo-key"><em>Click here to generate a </em><strong><em>personal free demo API Key</em></strong></a><em>, so you can copy &amp; paste all the cURL command examples below on your own terminal and </em><strong><em>play with it live</em></strong><em> using our </em><a href="https://docs.slicingdice.com/docs/api-keys#section-demo-api-key"><em>/test endpoint</em></a><em>.</em></blockquote><p>In this example below our entities are <strong>web pages </strong>and we will be inserting page load times for each one of them.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f34d26851476d36e134fe888cdd464e7/href">https://medium.com/media/f34d26851476d36e134fe888cdd464e7/href</a></iframe><p>Looking this data insertion command above, we can clearly see that we have three <strong>web page </strong>entities: <strong>/index</strong>, <strong>/contact</strong> and <strong>/dashboard</strong>.</p><p>All entities are sharing the same column called <strong>loadtime</strong>, although each entity has its own values and dates associated to the column.</p><p>What is happening here is that you are telling SlicingDice to store that the entity <strong>/index</strong> had a <strong>loadtime</strong> of “1.223” on date “2017–xx–xxT02:33:09Z”, and the entity <strong>/contact</strong> had a <strong>loadtime</strong> of “2.348” on date “2017–xx–xxT12:30:18Z” and so on.</p><p>Before starting to query this data, <strong>let’s see another insertion example:</strong><br><strong><em>Again:</em></strong><em> if you paste your </em><a href="https://panel.slicingdice.com/generate-demo-key/"><strong><em>personal demo API key</em></strong></a><em> on this cURL command below and execute it on your terminal, it will really work. Go ahead and try yourself.</em></p><p>In this example below our entities are still <strong>web pages </strong>and we will insert all the visits and the page views generated by visitors.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/26fd6570724a21eb9afdbb2df02084bb/href">https://medium.com/media/26fd6570724a21eb9afdbb2df02084bb/href</a></iframe><p>Again, we can clearly see that we have three <strong>web page </strong>entities: <strong>/index</strong>, <strong>/contact</strong> and <strong>/blog/feelings</strong>.</p><p>For these three entities we associated two columns: <strong>words</strong> and <strong>actions</strong>.</p><p>As you can see, all entities <strong>/index</strong>, <strong>/contact</strong> and <strong>/blog/feelings</strong> have the same columns <strong>words</strong> and <strong>actions</strong>, but each with different values.</p><p>What is happening here is that you are telling SlicingDice that the <strong>words</strong> of the entity <strong>/index</strong> are [”welcome”, “slicingdice”, “data”, “warehouse”, “analytics”, “database”, “service”] and also that the <strong>actions</strong> was “access” on “2017–xx–xxT02:33:09Z”, on “2017–xx–xxT04:57:11Z” and so on.</p><p>The exactly same thing is happening for the entities <strong>/contact</strong> and <strong>/blog/feelings</strong>, but with different words and actions.</p><p>That’s it. Simple like that. As we now have some data stored, let’s answer the questions we defined in the beginning of this post:</p><ol><li>What was the average load time of our webpages in the past week?</li><li>How many webpages from our website containing the words “love” and “peace” were accessed more than 3 times in the past 7 days?</li></ol><h3>Querying your data</h3><p>Making queries on SlicingDice is simple and easy. It’s possible to do <a href="https://docs.slicingdice.com/docs/how-to-make-queries"><strong>multiple types of analysis using our API</strong></a><strong> </strong>and you can get to speed by seeing all the ready-to-use query examples we have on our Github clients repositories for <a href="https://github.com/SlicingDice/slicingdice-python/tree/master/tests_and_examples"><strong>Python</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-ruby/tree/master/tests_and_examples"><strong>Ruby</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-javascript/tree/master/tests_and_examples"><strong>JavaScript</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-java/tree/master/src/test/java/com/slicingdice/jslicer"><strong>Java</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-dot-net/tree/master/TestsAndExamples"><strong>.NET/C#</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-php/tree/master/tests_and_examples"><strong>PHP</strong></a>, and <a href="https://github.com/SlicingDice/slicingdice-go/tree/master/tests_and_examples"><strong>Go</strong></a>.</p><p>In order to answer the question <em>“</em><strong><em>What was the average load time of our webpages in the past week?</em></strong><em>”</em> we will be making an <a href="https://docs.slicingdice.com/docs/aggregations">aggregation analysis</a>.</p><p><a href="https://docs.slicingdice.com/docs/aggregations">Aggregation</a> is a powerful way to cross data in order to find insights and unexpected patterns. You can think about it like being an Excel <a href="https://en.wikipedia.org/wiki/Pivot_table">Pivot Table</a>.</p><p>What is happening on this aggregation query below is that we are asking SlicingDice to get the average of all the “loadtime” values that took place between “now” and “1 week ago”.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d2dce8fdd069a53d933e538b4d38bbff/href">https://medium.com/media/d2dce8fdd069a53d933e538b4d38bbff/href</a></iframe><p>Based on the data we inserted before, if you run this query above on your own terminal, you should be able to see these results below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/59a0013ea785ea2a9c8cfe1879a677a8/href">https://medium.com/media/59a0013ea785ea2a9c8cfe1879a677a8/href</a></iframe><p>As you can see, the result is basically showing the average load time from all page load times stored in the past 7 days. You can answer a lot of questions using aggregations and more importantly, discover insights out of your data.</p><p>Now let’s answer the second question we have: <em>“</em><strong><em>How many webpages from our website containing the words “love” and “peace” were accessed more than 3 times in the past 7 days?</em></strong><em>”</em>. We can easily answer this question by using the <a href="https://docs.slicingdice.com/docs/count-entities">count entities analysis</a>.</p><p><a href="https://docs.slicingdice.com/docs/count-entities">Count entities</a> is a simply and fast way to know how many unique entities (web pages) you have that satisfies some set of conditions you define.</p><p>Let’s take as example our query below, what is happening here is that we want to know how many unique web pages (entities) have the “words” column with “love” AND “peace” values AND that had more than 3 “actions” values between “now” and “7 days ago”.</p><p>Note that we are putting a name for this query (love-and-peace-with-3-or-more-accesses) because our API accepts making multiple count queries in a single request.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/926664eed35ec3c87fd22e7b374af1eb/href">https://medium.com/media/926664eed35ec3c87fd22e7b374af1eb/href</a></iframe><p>Based on the data we inserted before, if you run this query above on your own terminal, you should be able to see these results below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2d70b005e1bad2536e38a1cc2abd872f/href">https://medium.com/media/2d70b005e1bad2536e38a1cc2abd872f/href</a></iframe><p>As you can see, the result is basically showing that there is <strong>1 web page (entity)</strong> with both words on content and that were accessed more than 3 times in the last 7 days.</p><p>Now, if you want to know what web pages (entities) are these, you can simply make this <a href="https://docs.slicingdice.com/docs/result-extraction">result data extraction</a> query below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e7d38327cf6e4fbd667d2af3cdf6a085/href">https://medium.com/media/e7d38327cf6e4fbd667d2af3cdf6a085/href</a></iframe><p>As you can see below, it’s showing that the web page <strong>/blog/feelings</strong> is the one that has the words and was accessed more than 3 times in last 7 days.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c8eab3225852a0ed0542c1eff5123d1f/href">https://medium.com/media/c8eab3225852a0ed0542c1eff5123d1f/href</a></iframe><h3>What other questions and analysis can I make?</h3><p>SlicingDice supports <a href="https://docs.slicingdice.com/docs/how-to-make-queries">multiple types of data analysis</a>, so you can basically answer any kind of question you may need for analytics purposes, for example:</p><ul><li>What ware the main referrers for each web page</li><li>What are the top entry and exit pages of my website?</li><li>What was the distribution of the most accessed pages per day in the past month?</li><li>What are the most accessed pages containing “election” in their title?</li></ul><h3>You nailed it, hero! — Next steps</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*2l2udxr7w9iiH6yLfvV-_A.gif" /></figure><p><strong>That’s it.</strong> You are now ready to start making as much web analytics as you want.<br>If you are inclined to think that SlicingDice might work for you, we suggest you take a look on <a href="https://docs.slicingdice.com/">our documentation</a> and at least follow our <a href="https://docs.slicingdice.com/docs/quickstart-guide">quickstart guide</a>.</p><p>Please, don’t hesitate to contact our <a href="https://www.slicingdice.com/faq-and-contact"><strong>developer support team</strong></a> <strong>at any time, for any reason</strong>. We are here to support your needs.</p><h3>Loved it… but, how much does it cost?</h3><p><a href="https://blog.slicingdice.com/slicingdice-pricing-model-and-competitors-comparison-31f1c9f0f076">Our price is really innovative and cheap</a>. We charge based on the <strong>quantity of columns</strong> you have, doesn’t matter how many rows you store for them.</p><p>So for example you can store <strong>unlimited data</strong> on SlicingDice for these two use cases presented above (web pages, for example) <strong>for less $ 10.00 per month</strong>. It’s true. <a href="https://www.slicingdice.com/pricing">Check our website pricing page</a>.</p><h3>Why SlicingDice?</h3><p>Developers want to store and query their data, but they hate having to manage complex data infrastructure, so <strong>we do it for them</strong>.<br>All they have to do is simply store and query billions of <strong>real-time and historical data,</strong> <strong>without managing any infrastructure</strong>.</p><p><strong>High availability?</strong><br>You don’t need to worry. We always replicate and backup your data <strong>on three different datacenters</strong>, located in <strong>France, Canada</strong> and <strong>Germany</strong>.</p><p><strong>Query speed?</strong><br>If any query takes <strong>longer than 10 seconds to complete</strong>, no matter the query complexity or data size, you receive a <strong>10¢ discount</strong> for each query. We believe ensuring fast queries is <strong>our responsibility, not yours</strong>.</p><h3>Not sure if we can support your needs?</h3><p><a href="https://calendly.com/slicingdice/dev15min/"><strong>Click here and schedule</strong></a> a 15-minute talk with <strong>our developers</strong>, totally free of charge, so we can evaluate your case together.</p><p>Don’t know how to model your data in order to send it to SlicingDice? <br>No problem at all, <a href="https://calendly.com/slicingdice/dev15min/"><strong>schedule a time</strong></a> so we can talk or <a href="https://www.slicingdice.com/faq-and-contact"><strong>let’s chat online now</strong></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4184999c310b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slicingdice-com-blog/web-analytics-in-10-minutes-4184999c310b">Web Analytics in 10 minutes</a> was originally published in <a href="https://medium.com/slicingdice-com-blog">SlicingDice.com Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sales and Business Analytics in 10 minutes]]></title>
            <link>https://medium.com/slicingdice-com-blog/sales-and-business-analytics-in-10-minutes-2c1655bb802e?source=rss-45dd2f3ce3c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c1655bb802e</guid>
            <category><![CDATA[business-intelligence]]></category>
            <category><![CDATA[big-data-analytics]]></category>
            <category><![CDATA[business-analytics]]></category>
            <category><![CDATA[slicingdice]]></category>
            <category><![CDATA[business-analysis]]></category>
            <dc:creator><![CDATA[SlicingDice Team]]></dc:creator>
            <pubDate>Fri, 21 Apr 2017 03:51:21 GMT</pubDate>
            <atom:updated>2017-05-29T19:01:12.888Z</atom:updated>
            <content:encoded><![CDATA[<p>Go <strong>from zero to sales and business analytics hero in less than 10 minutes</strong>, without managing any infrastructure or worrying about data size.</p><p>This guide will show how to use <a href="http://www.slicingdice.com/">SlicingDice</a> for sales and business analytics, a <strong>Serverless Data Warehouse and Analytics Database as a Service</strong>.</p><p>Everyday SlicingDice receives <strong>more than 1.1 billion data inserts</strong> and <strong>millions of queries</strong> from multiple indie devs and companies, many of them doing <strong>analytics on top of sales and business data</strong>, such as transactions.</p><h4>Scenario description</h4><p>Let’s imagine you have sales and business data from your company CRM and want to use it to run analytics and make data-oriented decisions.</p><h4>Example of sales and business questions we want to answer:</h4><ol><li>What is the average lead monetary value by status by salesperson in the last 48 hours?</li><li>How many purchases by day were originated by people who bought at least 2 times in the past 30 days and are from “New York” or “San Francisco”?</li></ol><h3>Sending your sales and business data to SlicingDice</h3><p>Sending data to SlicingDice is <strong>very simple and fast</strong>. You can use our <a href="https://docs.slicingdice.com/docs/quickstart-guide"><strong>easy-to-use API</strong></a> or any of our clients available in <a href="https://docs.slicingdice.com/docs/python-client-sdk"><strong>Python</strong></a>, <a href="https://docs.slicingdice.com/docs/ruby-client-sdk"><strong>Ruby</strong></a>, <a href="https://docs.slicingdice.com/docs/javascript-client-sdk"><strong>JavaScript</strong></a>, <a href="https://docs.slicingdice.com/docs/java-client-sdk"><strong>Java</strong></a>, <a href="https://docs.slicingdice.com/docs/net-csharp-client-sdk"><strong>.NET/C#</strong></a>, <a href="https://docs.slicingdice.com/docs/php-client-sdk"><strong>PHP</strong></a>, <a href="https://docs.slicingdice.com/docs/go-client-sdk"><strong>Go</strong></a> and <a href="https://docs.slicingdice.com/docs/arduino-client-sdk"><strong>Arduino</strong></a>.</p><p>In order to send your data, first you simply need to:<br>1. Define what your entity is going to be. We consider an entity to be like a car, a user, a server and so on. That’s basically a way of saying: who owns the data? So looking the first question above, the data is clearly produced by sales leads, and on the second, each entity could be a customer.</p><p>2. Once you know what is your entity, you simply need to specify the columns and values you want to associate to your entities.</p><h4>Check this data insertion example below</h4><blockquote><strong><em>Pro Tip:</em></strong><em> </em><a href="https://panel.slicingdice.com/generate-demo-key"><em>Click here to generate a </em><strong><em>personal free demo API Key</em></strong></a><em>, so you can copy &amp; paste all the cURL command examples below on your own terminal and </em><strong><em>play with it live</em></strong><em> using our </em><a href="https://docs.slicingdice.com/docs/api-keys#section-demo-api-key"><em>/test endpoint</em></a><em>.</em></blockquote><p>In this example our entities are <strong>sales leads </strong>and we will be inserting all the lead details, such as ticket size, salesperson and status.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b85ec731c2830461b3e9b7d50dc6c438/href">https://medium.com/media/b85ec731c2830461b3e9b7d50dc6c438/href</a></iframe><p>Looking this data insertion command above, we can clearly see that we have three <strong>sales lead </strong>entities: <strong>lead-01</strong>, <strong>lead-02</strong> and <strong>lead-03</strong>.</p><p>For these three entities we associated three columns: <strong>ticket</strong>, <strong>salesperson</strong> and <strong>lead-status</strong>.</p><p>As you can see, all entities <strong>lead-01</strong>, <strong>lead-02</strong> and <strong>lead-03</strong> have the same columns <strong>ticket</strong>, <strong>salesperson</strong> and <strong>lead-status</strong>, but each with different values.</p><p>What is happening here is that you are telling SlicingDice that the <strong>ticket</strong> of the entity <strong>lead-01</strong> was “489745.12”, the <strong>salesperson</strong> is “Glenna” and also that <strong>lead-status</strong> was “first-contact” for the date “2017–xx–xxT00:33:09Z”, “negotiating” on “2017–xx–xxT04:30:18Z” and so on.</p><p>The exactly same thing is happening for the entities <strong>lead-02</strong> and <strong>lead-03</strong>, but with different values for the columns.</p><p>Before starting to query this data, <strong>let’s see another insertion example:</strong><br><strong><em>Again:</em></strong><em> if you paste your </em><a href="https://panel.slicingdice.com/generate-demo-key/"><strong><em>personal demo API key</em></strong></a><em> on this cURL command below and execute it on your terminal, it will really work. Go ahead and try yourself.</em></p><p>In this example below our entities are <strong>customers</strong> and we will be inserting the city, actions and purchases for each of them.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2bf0b046863529b4771222545e7be623/href">https://medium.com/media/2bf0b046863529b4771222545e7be623/href</a></iframe><p>Again, we can clearly see that we have four <strong>customers</strong> entities: <strong>customer-01</strong>, <strong>customer-02</strong>, <strong>customer-03</strong> and <strong>customer-04</strong>.</p><p>Coincidentally all entities are sharing the same columns, <strong>city</strong>, <strong>actions</strong> and <strong>purchases</strong>, although each entity has its own values associated to the columns. It’s important to note that not all entities have to have the same columns.</p><p>What is happening here is that you are telling SlicingDice to store that the <strong>city</strong> of the <strong>customer-01</strong> is “New York”, that he made multiple <strong>actions</strong>, such as “purchase” on “2017–xx–xxT06:42:42Z”, and also made multiple <strong>purchases</strong>, such as “600.00” on “2017–xx–xxT06:42:42Z”.</p><p>That’s it. Simple like that. As we now have some data stored, let’s answer the questions we defined in the beginning of this post:</p><ol><li>What is the average lead monetary value by status by salesperson in the last 48 hours?</li><li>How many purchases by day were originated by people who bought at least 2 times in the past 30 days and are from “New York” or “San Francisco”?</li></ol><h3>Querying your data</h3><p>Making queries on SlicingDice is simple and easy. It’s possible to do <a href="https://docs.slicingdice.com/docs/how-to-make-queries"><strong>multiple types of analysis using our API</strong></a><strong> </strong>and you can get to speed by seeing all the ready-to-use query examples we have on our Github clients repositories for <a href="https://github.com/SlicingDice/slicingdice-python/tree/master/tests_and_examples"><strong>Python</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-ruby/tree/master/tests_and_examples"><strong>Ruby</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-javascript/tree/master/tests_and_examples"><strong>JavaScript</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-java/tree/master/src/test/java/com/slicingdice/jslicer"><strong>Java</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-dot-net/tree/master/TestsAndExamples"><strong>.NET/C#</strong></a>, <a href="https://github.com/SlicingDice/slicingdice-php/tree/master/tests_and_examples"><strong>PHP</strong></a>, and <a href="https://github.com/SlicingDice/slicingdice-go/tree/master/tests_and_examples"><strong>Go</strong></a>.</p><p>In order to answer the question <em>“</em><strong><em>What is the average lead monetary value by status by salesperson in the last 48 hours?</em></strong><em>”</em> we will be making a <a href="https://docs.slicingdice.com/docs/aggregations">filtered aggregation analysis</a>.</p><p><a href="https://docs.slicingdice.com/docs/aggregations">Aggregation</a> is a powerful way to cross data in order to find insights and unexpected patterns. You can think about it like being an Excel <a href="https://en.wikipedia.org/wiki/Pivot_table">Pivot Table</a>.</p><p>What is happening under the hood on this aggregation query below is that we are asking SlicingDice to: <br>1. first filter just the sales leads that has “status” equals to “first-contact” between “now” and the “last 48 hours”.<br>2. next retrieve the all sales leads from the Top 20 most common values for the “salesperson” column;<br>2. then for the leads of each “salesperson”, make an intersection with the most common values for the “status” column values;<br>3. finally take the previous group of leads and make an average on the values of the “ticket” column of these leads.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5ecbc49d637f918e1f2ebe7ca9fb208d/href">https://medium.com/media/5ecbc49d637f918e1f2ebe7ca9fb208d/href</a></iframe><p>Based on the data we inserted before, if you run this query above on your own terminal, you should be able to see these results below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f882fe47cc2ff0cc2397d166d01b8335/href">https://medium.com/media/f882fe47cc2ff0cc2397d166d01b8335/href</a></iframe><p>As you can see, the results are basically showing the average ticket value per lead status and salesperson. You can answer a lot of questions using aggregations and more importantly, discover insights out of your data.</p><p>Now let’s answer the second question we have: <em>“</em><strong><em>How many purchases by day were originated by people who bought at least 2 times in the past 30 days and are from “New York” or “San Francisco”?</em></strong><em>”</em>. We can easily answer this question by another filtered histogram aggregation.</p><p><a href="https://docs.slicingdice.com/docs/aggregations">Histogram aggregations</a> are great to understand how a determined metric on a event column (like purchases) is distributed along a time interval.</p><p>Let’s take as example our query below, that we are asking SlicingDice to: <br>1. first filter just the customers that has “actions” column value equals to “purchase” between “now” and the “last 30 days” AND has “New York” or “San Francisco” as “city” values.<br>2. next make a count of events that happened for the “purchase” column between “now” and the “last 30 days”;<br>3. finally group the quantity of purchases per day.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0bf6d03a8ad5df914d0fd6c40badd266/href">https://medium.com/media/0bf6d03a8ad5df914d0fd6c40badd266/href</a></iframe><p>Based on the data we inserted before, if you run this query above on your own terminal, you should be able to see these results below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/adc618d955145e413f1888ebecd36763/href">https://medium.com/media/adc618d955145e413f1888ebecd36763/href</a></iframe><p>As you can see, the results are basically showing the quantity of purchases per day that were originated by customers that made at least two purchases in the past 30 days and that are from “New York” or “San Francisco”.</p><p>Now, if you want to know who these customers are, you can simply make this <a href="https://docs.slicingdice.com/docs/result-extraction">result data extraction</a> query below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/909c1c83b431bd37cd6b4e20fc3aee9b/href">https://medium.com/media/909c1c83b431bd37cd6b4e20fc3aee9b/href</a></iframe><p>As you can see below, the result is showing that the <strong>customer-01</strong> and <strong>customer-03</strong> are the ones that made more than two purchases in the past 30 days and are from “New York” or “San Francisco”.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ce55d747d40daf128b0366023a93a9eb/href">https://medium.com/media/ce55d747d40daf128b0366023a93a9eb/href</a></iframe><h3>What other questions and analysis can I make?</h3><p>SlicingDice supports <a href="https://docs.slicingdice.com/docs/how-to-make-queries">multiple types of data analysis</a>, so you can basically answer any kind of question you may need for analytics purposes, for example:</p><ul><li>What number of customers reached each sales funnel step?</li><li>What is the average revenue per customer in the past 30 days from customers that bought “product A“ and “product B” ?</li></ul><h3>You nailed it, hero! — Next steps</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*2l2udxr7w9iiH6yLfvV-_A.gif" /></figure><p><strong>That’s it.</strong> You are now ready to start making as much sales and business analysis as you want.<br>If you are inclined to think that SlicingDice might work for you, we suggest you take a look on <a href="https://docs.slicingdice.com/">our documentation</a> and at least follow our <a href="https://docs.slicingdice.com/docs/quickstart-guide">quickstart guide</a>.</p><p>Please, don’t hesitate to contact our <a href="https://www.slicingdice.com/faq-and-contact"><strong>developer support team</strong></a> <strong>at any time, for any reason</strong>. We are here to support your needs.</p><h3>Loved it… but, how much does it cost?</h3><p><a href="https://blog.slicingdice.com/slicingdice-pricing-model-and-competitors-comparison-31f1c9f0f076">Our price is really innovative and cheap</a>. We charge based on the <strong>quantity of columns</strong> you have, doesn’t matter how many rows you store for them.</p><p>So for example you can store <strong>unlimited data</strong> on SlicingDice for these two use cases presented above (customers, for example) <strong>for less $ 10.00 per month</strong>. It’s true. <a href="https://www.slicingdice.com/pricing">Check our website pricing page</a>.</p><h3>Why SlicingDice?</h3><p>Developers want to store and query their data, but they hate having to manage complex data infrastructure, so <strong>we do it for them</strong>.<br>All they have to do is simply store and query billions of <strong>real-time and historical data,</strong> <strong>without managing any infrastructure</strong>.</p><p><strong>High availability?</strong><br>You don’t need to worry. We always replicate and backup your data <strong>on three different datacenters</strong>, located in <strong>France, Canada</strong> and <strong>Germany</strong>.</p><p><strong>Query speed?</strong><br>If any query takes <strong>longer than 10 seconds to complete</strong>, no matter the query complexity or data size, you receive a <strong>10¢ discount</strong> for each query. We believe ensuring fast queries is <strong>our responsibility, not yours</strong>.</p><h3>Not sure if we can support your needs?</h3><p><a href="https://calendly.com/slicingdice/dev15min/"><strong>Click here and schedule</strong></a> a 15-minute talk with <strong>our developers</strong>, totally free of charge, so we can evaluate your case together.</p><p>Don’t know how to model your data in order to send it to SlicingDice? <br>No problem at all, <a href="https://calendly.com/slicingdice/dev15min/"><strong>schedule a time</strong></a> so we can talk or <a href="https://www.slicingdice.com/faq-and-contact"><strong>let’s chat online now</strong></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c1655bb802e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slicingdice-com-blog/sales-and-business-analytics-in-10-minutes-2c1655bb802e">Sales and Business Analytics in 10 minutes</a> was originally published in <a href="https://medium.com/slicingdice-com-blog">SlicingDice.com Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>