<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>ACM Queue - Databases</title>
    <link>http://queue.acm.org/listing.cfm?item_topic=Databases&amp;qc_type=topics_list&amp;filter=Databases&amp;page_title=Databases&amp;order=desc</link>
    <description />
    <item>
      <title>The Way We Think About Data</title>
      <link>http://queue.acm.org/detail.cfm?id=3384393</link>
      <description>The two papers I've chosen for this issue of acmqueue both challenge the way we think about and use data, though in very different ways. In "Stop Explaining Black-box Machine-learning Models for High-stakes Decisions and Use Interpretable Models Instead," Cynthia Rudin makes the case for models that can be inspected and interpreted by human experts. The second paper, "Local-first Software: You Own Your Data, in Spite of the Cloud," describes how to retain sovereignty over your data.</description>
      <category>Databases</category>
      <pubDate>Tue, 18 Feb 2020 12:20:53 GMT</pubDate>
      <author>Adrian Colyer</author>
      <guid isPermaLink="false">3384393</guid>
    </item>
    <item>
      <title>Numbers Are for Computers, Strings Are for Humans</title>
      <link>http://queue.acm.org/detail.cfm?id=3379349</link>
      <description>Unless what you are processing, storing, or transmitting are, quite literally, strings that come from and are meant to be shown to humans, you should avoid processing, storing, or transmitting that data as strings. Remember, numbers are for computers, strings are for humans. Let the computer do the work of presenting your data to the humans in a form they might find palatable. That's where those extra bytes and instructions should be spent, not doing the inverse.</description>
      <category>Databases</category>
      <pubDate>Mon, 13 Jan 2020 14:22:40 GMT</pubDate>
      <author>George V. Neville-Neil</author>
      <guid isPermaLink="false">3379349</guid>
    </item>
    <item>
      <title>Space Time Discontinuum</title>
      <link>http://queue.acm.org/detail.cfm?id=3372732</link>
      <description>Back when you had only one database for an application to worry about, you didn't have to think about partial results. You also didn't have to think about data arriving after some other data. It was all simply there. Now, you can do so much more with big distributed systems, but you have to be more sophisticated in the tradeoff between timely answers and complete answers.</description>
      <category>Databases</category>
      <pubDate>Mon, 18 Nov 2019 16:04:09 GMT</pubDate>
      <author>Pat Helland</author>
      <guid isPermaLink="false">3372732</guid>
    </item>
    <item>
      <title>Back under a SQL Umbrella</title>
      <link>http://queue.acm.org/detail.cfm?id=3371598</link>
      <description>Procella is the latest in a long line of data processing systems at Google. What's unique about it is that it's a single store handling reporting, embedded statistics, time series, and ad-hoc analysis workloads under one roof. It's SQL on top, cloud-native underneath, and it's serving billions of queries per day over tens of petabytes of data. There's one big data use case that Procella isn't handling today though, and that's machine learning. But in 'Declarative recursive computation on an RDBMS... or, why you should use a database for distributed machine learning,' Jankov et al. make the case for the database being the ideal place to handle the most demanding of distributed machine learning workloads.</description>
      <category>Databases</category>
      <pubDate>Wed, 06 Nov 2019 14:02:48 GMT</pubDate>
      <author>Adrian Colyer</author>
      <guid isPermaLink="false">3371598</guid>
    </item>
    <item>
      <title>Write Amplification Versus Read Perspiration</title>
      <link>http://queue.acm.org/detail.cfm?id=3364509</link>
      <description>In computing, there's an interesting trend where writing creates a need to do more work. You need to reorganize, merge, reindex, and more to make the stuff you wrote more useful. If you don't, you must search or do other work to support future reads.</description>
      <category>Databases</category>
      <pubDate>Mon, 23 Sep 2019 15:58:19 GMT</pubDate>
      <author>Pat Helland</author>
      <guid isPermaLink="false">3364509</guid>
    </item>
    <item>
      <title>DAML: The Contract Language of Distributed Ledgers</title>
      <link>http://queue.acm.org/detail.cfm?id=3357728</link>
      <description>"We'll see the same kind of Cambrian explosion we witnessed in the web world once we started using mutualized infrastructure in public clouds and frameworks. It took only three weeks to learn enough Ruby on Rails and Heroku to push out the first version of a management system for that brokerage. And that's because I had to think only about the models, the views, and the controllers. The hardest part, of course, had to do with building a secure wallet."</description>
      <category>Databases</category>
      <pubDate>Mon, 19 Aug 2019 13:25:37 GMT</pubDate>
      <author>Shaul Kfir, Camille Fournier</author>
      <guid isPermaLink="false">3357728</guid>
    </item>
    <item>
      <title>Extract, Shoehorn, and Load</title>
      <link>http://queue.acm.org/detail.cfm?id=3339880</link>
      <description>It turns out that the business value of ill-fitting data is extremely high. The process of taking the input data, discarding what doesn't fit, adding default or null values for missing stuff, and generally shoehorning it to the prescribed shape is important. The prescribed shape is usually one that is amenable to analysis for deeper meaning.</description>
      <category>Databases</category>
      <pubDate>Wed, 05 Jun 2019 15:42:56 GMT</pubDate>
      <author>Pat Helland</author>
      <guid isPermaLink="false">3339880</guid>
    </item>
    <item>
      <title>Identity by Any Other Name</title>
      <link>http://queue.acm.org/detail.cfm?id=3314115</link>
      <description>New emerging systems and protocols both tighten and loosen our notions of identity, and that's good! They make it easier to get stuff done. REST, IoT, big data, and machine learning all revolve around notions of identity that are deliberately kept flexible and sometimes ambiguous. Notions of identity underlie our basic mechanisms of distributed systems, including interchangeability, idempotence, and immutability.</description>
      <category>Databases</category>
      <pubDate>Tue, 19 Feb 2019 17:53:33 GMT</pubDate>
      <author>Pat Helland</author>
      <guid isPermaLink="false">3314115</guid>
    </item>
    <item>
      <title>Edge Computing</title>
      <link>http://queue.acm.org/detail.cfm?id=3313377</link>
      <description>Creating edge computing infrastructures and applications encompasses quite a breadth of systems research. Let's take a look at the academic view of edge computing and a sample of existing research that will be relevant in the coming years.</description>
      <category>Databases</category>
      <pubDate>Tue, 12 Feb 2019 14:11:15 GMT</pubDate>
      <author>Nitesh Mor</author>
      <guid isPermaLink="false">3313377</guid>
    </item>
    <item>
      <title>Achieving Digital Permanence</title>
      <link>http://queue.acm.org/detail.cfm?id=3311889</link>
      <description>Today's Information Age is creating new uses for and new ways to steward the data that the world depends on. The world is moving away from familiar, physical artifacts to new means of representation that are closer to information in its essence. We need processes to ensure both the integrity and accessibility of knowledge in order to guarantee that history will be known and true.</description>
      <category>Databases</category>
      <pubDate>Wed, 06 Feb 2019 11:31:00 GMT</pubDate>
      <author>Raymond Blum, Betsy Beyer</author>
      <guid isPermaLink="false">3311889</guid>
    </item>
  </channel>
</rss>

