<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:a10="http://www.w3.org/2005/Atom" version="2.0">
  <channel xmlns:media="http://search.yahoo.com/mrss/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <title>ABP.IO Stories</title>
    <link>https://abp.io/community/articles</link>
    <description>A hub for ABP Framework, .NET, and software development. Access articles, tutorials, news, and contribute to the ABP community.</description>
    <lastBuildDate>Fri, 02 Oct 2026 18:10:03 Z</lastBuildDate>
    <generator>Community - ABP.IO</generator>
    <image>
      <url>https://abp.io/assets/favicon.ico/favicon-32x32.png</url>
      <title>ABP.IO Stories</title>
      <link>https://abp.io/community/articles</link>
    </image>
    <a10:link rel="self" type="application/rss+xml" title="self" href="https://abp.io/community/rss?member=HeadChannel" />
    <item>
      <guid isPermaLink="true">https://abp.io/community/posts/multitenancy-support-in-angular-apps-with-abp.io-lw9l36c5</guid>
      <link>https://abp.io/community/posts/multitenancy-support-in-angular-apps-with-abp.io-lw9l36c5</link>
      <a10:author>
        <a10:name>HeadChannel</a10:name>
        <a10:uri>https://abp.io/community/members/HeadChannel</a10:uri>
      </a10:author>
      <title>Multi-Tenancy Support in Angular Apps with ABP.IO</title>
      <description>In today's rapidly evolving digital landscape, implementing multi-tenant architecture has become essential for web applications to ensure scalability, efficiency, and cost-effectiveness. One of the simplest and most effective methods is tenant identification using subdomains. In this post, we explore how to implement multi-tenancy in Angular applications using the ABP.IO framework and the URL structure: https://{tenant}.mydomain.com/.</description>
      <pubDate>Mon, 21 Oct 2024 12:53:05 Z</pubDate>
      <a10:updated>2026-03-27T10:13:19Z</a10:updated>
      <content:encoded><![CDATA[In today's rapidly evolving digital landscape, implementing multi-tenant architecture has become essential for web applications to ensure scalability, efficiency, and cost-effectiveness. One of the simplest and most effective methods is tenant identification using subdomains. In this post, we explore how to implement multi-tenancy in Angular applications using the ABP.IO framework and the URL structure: https://{tenant}.mydomain.com/.<br \><a href="https://headchannel.co.uk/blog/multi-tenancy-support-in-angular-apps-with-ABP-IO/?utm_source=abp&utm_medium=blog" rel="nofollow noopener noreferrer" title="Go to the Post">Go to the Post</a>]]></content:encoded>
      <media:thumbnail url="https://abp.io/api/posts/cover-picture-source/3a15c150-3c53-98d1-6533-1468e00b7aaf" />
      <media:content url="https://abp.io/api/posts/cover-picture-source/3a15c150-3c53-98d1-6533-1468e00b7aaf" medium="image" />
    </item>
    <item>
      <guid isPermaLink="true">https://abp.io/community/posts/managing-baseline-creation-in-applications-based-on-abp-framework-yiacte5c</guid>
      <link>https://abp.io/community/posts/managing-baseline-creation-in-applications-based-on-abp-framework-yiacte5c</link>
      <a10:author>
        <a10:name>HeadChannel</a10:name>
        <a10:uri>https://abp.io/community/members/HeadChannel</a10:uri>
      </a10:author>
      <category>abp</category>
      <title>Managing Baseline Creation in Applications Based on ABP Framework</title>
      <description>Explore a module developed to manage baselines creation, entity versioning, ensuring accurate and comprehensive change tracking. The article discusses how to develop baselining and entity versioning features with ABP framework, which offers a powerful solution for creating baselines and reporting changes, enhancing data integrity and application reliability. This ensures smoother updates, accurate audits, and a better overall user experience.</description>
      <pubDate>Fri, 19 Jul 2024 08:47:44 Z</pubDate>
      <a10:updated>2026-04-27T10:25:47Z</a10:updated>
      <content:encoded><![CDATA[Explore a module developed to manage baselines creation, entity versioning, ensuring accurate and comprehensive change tracking. The article discusses how to develop baselining and entity versioning features with ABP framework, which offers a powerful solution for creating baselines and reporting changes, enhancing data integrity and application reliability. This ensures smoother updates, accurate audits, and a better overall user experience.<br \><a href="https://headchannel.co.uk//blog/managing-baseline-creation-in-applications-based-on-ABP-IO-framework/" rel="nofollow noopener noreferrer" title="Go to the Post">Go to the Post</a>]]></content:encoded>
      <media:thumbnail url="https://abp.io/api/posts/cover-picture-source/3a13dc59-d6ad-b4b6-9b42-9811e419a735" />
      <media:content url="https://abp.io/api/posts/cover-picture-source/3a13dc59-d6ad-b4b6-9b42-9811e419a735" medium="image" />
    </item>
    <item>
      <guid isPermaLink="true">https://abp.io/community/posts/how-to-test-the-system-using-postgresql-and-testcontainers-8yh8t0j8</guid>
      <link>https://abp.io/community/posts/how-to-test-the-system-using-postgresql-and-testcontainers-8yh8t0j8</link>
      <a10:author>
        <a10:name>HeadChannel</a10:name>
        <a10:uri>https://abp.io/community/members/HeadChannel</a10:uri>
      </a10:author>
      <category>postgresql</category>
      <category>test-containers</category>
      <title>How to Test The System Using PostgreSQL and TestContainers</title>
      <description>In one of our recent projects, we opted to use PostgreSQL due to its robust JSON support and cost-effectiveness, particularly when hosted on Azure. However, we soon encountered challenges with writing integration tests because PostgreSQL cannot run in-process and in-memory. Unlike SQLite, PostgreSQL requires multiple processes for each connection, as it’s based on a multiprocessing architecture.</description>
      <pubDate>Fri, 19 Jul 2024 08:45:53 Z</pubDate>
      <a10:updated>2026-04-08T20:07:38Z</a10:updated>
      <content:encoded><![CDATA[In one of our recent projects, we opted to use PostgreSQL due to its robust JSON support and cost-effectiveness, particularly when hosted on Azure. However, we soon encountered challenges with writing integration tests because PostgreSQL cannot run in-process and in-memory. Unlike SQLite, PostgreSQL requires multiple processes for each connection, as it’s based on a multiprocessing architecture.<br \><a href="https://headchannel.co.uk//blog/how-to-test-the-system-using-postgreSQL-and-testcontainers/" rel="nofollow noopener noreferrer" title="Go to the Post">Go to the Post</a>]]></content:encoded>
      <media:thumbnail url="https://abp.io/api/posts/cover-picture-source/3a13dc58-22f9-3ce1-cf44-278e220e5c6e" />
      <media:content url="https://abp.io/api/posts/cover-picture-source/3a13dc58-22f9-3ce1-cf44-278e220e5c6e" medium="image" />
    </item>
  </channel>
</rss>