What ORM developers use to connect to Azure?

I’m interested in knowing what methods developers use to connect to a Windows Azure instance running in the cloud?

From what I understand, it is very similar to SQL Server with two main differences, which are multiple active recordsets, are not supported, and unoccupied / long connections are automatically completed in azure. To do this, microsoft offers to include retry logic in your application to detect a closed connection, and then try to complete the interrupted action. Does anyone have an example of the code they are currently using on this?

To create a data layer, I looked at various ORMs. Since I need to access the azure from the azure window (i.e. separate fields), it seems to me that any ORM carpper should support asynchronous methods so as not to block any windows from the azure instances. Any suggestions as to which ORM mapper to use, or comments on what you are currently using

+3
source share
5 answers

I have successfully used NHibernate with Azure, and we are in the process of building a commercial application on top of NHibernate. The only problem I encountered was in connection pools when running locally and connecting to SQL Azure in the cloud - this was fixed when disconnecting the connection pool.

ORM... SQL Azure ( ), . - , ..

!

+2

Azure:

"Telerik Open Access, ORM, SQL Windows Azure cloud. "

Azure User Group LLBLGen Entity Framework.

+1

Entity Framework - , .

, . , EF. , , , , , .

EF , . ... , Azure, , , , ( )

+1
0

NHibernate - Azure (, ), Lokad.Translate .

0

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


All Articles