<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>(Lightning) Towards a Practical HTAP Engine for Polystores</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Scalar</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Inc. Tokyo</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Japan</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Hiroyuki Yamada</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Akihiro Okuno</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Toshihiro Suzuki</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jun Nemoto</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Workshop Proceedings</string-name>
        </contrib>
      </contrib-group>
      <abstract>
        <p>In this Lightning talk, we introduce a ScalarDB approach for achieving HTAP in polystores. Polystores have gained much interest in the database community because of an increasing need for combining a variety of special-purpose databases, modernizing system architecture (e.g., employing a microservice architecture [1, 2]), and dealing with siloed databases in enterprises As one of the approaches to realizing polystores from a transactional perspective, we have been developing and providing a product called ScalarDB [5]. ScalarDB achieves distributed transactions across multiple disparate databases. Specifically, ScalarDB provides a databaseagnostic transaction manager on top of its database abstraction; thus, it achieves transactions spanning multiple disparate databases without depending on the transactional capability of underlying databases. Although ScalarDB was started as a universal transaction manager, it has evolved as a universal HTAP engine, running complex analytical workloads on the databases with which ScalarDB interacts while providing transactional capability.</p>
      </abstract>
      <kwd-group>
        <kwd>polystores</kwd>
        <kwd>federated database systems</kwd>
        <kwd>HTAP</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>1. Introduction
abstraction mechanisms to seamlessly integrate such distributed query engines with
ScalarDBmanaged databases.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>J.</given-names>
            <surname>Lewis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Fowler</surname>
          </string-name>
          , Microservices, https://martinfowler.com/articles/microservices.html,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>R.</given-names>
            <surname>Laigner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Zhou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Salles</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Liu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Kalinowski</surname>
          </string-name>
          ,
          <article-title>Data Management in Microservices: State of the Practice, Challenges</article-title>
          , and Research Directions, PVLDB
          <volume>14</volume>
          (
          <year>2021</year>
          )
          <fpage>3348</fpage>
          -
          <lpage>3361</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>B.</given-names>
            <surname>Hagler</surname>
          </string-name>
          , Overcoming Data Silos In Your Organization, https://www.forbes.com/sites/ forbestechcouncil/2020/05/12/overcoming
          <article-title>-data-silos-in-your-</article-title>
          <string-name>
            <surname>organization</surname>
          </string-name>
          ,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>P.</given-names>
            <surname>Strong</surname>
          </string-name>
          , Enterprise Grid Computing:
          <article-title>Grid Computing Holds Great Promise for the Enterprise Data Center, but Many Technical and Operational Hurdles Remain</article-title>
          .,
          <source>Queue</source>
          <volume>3</volume>
          (
          <year>2005</year>
          )
          <fpage>50</fpage>
          -
          <lpage>59</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>H.</given-names>
            <surname>Yamada</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Suzuki</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Ito</surname>
          </string-name>
          , J. Nemoto, ScalarDB: Universal Transaction Manager for Polystores, PVLDB
          <volume>16</volume>
          (
          <year>2023</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>The</given-names>
            <surname>Apache Software Foundation</surname>
          </string-name>
          , Apache Spark, https://spark.apache.org/,
          <year>2023</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>The</given-names>
            <surname>Trino Software Foundation</surname>
          </string-name>
          , Trino, https://trino.io/,
          <year>2023</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>