<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="22533" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://archives.christuniversity.in/items/show/22533?output=omeka-xml" accessDate="2026-06-18T16:18:44+00:00">
  <collection collectionId="7">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3139">
                <text>Faculty Publications</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="19">
    <name>Article</name>
    <description>Faculty Publications -Articles</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="210625">
              <text>Komarasamy, Dinesh; Rajavel, Rajkumar; Harimoorthy, Karthikeyan; Pitchai, Aravind</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="210626">
              <text>A scalable scheduling and resource management framework for cloud-native B2B applications</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="210627">
              <text>01-01-2025</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="210628">
              <text>Scientific Reports;Volume;15;Issue;1;Article No.;44500;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="210629">
              <text>&lt;a href="https://doi.org/10.1038/s41598-025-28149-5" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1038/s41598-025-28149-5&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/pages/publications/105025748225?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105025748225?origin=resultslist&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="38">
          <name>Coverage</name>
          <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
          <elementTextContainer>
            <elementText elementTextId="210630">
              <text>Komarasamy D., Department of Computer Science and Engineering, Kongu Engineering College, Perundurai, India; Rajavel R., Department of AI, ML &amp;amp; Data Science, Christ University, Bangalore, India; Harimoorthy K., Department of Computer Science and Engineering, Christ University, Bangalore, India; Pitchai A., Department of Electrical and Computer Engineering, Mattu University, Mattu, Ethiopia</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="210631">
              <text>In modern cloud computing environments, customers increasingly depend on on-demand resource provisioning to handle dynamic workloads. However, fluctuations in job arrival rates can result in prolonged queue times, which negatively affect overall system performance. Although existing scheduling algorithms provide efficient job management, they often fail to account for the combined impact of queue delays and the need for flexible resource provisioningparticularly in business-critical applications. In order to tackle these issues, the paper proposes a new Optimized Job Scheduling and Resource Scaling (OJSRS) algorithm designed to improve job execution efficiency and support elastic resource management in cloud environments. The OJSRS algorithm integrates two key components: Tree-based Job Scheduling (TJS) and Automated Resource Scaling and Scheduling (ARSS). The TJS component constructs a hierarchical structure that concurrently maps incoming jobs to the most suitable Virtual Machines (VMs), thereby minimizing queue delays. Meanwhile, ARSS adjusts resource allocation dynamically, increasing or decreasing capacity according to workload requirements and cloud service provider policies, enabling responsive and adaptive provisioning. Experimental results show that the OJSRS algorithm increases resource utilization by approximately 510% and accelerates job completion through proactive resource scaling. This approach provides a significant performance advantage for cloud-native business applications that require both efficiency and scalability.  The Author(s) 2025.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="210632">
              <text>Automated resource scaling; Business-to-Business applications; Cloud computing; Cloud native platform; Decent work and economic growth; Job scheduling; Load balancing</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="210633">
              <text>Nature Research</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="210634">
              <text>ISSN: 20452322;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="210635">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="210636">
              <text>Article</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="210637">
              <text>All Open Access; Gold Open Access; Green Open Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="42">
          <name>Format</name>
          <description>The file format, physical medium, or dimensions of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="210638">
              <text>online</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
