What to do, when your Azure Function/Azure Web App application, after some time running, starts failing outgoing connections (e.g. HttpClient requests) on SocketException, but after restart your app starts to work.
At Česko.Digital community, we helped to create a crisis information website for Czech Ministry of Health about the coronavirus outbreak in the Czech Republic. The website has since become one of the main information channels for all Czech citizens. This article describes how we modified the website with the Ministry’s IT dept. to handle expected load.
Azure CosmosDB is one of the best NoSQL databases I ever worked with. But in many use cases, this database makes your budget bleeding. This post describes this service pricing & how to optimize costs (mostly for MongoDB-styled developers).
Do you have some Application settings in appsettings.json for App Service (or Azure Function) structured in sections? And do you know how to set up same structure as Application settings in Azure?
One day I have deployed my Azure Function app into container to production server (.NET Core on Linux). And app started to fail after few minutes, without any reason, with exit code 137. This post describes how I debugged the problem – to my suprise, it was caused by .NET Garbage Collector.
