Search
Search titles only
By:
Search titles only
By:
Log in
Register
Search
Search titles only
By:
Search titles only
By:
Menu
Install the app
Install
Forums
New posts
All threads
Latest threads
New posts
Trending threads
Trending
Search forums
What's new
New posts
New ads
New profile posts
Latest activity
Free Ads
Latest reviews
Search ads
Members
Current visitors
New profile posts
Search profile posts
Contact us
Latest ads
Ad icon
V2ray VPN for Tunneling
hu KANNA
Updated:
Thursday at 9:10 PM
FREE SEO Check & Google Maps Check for Sri Lankan Businesses | Web Design, Website Price Rs 14,900 |
LankaSolve
Updated:
Tuesday at 7:01 PM
ඕනම රටකට සෙට් වෙන CV එකක්
ErMurazor
Updated:
Oct 17, 2026
Hambantota
7 Acres Beachfront Land For Sell DownSouth , PerPerch Price 420 000
1024 Digital
Updated:
Oct 14, 2026
Baseus PI LITE INDOOR CAMERA
ErMurazor
Updated:
Oct 12, 2026
Electronics
Vehicles
Property
Search
Reply to thread
Forums
General
ElaKiri Talk!
fuelpass app එක හදන්නේ කොහොමද
Get the App
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="rockmon" data-source="post: 27966713" data-attributes="member: 563778"><p>mey site/app eka ubala haduwa nam kohomada hadanne ?</p><p></p><p>( dan eka nam React/TypeScript/ Backend php/node wenna one ,server nginx server)</p><p></p><p>aduma 1million concurrnet users/request handle karanne kohomada ?</p><p></p><p>mokadda tech stack eka ? LAMP or MERN</p><p></p><p>code level ekenda hadnle wenne or server configurations level ekenda ( multiple servers or load balancing )</p><p></p><p>budget eka kohoma weyida ?</p><p></p><p>any ideas elakiri SE experts or DevOps experts ?</p><p></p><p>ubala ehema hadapu example app/sites tiyenwada live ?</p><p></p><p></p><p><strong>programming language wala namak withrak danna epa, pulwuan nam podi explantion ekak denna</strong></p><p><strong></strong></p><p><strong></strong></p><p><strong></strong></p><p><strong>net eken ansswer ekaka</strong></p><p></p><p></p><p><span style="color: rgb(147, 101, 184)"><span style="font-size: 18px">For something like this; load balancing. The app can be running on many servers distributing the load. Once that is achieved, it's literally trivial (a few button clicks) to add/remove servers, or have AWS do it automatically with auto-scaling. Like maybe the bulk of your load is during US business hours. You could have 4 (or whatever) app servers running during those times, and only have 1 or 2 during off peak times.</span></span></p><p><span style="color: rgb(147, 101, 184)"><span style="font-size: 18px"></span></span></p><p><span style="color: rgb(147, 101, 184)"><span style="font-size: 18px"></span></span></p><p><span style="color: rgb(147, 101, 184)"><span style="font-size: 18px">This setup also helps with failover, as there isn't a single point of failure if you set it up right. If an app server goes down, the other servers just pick up the load. You destroy the bad server and bring up a new one with no downtime to your app. That can also be automated.</span></span></p><p><span style="color: rgb(147, 101, 184)"><span style="font-size: 18px"></span></span></p><p><span style="color: rgb(147, 101, 184)"><span style="font-size: 18px"></span></span></p><p><span style="color: rgb(147, 101, 184)"><span style="font-size: 18px">This type of setup is different from a typical setup. You'd have a separate db server that the other webservers share. You'd use S3 for storing all assets instead of on an individual server, so that all servers (acting as one) has access to the same data. If user A uploads a file to Server A, it needs to be accessible by servers B, C and D as well, so it can't be stored on the individual webserver.</span></span></p><p><span style="color: rgb(147, 101, 184)"><span style="font-size: 18px"></span></span></p><p><span style="color: rgb(147, 101, 184)"><span style="font-size: 18px"></span></span></p><p><span style="color: rgb(147, 101, 184)"><span style="font-size: 18px">The same goes for sessions. A user might login to server A, but the next request gets served from server B. So you need a common session store that all servers use, like redis.</span></span></p><p><span style="color: rgb(147, 101, 184)"><span style="font-size: 18px"></span></span></p><p><span style="color: rgb(147, 101, 184)"><span style="font-size: 18px"></span></span></p><p><span style="color: rgb(147, 101, 184)"><span style="font-size: 18px">Now you're just left with dumb webworkers, so you can just add new ones to increase capacity and scale.</span></span></p><p><span style="color: rgb(147, 101, 184)"><span style="font-size: 18px"></span></span></p><p><span style="color: rgb(147, 101, 184)"><span style="font-size: 18px"></span></span></p><p><span style="color: rgb(147, 101, 184)"><span style="font-size: 18px">Here's a good place to start learning: <a href="https://serversforhackers.com/c/so-you-got-yourself-a-loadbalancer" target="_blank">https://serversforhackers.com/c/so-you-got-yourself-a-loadbalancer</a></span></span></p></blockquote><p></p>
[QUOTE="rockmon, post: 27966713, member: 563778"] mey site/app eka ubala haduwa nam kohomada hadanne ? ( dan eka nam React/TypeScript/ Backend php/node wenna one ,server nginx server) aduma 1million concurrnet users/request handle karanne kohomada ? mokadda tech stack eka ? LAMP or MERN code level ekenda hadnle wenne or server configurations level ekenda ( multiple servers or load balancing ) budget eka kohoma weyida ? any ideas elakiri SE experts or DevOps experts ? ubala ehema hadapu example app/sites tiyenwada live ? [B]programming language wala namak withrak danna epa, pulwuan nam podi explantion ekak denna net eken ansswer ekaka[/B] [COLOR=rgb(147, 101, 184)][SIZE=5]For something like this; load balancing. The app can be running on many servers distributing the load. Once that is achieved, it's literally trivial (a few button clicks) to add/remove servers, or have AWS do it automatically with auto-scaling. Like maybe the bulk of your load is during US business hours. You could have 4 (or whatever) app servers running during those times, and only have 1 or 2 during off peak times. This setup also helps with failover, as there isn't a single point of failure if you set it up right. If an app server goes down, the other servers just pick up the load. You destroy the bad server and bring up a new one with no downtime to your app. That can also be automated. This type of setup is different from a typical setup. You'd have a separate db server that the other webservers share. You'd use S3 for storing all assets instead of on an individual server, so that all servers (acting as one) has access to the same data. If user A uploads a file to Server A, it needs to be accessible by servers B, C and D as well, so it can't be stored on the individual webserver. The same goes for sessions. A user might login to server A, but the next request gets served from server B. So you need a common session store that all servers use, like redis. Now you're just left with dumb webworkers, so you can just add new ones to increase capacity and scale. Here's a good place to start learning: [URL]https://serversforhackers.com/c/so-you-got-yourself-a-loadbalancer[/URL][/SIZE][/COLOR] [/QUOTE]
Insert quotes…
Verification
Awruddata maasa keeyada?
Post reply
Top
Bottom