This guy is weirdly addictive 😁😁

This is the first video from this guy that I watch where he actually sounds approachable and down to earth.

TechLead, Can you revisit this topic? Maybe you've learned a better way since 2018 for scaling your product?

Thank you so much for making this. I really appreciate how you value simplicity over computational efficiency. I've always felt I'd rather spend a bit more to keep things simple and straight forward so in times of crisis the solutions are that much simpler and quicker to arrive at. The tips about database master/slave and the computed and cached queries is genius. I always feel a bit anxious when I write joins and am always curious whether or not it would be wiser to do two smaller queries or like you mentioned, have a cron job perform the join when server load is low (or on a slave) and then create a whole new table of the queried result. Great information! I truly appreciate it.

Incredible description, you explained everything just enough to understand the primary roles of each layer without getting too technical. These vids are great, keep it up!

This is better than a 5 how-to-scale-up-your-website articles combined. Easy to understand, practical, and to the point!

This is pure gold. You are awesome!

Not that I'm anywhere close to needing to scale something like this but it's always inspiring to listen to you 👏

This is the content I was waiting for.....interested in learning system design as I am already 2 years into software development... Thanks TechLead!!!

Dude I just found your channel and this is so helpful as a young app developer. Thank you!

This was the very first video of yours I ever watched. I never heard of you before, but I was on a kiteboarding trip driving home alone, and thumb searched for scaling AWS. In the first minute, I'm like - this guy sounds like he doesn't know anything lol... I proceeded to listen to your channel over mobile data connection for the next 6 hours of my trip. Wow awesome channel. Wish I had discovered it before!!! Just came out of a 10 year tech job.. happy to experience the down time and explore passions... like kiteboarding and salsa! Your channel is greatly inspiring.. sharing. And thanks!

wow , im a beginner jsut putting my first site out in a few weeks....this is a great summary of information..thank you

I have no clue about setting up websites, but I learned today how to setup a functioning system with slaves and masters. Thanks TechLead

Thanks Patrick for inspiring me alot I can now proudly say I have transformed alot from security to a junior database developer am now learning angularjs courtesy of you .

Your description is pretty accurate except for the load balancing part. Nginx or HAProxy are solid choices for load balancing and are desirable in a scalable architecture. I have also been using a similar architecture and have been able to achieve pretty awesome results!

Gonna memorise this for my interview

probably the most interesting video you put out. thank you patrick!

wow, I have always conflicted view on concurrent write atomicity issue whenever I try the master-slave approach, but it's clearer now. Thanks for the upload, its really helpful.

This is one of TechLead's best videos imo. I've done a bunch of server setups and full stack development and half of the stuff he mentioned never occured to me, like splitting users between databases based on a master user table. That being said I still think a load balancer is a good idea as it ultimately saves you time. Also Firebase or AWS is really a huge time saver, even if it does cost a bit more. For me personally the hours I spend trying to get all the configs and scripts right on a linux server and complaining all the dependencies from source with all the correct configs ends up taking so much extra time that the the price I spend on FIrebase or AWS is worth it. That being said if you want to go the configure it yourself route, this video is a treasure trove of really good ideas.

Simple and beautiful explanation. The only thing I found missing was the discussion on the upload speed/bandwidth of the server environment and what effect it can have on the user experience.

I am facing a similar situation and found your talk. You nicely vocalize some ideas which I was hatching for some time. Keep the server architecture simple, so that you can easily duplicate them for horizontal scaling. In very much agreement.

awesome! im walking this path and my mindset is basically the same as yours consistency is not aways necessary db queries must be optimized/background scripts must be set in place share the load the more you can

Wow, I was searching something that might help or give advice to me regarding on how to deploy a large scale system correctly and your video actually gave more than enough ideas on how to set it up properly.

I'm currently a performance engineer (used to be a software developer, most likely will go back to that soon). I'm currently working with techs such as OpenShift and the way we scale micro-services through OSE is with JMeter, SysDig, and Dynatrace. It's a combination of finding the right cpu/memory combo, along with optimizing the application code/config itself. Let's take a Java micro-service for example; gotta make sure the GC isn't going crazy, make sure you're actually using the right GC algorithm, making sure your multi threading isn't screwing up (thread pools, dead locks, etc.), doing some code review to ensure the algorithms used are as optimized as they can be, etc. Basically, just try to vertically scale the micro-service at first. Then, it's just a matter of verifying that when you scale horizontally, you actually double your performance and that it scales correctly. Finally, you can set the auto-scaler depending on your needs. That's the way my colleagues and I currently work when scaling web apps in a micro-service architecture right now.

6:16 issue with connection ,9:21 master-slave db setup , 10:41 db sharding

One of the best video I have seen. Very helpful

Ey, the endpoint configuration thing is a great idea to keep in mind!

Man, your videos lately are Killing it.

Good info! Definitely will use these tips in the future! You should do an episode on the Q&A from your subscribers.

About to deploy my first application. Thanks for this video!

Hello TechLead, I'm watching your channel since long time, and this one is pure gold! Thank you for sharing your experience. On my current project (as a team lead myself) I've decided to go with AWS Mobile hub, lambdas and DynamoDB. DynamoDB does not feel right for my project, though, but I'm looking for I'm using netlify.com as hosting. I'm deploying front-end React.js App statically generated html/js/css build with `react-static` from production and staging branches on push from git. For AWS lambda functions I'm using separate branch, and deploy functions to AWS with Claudia.js. Authentication goes smooth through Cognito - JWT. I've started the project before GraphQL was implemented in Mobile hub, and now I have 3 environments: development and staging on one aws account, and production on second aws account, and it is 16 tables for each environment. The architecture issue I'm experiencing is tough. For each page reload I'm requesting user authentication and only after authentication, I'm requesting ~700 products for a shop and storing it to Redux with Immutable.js for pagination and fuzzy search. In same request I'm receiving 5+ full tables. I feel like it is pretty long to request each item of a table iteratively, but another option called `Scan` is very fast (and costly $$$) Can you advise, would a switch to GraphQL solve my issues? The thing that worries me is that browser performance could drop down if I will use GraphQL right in components, oposite to storing data in Redux with Immutable.js.

Very nice detailed video! Thank you for this.

what a wonderfully concise scaling explanation !! 5 / 5 stars !

I understand everything you say because I worked in a really good startup. Nice talk.

Liked your video :) You are funny as all get out! The databases we used usually would do the job - but then again - I worked at SAP - so - they tend to have a dispatcher that would send the processing (when the user logged in) to an Application Server (which pretty much acts as a type of Middle ware). Whenever systems became slow, one would just add another Application Server. Queries on the DB were simple (although, you would get the Query From Hell every so often). As you have said, if you have a lot of Memory in use, the DB will pretty much sit in it. I remember working on one project where the company had 30,000 users/employees - but - it was determined that there would be 2000 Simultaneous users for the system (so, scaling efforts took place with that number - 2000 - in mind). One way they controlled the performance was to associate different applications with certain Application Servers. This way, the local data associated with that particular app could "cache" on that one App Server (ex; you would associate Human Resources on one App Server, Material Management on another App Server, etc.) Maybe you can look at Oracle for your data partitioning needs. They had table partitioning which would allow one to partition large data over several tables (and not have all of it located in just one table). Something like UserId would be the Key. The only time more than one DB would be used at a time was for backup purposes (Pepsi did this). The DB being used was Oracle - so - Offline Redo Logs would be copied (scp) to the machine that had the backup DB. The idea was that if the main DB got trashed, you could immediately switch over to the backup DB, turn it on and keep on going.

U've just narrated the entire system design of some web-app i know.. THIS IS THE TechLead!

Thanks for this video. I am doing an application that need all these stuff. So thank you again. 👍🏻

Your explanation helped me understand my assignment. Thank you so much for your sharing.

My 2 cents : You can use dynamic content on the CDN too. Most CDN's with their enormous infrastructure have direct routing to the origin servers. They bypass the traditional internet and the requests directly land on your server via the CDN. Plus you can use a global traffic management SAAS applications which most CDN provide to load balance based on geo.

This sounds so much like a high level system design interview.

This guy has experience. That's for sure.

So refreshing a tech lead video without sarcasm or bravado. More like this please.

Reducing load on dB server using caching layers like memcache, redis, cassandra. Using symbolic links to remote mount file systems. Database sharding. These are treasures of info.

Awesome and simple explanation! Thank you!

This has just given me so many insights of how to scale our product at work.

Maybe for another video it would be good to talk about monitoring the stack/infrastructure (maybe about failover too?) and the difference between named & concurrent user loads? :-)

Hi The Tech Lead, thank you for being the tech lead today for TechLead

Learned a Ton. Thanks for this.

Can you make a video on can flipping optimizations?

Nicely put together

This was very useful! Thank you!

Very informative, thank you for sharing this!

Great talk thank u. I really got quite a lot of ideas. You certainly are brilliant

F5's handle scaling well. Great video, thank you.

Love this video. TL describes a lot here

Thanks for sharing your experience.

Nice tips! I also try to minimize the amount of data that I am storing. Data that is not stored cannot be hacked (and costs less to maintain).

Switched to use Google App Engine because my one server setup was no longer coping with the load. Yes, had to rewrite the DB layer, but that was a lot easier than doing all the stuff you talked about.

Something I do to avoid heavy database calculations and lag time is have Oracle jobs run and create materialized views based on other table data, and it pretty much just became a look up from there. Typically had some beast servers for my databases though.

Excellent, direct to the point, extremely inspiring

straight to the point, nice, thx!

Thank you, sir. I learnt stuff today

Amazing! Just what I was searching for

Thanks dude great video !

Thanks techlead this is very informative.

Great information. Thank you!

Session persistence is handled via sticky sessions in load balanced environments (from what I've learned), cross load balanced environment the user will usually be re-directed to the original machine the session was created on, FYI I am using Azure at the moment to manage all these resources. You can scale up a database server, or scale out for read operations via replication. But overall I would agree about trying to reduce the amount of database interaction, caching data that doesn't change often, as database IO is an expensive IO operation (and usually the bottle neck of most large web infrastructures), but overall trying to develop in a very efficient manner while knowing the various limitations of the tech stack is important.

Great insight. I enjoy your videos.

We asked, he delivered! Thank you techlead!

I really love your videos, please keep up!

Astonishing explanation. In my experience, I have face a problem where we were running out of synchronization of data from database update to other microservices. There were IBM queues used to deal with synchronization, however they were getting old and slow also the support was not so good. So, I hav decided to replacing IBM quese with kafka pub/sub.

am I the only one who uses this channel for drink reviews?

Awesomely explained !

12-factor app patterns are a great place to start if you plan to scale up an app

TechLead, plz continue to teach us! :D

Thank You for your Sharing !

Awesome insight!!!

wow I learned so much. Thanks 👏👏👏

Great video!

great video!

amazing !! thank you!

You are an inspiration dude.

This is so valuable formation... thanks.

This guy gave a really clear explanation of this, thanks TechLead lol

Great video Sir, Please Please Please make more video like this.

Amazing tips. Thanks for sharing the information. Do you also have video on Database Sharding? I would like to know how to scale an application region wise. Would like to know what are things to be consisdered in terms of Database for regionwise deployment.

always new interesting stuff

very nice! you have used the principles of microservices before they have been standardised

Great Video!

Hey Techlead, could you do a video on how to flip a can like you did in the first few seconds of the video?

WOW! So you actually made the world a better place! That's AWESOME!

To provide a more pragmatic comment... For scaling a one man web application to 10 million users I would recommend cloud managed services as far as possible since you won't have the man power to keep your finger on all of the moving parts of your service. Using managed cloud services you don't have to manage servers and can save costs as well depending on how you configure your services. For static content I would use Cloudfront to serve static files hosted in S3 (they work well together since they both from AWS so you can do e.g. origin access identities to limit S3 access to only Cloudfront so that nobody can access your static content directly. Dynamic content can be managed with the app making requests to api gateway (serverless rest api managed service) with integration requests to either lambda (function as a service)+dynamodb (managed nosql db) if you want to go full serverless and not manage a single server. If you do want to manage your backend servers, api gateway can also integrate with an ALB (managed layer 7 load balancer) and have an autoscaling group that you can configure to automatically scale-in or scale-out your ec2 instances based on health checks done by the ALB. No need to script and stress. The ALB supports sticky sessions if you want to maintain a session to a backend instance, although this isn't necessary if you're using a stateless front-end app with token-based authentication (cognito to the rescue, another managed service).

You're just so ridiculous and amazing. Too good. Thanks for the info.

I think you should create a separate playlist for reviewing those drinks. 😂

Wow this drink review went off on a wild technical tangent.

not a programmer, but entrepreneur, its good to know this with the outsourced help i require. now i can speak their language.

Cookies are stored on the client and they are per domain. Sessions can be stored in a distributed memory fashion (using Memcached) or on a database.

OMG my favorite drink! The drink reminds me of Facebook ;). Thanks for making this video. I actually wanna learn more about performance and optimization. In one of my interview, the interviewer asked me about optimization!!

Thank you !

u also didn't mention about dns and direct connects. they play a huge part in reducing network latency, and api failovers. direct connect allows your edge dc server (where ur ui lives) to connect to your core dc servers (api process ,DB etc) in two hops. dns can auto route traffic to another dc if ur default dc goes down.