How to design and code a scaleable solution (from monolith to microservices)
Vložit
- čas přidán 15. 06. 2024
- Become a Patreon and get source code access: / nickchapsas
Check out my courses: dometrain.com
Hello everybody I'm Nick and in this video I will explain everything that you need to know about how you can scale your microservices. This video is useful for both Software Engineers and Solution Architects and touches upon everything that you need to be aware of when you are designing and coding your solution.
Don't forget to comment, like and subscribe :)
Social Media:
Follow me on GitHub: bit.ly/ChapsasGitHub
Follow me on Twitter: bit.ly/ChapsasTwitter
Connect on LinkedIn: bit.ly/ChapsasLinkedIn
#scale #microservices #cloud
This is one of the most useful channels i have shared it with my friends in my company and we really love your content nick keep posting and keep the good work up
that is really helpful thanks nick , you are doing a great job.
Useful content , thanks & hope u continue this series
A really useful video! Thanks for sharing. I’m trying to learn and build a project at the same time using MicroServices architecture
High quality content and to the point. I Like!
Best youtube .Net channel ever
Done thanks
Thanks for the content.
Maybe it worth to turn back and go deeper into this topic? Architecture knowledge is getting more and more demanding. Microservices nowadays are everywhere
Thanks so much for this video. What are the chances that you will do a video to physically show how to code and build a system with a couple of different microservices and the wiring necessary to put it all together?
I actually really wanted to do so but the problem with that is that it will be very hard to demonstrate over a series of videos and very long to do in a single video. I definitely want to but I don't have a clear plan in terms of how to do so.
Hi Nick very useful, is it ok if you gradually go deeper into microservices, teach us everything you know
how would it work for the database those APIs are sending/getting data from?
It would have to be databases that scale out too. Most of the NoSQL databases are designed with horizontal scaling in mind.
👍🏽
How do you ensure message is not consumed twice in Azure Service Bus Queue when scaling out number of consumers?
You don't. You aim for 'idempotency'. In mathematics an idempotent function is one that you can apply twice and the result will be the same as applying it once. Absolute value, for example. The absolute value of the absolute value of a number is the same as the absolute value of the number, so absolute value is an idempotent function. In this context I think it means that you build your service in a way that the outcome of handling a message twice is the same as handling it once. Then you don't need to guarantee that a message is only consumed once (which the two generals problem makes impossible), so you don't.
Yeah he explained that badly. I only understood what he meant because I already knew what idempotency meant in a related context, and am still not 100% sure.
Nice but a bit misleading. You don't need microservices to scale out. You can easily (think web apps were running on a single box before microservices were invented? :)) scale monoliths as long as you keep your application layer state free. Technically you can even scale out stateful application layer, state just needs to be pushed somewhere shared. In any application, including microservices, there is almost always a shared state somewhere such as some sort of database engine which is shared at least between few services or a service in front of that engine shared by multiple callers. Both monoliths and microservices have their place and trying to create artificial "monolith single box no scaley" vs "microservices endless scaly" distinction tends to distort the reality.
You are wrong about stateless systems and scaling. In fact most distributed systems are actor based (Orleans, akka).
I think I need to reduce the playback speed...
Very good channel but could you speak slower ? :)
use the playback speed