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.
One of the questions you may have is “Why do you say it is important when there is Azure Container Service?” The answer to that is very simple and very straightforward: Take the power of App Service on Windows with all of its services (scalability, custom domains, continuous integration, …) and leverage its power with your custom environment thanks to Docker.
So while the benefits of using Single Sign On are obvious and there many articles about it, it way less discussed topic is Single Sign Out – the process of signing out the user from all web application which use the same IdP.
The initial problem with App Service is its slow filesystem (which I have blogged about already more than once). Up until this discovery you had two options – either have all the files delivered through the slow replicated filesystem or enable Local Cache which results in the files written locally no longer being persistent which is a major issue with most PHP applications (even for full WordPress functionality – installing plugins, updates, etc.). Now, there is a third option ...
What isn’t as simple is what goes into running Netflix, a service that streams around 250 million hours of video per day to around 98 million paying subscribers in 190 countries. At this scale, providing quality entertainment in a matter of a few seconds to every user is no joke. And as much as it means building top-notch infrastructure at a scale no other Internet service has done before, it also means that a lot of participants in the experience have to be negotiated with and kept satisfied.
Force.com is the preeminent cloud application development platform in use today, supporting more than 100,000 organizations and 220,000 deployed apps. Individual enterprises and commercial Software as a Service (SaaS) vendors trust the platform to deliver robust, reliable, and Internet-scale applications. To meet the high demands of its large user population, Force.com’s foundation is a metadata-driven software architecture that enables multitenant applications. This paper explains the technolog
At Zendesk, our goal is to help bring companies and their customers closer together with software that’s easy to use, easy to customize, and easy to scale. It starts with ensuring Zendesk Support runs smoothly while providing you with a service that scales to meet your ever-changing needs.
Get a behind-the-scenes look from our engineering team about how our cloud architecture is set up, how requests are processed in Jira or Confluence, and how we handle performance and availability.
After using a bunch of methods to scale like R/W split, MySQL partitioning and witnessing them being inadequate for our rapid growth, we came to the conclusion that scaling vertically can only get you so far. The more we thought about it, the more it made sense for us to shard our database.