Do I need to design the application architecture while supporting Azure?

I am currently designing architecture for my new project. This is the ASP.Net MVC web client and WCF web services for third-party integration as front-end.

Currently, this application will be placed by us on a rented rack in the data center, but in the future we can transfer it to Microsoft Azure.

Do I need to do some planning for Azure in my architecture? Or my current architecture with IIS, MSMQ, SQL Server, Velocity, etc. Will it work in Azure without any problems? I was inattentive to Azure due to lack of available time, but I need to make sure that I get the rights to the architecture for future needs.

What do i need to keep track of?

Thanks and respect,

Ajay

+3
source share
3 answers

It depends on how seriously you plan to move to Lazur and how soon. If so, then I would say yes.

Unfortunately, the idea of ​​being able to write, to ever run anywhere, is a bit of a pipe dream. The concept of abstracting everything away just doesn't work if the platform limits the choice of your architecture - and almost every platform. Even if you can choose data storage technology, for example, you will almost certainly encounter the problem of impedance mismatch at some point that will affect your design.

So, in the case of Azure, there are a few issues you need to think about.

-, MSMQ Velocity. Azure , ( , ..), , MSMQ, , . , , ( , Velocity).

-, Azure Table Storage SQL Azure Database , . , , , . - SQL, , SQL Server, , ( ), .. , SQL Server , , , - . , Azure Table Storage - , , , , , REST-HTTP. BASE, ACID.

-, - . , , , Azure Blob , .

-, : -, IIS ( , IIS) , Windows. , - /. .

, , Azure - , , , , . Azure, , , , .

[: , Azure. , , - , , - Azure.NET Service Bus, ]

+10

, .

Azure , . , , .

, , , .

+2

Azure, , , . , , .

+1

Source: https://habr.com/ru/post/1715235/


All Articles