<?xml version="1.0" encoding="UTF-8"?>
<article article-type="Research Article">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher">journal-of-information-and-optimization-sciences</journal-id>
      <journal-title-group>
        <journal-title>Journal of Information and Optimization Sciences</journal-title>
      </journal-title-group>
      <issn publication-format="electronic">2169-0103</issn>
      <issn publication-format="print">0252-2667</issn>
      <publisher>
        <publisher-name>Taru Publications</publisher-name>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.47974/JIOS-2274</article-id>
      <title-group>
        <article-title>Developing a dynamic data partitioning model for multi-tenant database environments in cloud platforms</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <name>
            <surname>Datar</surname>
            <given-names>Dinesh Shravan</given-names>
          </name>
          <aff>Department of Artificial Intelligence &amp; Data Science, Vishwakarma Institute of Technology, Pune, Maharashtra, 411037, India</aff>
        </contrib>
        <contrib contrib-type="author" corresp="yes">
          <name>
            <surname>Gaurav</surname>
            <given-names>Amit</given-names>
          </name>
          <aff>School of Engineering &amp; Technology, Noida International University, Greater Noida, Uttar Pradesh, 203201, India</aff>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Arivukkodi</surname>
            <given-names>R.</given-names>
          </name>
          <aff>Department of Computer Science, Meenakshi College of Arts and Science, Meenakshi Academy of Higher Education and Research, Chennai, Tamil Nadu, 600078, India</aff>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Borkar</surname>
            <given-names>Pradnya</given-names>
          </name>
          <aff>Department of Computer Science and Engineering, Nagpur Campus, Symbiosis International (Deemed University), Symbiosis Institute of Technology, Nagpur, Maharashtra, 440008, India</aff>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Shirkande</surname>
            <given-names>Aparna Shrinivas</given-names>
          </name>
          <aff>Department of Electronics and Telecommunication Engineering, S. B. Patil College of Engineering Indapur, Affiliated to Savitribai Phule Pune University (SPPU) Pune, Pune, Maharashtra, 413106, India</aff>
        </contrib>
      </contrib-group>
      <volume>47</volume>
      <issue>5-A</issue>
      <fpage>1825</fpage>
      <lpage>1832</lpage>
      <pub-date date-type="pub">
        <day>23</day>
        <month>04</month>
        <year>2026</year>
      </pub-date>
      <abstract>
        <p>The growing adoption of cloud computing and Software-as-a-Service (SaaS) platforms has intensified the demand for scalable and performance-isolated multi-tenant database (MTDB) architectures. Traditional partitioning schemes, including hash, range, and hybrid methods, remain static and fail to address the challenges of heterogeneous workloads, workload skew, and elastic scalability. This paper proposes DynaPartMT, a dynamic, workload-aware data partitioning model for MTDBs in cloud platforms. The framework integrates continuous workload monitoring, lightweight forecasting, and a multi-objective cost-aware partitioning planner that jointly minimizes cross-partition transactions, balances load, enforces tenant-level isolation, and bounds migration overhead. The model is mathematically formalized, with optimization objectives and constraints explicitly defined to guarantee scalability and SLA compliance.</p>
      </abstract>
      <kwd-group>
        <kwd>Multi-tenant databases (MTDBs)</kwd>
        <kwd>Dynamic data partitioning</kwd>
        <kwd>Cloud platforms</kwd>
        <kwd>Tenant isolation</kwd>
        <kwd>Workload forecasting</kwd>
      </kwd-group>
      <custom-meta-group>
        <custom-meta>
          <meta-name>access</meta-name>
          <meta-value>open</meta-value>
        </custom-meta>
        <custom-meta>
          <meta-name>retracted</meta-name>
          <meta-value>no</meta-value>
        </custom-meta>
      </custom-meta-group>
    </article-meta>
  </front>
</article>
