try watching videos at 2x speed from now and in about a month you will be able to grasp that speed easily. Although you will end up becoming impatient in almost all of your activities like talking fast, walking fast etc. Siraj is such an example.
Haha, true that. :) But if you ever want to try, see if it works out. There are of course disadvantages to it like I mentioned, but in terms of understanding the material, you can definitely do it since our mind is capable of comprehending faster than any person on youtube can speak. Of course, the main goal should be to understand and not let speed take initiative, although this is just a suggestion(thats working for me right now). Maybe I will change my mind once I am a bit older. If thats the case I will re comment here. Good luck with your future endeavors :P
Interesting but makes no sense. Of course if you break something into multiple parts, the teams are going to have to communicate more with other teams because they are no longer on the same team. Foolishness. And how do you split a monolith into 5 parts and have those five parts be described as micro? Very misleading terminology. In what world does a monolith equal 5 micros?
That was a figurative description of course. - The best way I have seen it been described was with breaking it up into "user stories". The example that they used on user subscription is an excellent one. A microservice would entail that entire story from start to finish, including everything from CRUD the user and so on. But that's it. Any other part that needs the "services" provided by this microservice, has to communicate with it. There is a bit more complexity in the design, but think of application **instances** running at scale (rather than 10, think of 1000 - and yes, there are MANY like that in the world) and the manner by which independent scaling is achieved makes life an easier thing
