How to Scale Up Services (from a principal services engineer)

Рет қаралды 1,351

Күн бұрын

This video describes the steps in scaling up a simple stand-alone service into a multi-service aggregate, based on my experience as a principal software engineer at Microsoft, Amazon, and Oracle, and working with Azure and Kindle back-end services.
TABLE OF CONTENTS
00:00 Thanks Mohab!
00:07 Introduction
01:30 Services start monolithic, e.g. "blurt"
02:28 Different pieces of "blurt"
03:12 "Blurt" scaling dimensions
04:06 Overview of pieces and their scaleup
05:33 Consider data flow
06:13 Make sure scale pieces are well-bounded
06:30 Keep single-machine validation
07:47 Separate out services
09:50 Summary

Пікірлер: 21

@Itachi.Uchiha.Offical 2 жыл бұрын

Definitely more of those technical videos! Starting out with a monolithic application is an important detail here, since designing and running a monolith will help identify future service boundaries and scaling needs. It's a lot easier than coming up with a microservice architecture from scratch.

@TheDeliberateEngineer 2 жыл бұрын

Thanks for watching and for the vote. And yeah, previous application provides data on what's important and HOW important. Data's always nice when you're making decisions :)

@BenjaminDickey 2 жыл бұрын

Would love more videos like this

@TheDeliberateEngineer 2 жыл бұрын

Thanks for watching and for the feedback!

@RHExcelion 2 жыл бұрын

More videos like this please, this is the kind of advice I came to your channel for as other system design channels only talk about theoretical/known designs and don't have your kind of experience in actually building these systems.

@TheDeliberateEngineer 2 жыл бұрын

Thank you for watching & for letting me know the kind of videos you're looking for! One challenge I face is I relied on a lot of internal tools for building such services. They only make sense if you're at the same company I worked at at the time. So, I talk in generalities, sounds like that is still useful which is good to know!

@barebears289 2 жыл бұрын

Thank for the lesson. We would love to see vids about microservices/distributed systems.

@TheDeliberateEngineer 2 жыл бұрын

thanks for watching and commenting!

@rabahalmuhtaseb3612 Жыл бұрын

Thank you for sharing your experience and yes, this is extremely valuable especially it's stemmed from real work.

@TheDeliberateEngineer Жыл бұрын

Thanks for watching & commenting, glad you found it useful!

@mohabkhaled1391 2 жыл бұрын

😃😃, watched, learned and enjoyed the video, it seems this pattern of evolving from a monolith to a micro service is the preferred way to do it instead of "big bang" to a microservice (although you mentioned at the beginning sometimes this is not the case ), i think naturally one of the subsequent videos will address the challenge of making these services "talk" to each other, as this seems the most challenging part of decomposing the monolith, that surprise at the beginning just made my day 😃, thank you !

@TheDeliberateEngineer 2 жыл бұрын

Thanks for suggesting this video for the feedback! Much appreciated!

@nshekhar2 2 жыл бұрын

That was very nicely explained. Thanks.

@TheDeliberateEngineer 2 жыл бұрын

I'm glad it was clear, thanks for watching!

@shantanushekharsjunerft9783 Жыл бұрын

More of it please 👍!

@TheDeliberateEngineer Жыл бұрын

thanks for watching & commenting!

@x86cowboy 2 жыл бұрын

This is great. More technical videos, please. Also, maybe a good video on techniques or useful patterns for debugging distributed systems might be a good topic too. Technical videos like this can sometimes help take hard-learned knowledge back to our teams.

@TheDeliberateEngineer 2 жыл бұрын

Thanks for watching & commenting! BTW, I do have one that talks in general about debugging distributed systems: "Debug your distributed system easier" - kzfaq.info/get/bejne/lZd0n6yVuJjDYKc.html

@itsonmylist1247 11 ай бұрын

Can u have a video on how to choose tasks or work item that have bigger impacts as in bigger org we might not know everything that’s happening

@KhaledElAnsari Жыл бұрын

I like the video though I have a question, isn't that approach a bit time consuming? I know going to SoA or micro-services from the beginning can lead to some spaghetti situation but it would save time don't you think? Also I would love to hear your opinion about tech docs, how it should be wrote? what are the main sections? how to show your work in it and come up with alternatives? etc. Thanks again for such a great content.

@TheDeliberateEngineer Жыл бұрын

One of the biggest problems with a scalable service is knowing how big you're going to get. Using constituent services from the start can be incredibly expensive from a financial (if you pay for those services) or engineering (if you build them) for services you may not need scalability for. You need data and experience. It's really rare to know the RIGHT tradeoff to make when you're building a service you haven't already sold to a big audience. Thanks for the comment & watching!