Microservices in 1 Minute
ฝัง
- เผยแพร่เมื่อ 22 ม.ค. 2023
- in28minutes Roadmaps: github.com/in28minutes/roadmaps
Keep Learning in 1 Minute
1) Master Spring and Spring Boot with 10 Projects - links.in28minutes.com/sb
2) Download presentation PDF and Source Code - www.in28minutes.com/master-sp...
#shorts #in28minutes #java #microservices #learning
That's wrong.
1. The development cycle of monolithic apps depends on several factors and can be even faster than shipping microservices.
2. Microservices communication can be synchronous or asynchronous and REST apis is one of the synchronous ways
3. You need to test even when you make changes to mircroservices, to test both the changed microservice and the other ones as a result of this change.
4. The main benefit of microservices is having undependent teams working on different units of deployment that can be shipped undependently
really enjoying these 1 minutes videos sir
Wow, you are the only one who explains how microservices architecture is done in the way I want to have understood.
Ranga ive been watching your courses for a long time but i had no idea how your appeance look. wish the best for you.
these 1 minute minuscule reels are very helpful 👍🏼
Now it's time to rename in28seconds 😀,
anyway enjoying these videos Ranga..
Keep it up
Please also make one about Disadvantages/difficulties of/with Microservices ❤
very nice just got in within a minute tq
Keep it sir
It was fantastic
Except micro services are almost always dependent on others, so that means you have to waste time on building complex communication integration between them, then it also means it makes deployment even more complex because now you need to sync with multiple other services. In the end Monoliths are vastly simpler and can be made to be deployed fast, they can even use "pluggable" hot swappable design
In reality, if you build a monolith nowadays with Spring Boot you'll be able to ship much faster. Microservices Architecture solves some problems but brings in a host of other problems with it. For e.g debugging issues in microservices is a challenge because while in a monolith one can quickly check where the error occurred in a system there is no such quick visibility. No design pattern is perfect :)
I'm learning your 5 in 1 microservices course on udemy, nicely experience :)))
REST only?
Done😊
Only independent rest api or can be graphql too ?
Could be either.