From bc0c982039c9d8a93d26e4aa13ffccf0faf41416 Mon Sep 17 00:00:00 2001 From: selman koc <64414348+skoc10@users.noreply.github.com> Date: Sat, 18 Mar 2023 13:34:00 +0300 Subject: [PATCH 1/4] added migration mssql to postgresql --- .../2023-03-16-Migration-Abp.io-Azure/POST.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/en/Community-Articles/2023-03-16-Migration-Abp.io-Azure/POST.md b/docs/en/Community-Articles/2023-03-16-Migration-Abp.io-Azure/POST.md index e556dd6fb4..54e0945f5d 100644 --- a/docs/en/Community-Articles/2023-03-16-Migration-Abp.io-Azure/POST.md +++ b/docs/en/Community-Articles/2023-03-16-Migration-Abp.io-Azure/POST.md @@ -14,6 +14,12 @@ There were several reasons why the decision was taken to migrate from the old on The decision to move to the cloud was made to eliminate the disadvantages of the old platform. The migration to Azure meant that the resources would be independent of each other but faster in terms of communicating with each other. The platform would also take advantage of cloud security and availability. The managed Kubernetes service that Azure offers comes with autoscaling and loadbalancing, which makes the platform more reliable. Finally, the migration to Azure would provide a better quality service to global customers and the community. +### Before Moving to Azure + +Before migrating to Azure, we decided to switch our database from MSSQL to PostgreSQL on-premise first. This gave us the opportunity to test and fine-tune the migration process before making the final switch to Azure.You can check the details of database migration from this article [Migrating from MS-SQL to Postgresql](https://github.com/abpframework/abp/blob/dev/docs/en/Community-Articles/2023-03-15-Migration-Mssql-Postgresql/POST.md). + +Before moving to Azure, the platform was tested in the staging environment. The staging environment was created on Azure to test the migration process. The staging environment was created with the same resources as the production environment. The staging environment was used to test the migration process and to optimize the migration process. The staging environment was also used to test the migration of the data from the old platform to Azure. The migration of the data from the old platform to Azure was tested several times to ensure that the migration process was successful. + ### Creating and Configuring the abp.io Platform on Azure Several steps were taken to create and configure the abp.io platform on Azure. [Terraform](https://www.terraform.io/) was used to create the infrastructure (VM, Private Network, AKS, Postgresql Flexible Server...), while [Ansible](https://www.ansible.com/) was used to configure the Azure resources like Terraform, Helm, Kubectl, Docker, VPN, Redis, Prometheus, Grafana, ElasticSearch, Kibana and so on.... Azure DevOps pipelines and release were used for AKS deployment. The most time-consuming part in this process was to prepare, test and optimize the terraform and ansible settings files. From 7590bb5f99a3f5ce7f60a2763394535d15ebbd6b Mon Sep 17 00:00:00 2001 From: selman koc <64414348+skoc10@users.noreply.github.com> Date: Mon, 20 Mar 2023 10:21:41 +0300 Subject: [PATCH 2/4] Update POST.md --- .../2023-03-16-Migration-Abp.io-Azure/POST.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/Community-Articles/2023-03-16-Migration-Abp.io-Azure/POST.md b/docs/en/Community-Articles/2023-03-16-Migration-Abp.io-Azure/POST.md index 54e0945f5d..26a1cce1fe 100644 --- a/docs/en/Community-Articles/2023-03-16-Migration-Abp.io-Azure/POST.md +++ b/docs/en/Community-Articles/2023-03-16-Migration-Abp.io-Azure/POST.md @@ -16,7 +16,7 @@ The decision to move to the cloud was made to eliminate the disadvantages of the ### Before Moving to Azure -Before migrating to Azure, we decided to switch our database from MSSQL to PostgreSQL on-premise first. This gave us the opportunity to test and fine-tune the migration process before making the final switch to Azure.You can check the details of database migration from this article [Migrating from MS-SQL to Postgresql](https://github.com/abpframework/abp/blob/dev/docs/en/Community-Articles/2023-03-15-Migration-Mssql-Postgresql/POST.md). +Before migrating to Azure, we decided to switch our database from MSSQL to PostgreSQL on-premise first. This gave us the opportunity to test and fine-tune the migration process before making the final switch to Azure.You can check the details of database migration from this article [Migrating from MS-SQL to Postgresql](https://community.abp.io/posts/migrating-from-mssql-to-postgresql-lbi5anlv). Before moving to Azure, the platform was tested in the staging environment. The staging environment was created on Azure to test the migration process. The staging environment was created with the same resources as the production environment. The staging environment was used to test the migration process and to optimize the migration process. The staging environment was also used to test the migration of the data from the old platform to Azure. The migration of the data from the old platform to Azure was tested several times to ensure that the migration process was successful. From 3bc143287ca23188b6a358a4ae66b0c4019c67fc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alper=20Ebi=C3=A7o=C4=9Flu?= <9526587+ebicoglu@users.noreply.github.com> Date: Mon, 20 Mar 2023 10:29:17 +0300 Subject: [PATCH 3/4] Update POST.md --- .../2023-03-16-Migration-Abp.io-Azure/POST.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/Community-Articles/2023-03-16-Migration-Abp.io-Azure/POST.md b/docs/en/Community-Articles/2023-03-16-Migration-Abp.io-Azure/POST.md index 26a1cce1fe..212dd6fc0c 100644 --- a/docs/en/Community-Articles/2023-03-16-Migration-Abp.io-Azure/POST.md +++ b/docs/en/Community-Articles/2023-03-16-Migration-Abp.io-Azure/POST.md @@ -16,7 +16,7 @@ The decision to move to the cloud was made to eliminate the disadvantages of the ### Before Moving to Azure -Before migrating to Azure, we decided to switch our database from MSSQL to PostgreSQL on-premise first. This gave us the opportunity to test and fine-tune the migration process before making the final switch to Azure.You can check the details of database migration from this article [Migrating from MS-SQL to Postgresql](https://community.abp.io/posts/migrating-from-mssql-to-postgresql-lbi5anlv). +Before migrating to Azure, we decided to switch our database from MS-SQL to PostgreSQL on-premise first. This gave us the opportunity to test and fine-tune the migration process before making the final switch to Azure.You can check the details of database migration from this article [Migrating from MS-SQL to Postgresql](https://community.abp.io/posts/migrating-from-mssql-to-postgresql-lbi5anlv). Before moving to Azure, the platform was tested in the staging environment. The staging environment was created on Azure to test the migration process. The staging environment was created with the same resources as the production environment. The staging environment was used to test the migration process and to optimize the migration process. The staging environment was also used to test the migration of the data from the old platform to Azure. The migration of the data from the old platform to Azure was tested several times to ensure that the migration process was successful. From e12a9cc2a8aa723b2a6fa84c4a311604098af213 Mon Sep 17 00:00:00 2001 From: selman koc <64414348+skoc10@users.noreply.github.com> Date: Mon, 20 Mar 2023 10:37:58 +0300 Subject: [PATCH 4/4] Update POST.md --- .../2023-03-16-Migration-Abp.io-Azure/POST.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/Community-Articles/2023-03-16-Migration-Abp.io-Azure/POST.md b/docs/en/Community-Articles/2023-03-16-Migration-Abp.io-Azure/POST.md index 212dd6fc0c..49473d3207 100644 --- a/docs/en/Community-Articles/2023-03-16-Migration-Abp.io-Azure/POST.md +++ b/docs/en/Community-Articles/2023-03-16-Migration-Abp.io-Azure/POST.md @@ -18,7 +18,7 @@ The decision to move to the cloud was made to eliminate the disadvantages of the Before migrating to Azure, we decided to switch our database from MS-SQL to PostgreSQL on-premise first. This gave us the opportunity to test and fine-tune the migration process before making the final switch to Azure.You can check the details of database migration from this article [Migrating from MS-SQL to Postgresql](https://community.abp.io/posts/migrating-from-mssql-to-postgresql-lbi5anlv). -Before moving to Azure, the platform was tested in the staging environment. The staging environment was created on Azure to test the migration process. The staging environment was created with the same resources as the production environment. The staging environment was used to test the migration process and to optimize the migration process. The staging environment was also used to test the migration of the data from the old platform to Azure. The migration of the data from the old platform to Azure was tested several times to ensure that the migration process was successful. +The platform was tested in a staging environment created on Azure with the same resources as the production environment. The staging environment was used to test and optimize the migration process, including the migration of data from the old platform to Azure, which was tested multiple times to ensure success. ### Creating and Configuring the abp.io Platform on Azure