search

The way storage is designed for Azure App Service is very interesting. Unlike with Heroku (or other similar providers), App Service offers a shared, persistent storage for your application. This generally means, that when one instance in a farm makes a write to the file system (D:\home) it will be available for all the other instances in the farm and it is going to persist even if the farm restarts or recycles.

Bharat Dwarkani shared on Nov 10, 2019
image
hajekj.net
bookmarks
share
favorite_border0 visibility6
favorite_border0 visibility6 share bookmarks

When building several big cloud applications we found a lack of great solutions (that's not to say there aren't solutions out there) for many key pieces to building scalable distributed applications while keeping the development experience simple. Here are a few examples of why we built and use Foundatio:

Bharat Dwarkani shared on Oct 26, 2019
image
github.com
bookmarks
share
favorite_border0 visibility7
favorite_border0 visibility7 share bookmarks

ASP.NET Core supports several different caches. The simplest cache is based on the IMemoryCache, which represents a cache stored in the memory of the web server.

Bharat Dwarkani shared on Sep 09, 2019
image
docs.microsoft.com
bookmarks
share
favorite_border0 visibility2
favorite_border0 visibility2 share bookmarks

There are many types of caching - In-Memory, Distributed, Response caching. Check out how to do that in ASP.NET Core

Bharat Dwarkani shared on Aug 22, 2019
image
docs.microsoft.com
bookmarks
share
favorite_border0 visibility4
favorite_border0 visibility4 share bookmarks
add