<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Scaling on Alok Regmi</title>
		<link>https://alokregmi.com/tags/scaling/</link>
		<description>Recent content in Scaling on Alok Regmi</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sun, 19 Apr 2020 16:00:23 +0545</lastBuildDate>
		
			<atom:link href="https://alokregmi.com/tags/scaling/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Scaling</title>
				<link>https://alokregmi.com/braindump/2020/04/scaling/</link>
				<pubDate>Sun, 19 Apr 2020 16:00:23 +0545</pubDate>
				<guid>https://alokregmi.com/braindump/2020/04/scaling/</guid>
				<description>&lt;p&gt;Scalability of web request handling:&lt;/p&gt;&#xA;&lt;p&gt;That leads to the first golden rule for scalability: every server contains exactly the same codebase and does not store any user-related data, like sessions or profile pictures, on local disc or memory.&lt;/p&gt;&#xA;&lt;p&gt;Sessions need to be stored in a centralized data store which is accessible to all your application servers. It can be an external database or an external persistent cache, like Redis.&lt;/p&gt;&#xA;&lt;p&gt;After “outsourcing” your sessions and serving the same codebase from all your servers, you can now create an image file from one of these servers (AWS calls this AMI - Amazon Machine Image.)&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
