techwithshakul is a place where you'll find tech gyaan varying from how basic things like internet works to more complex things like cloud. The channel attempts to cover the very basic of a challenging topic and explain it as simply as possible in layman's term.
Reach out to me at: Phone/Whatsapp- 9810477613 Email- shakul.mittal@gmail.com
I think you missed the main point about SOA which is having an ESB/Middleware between the business applications which acts as orchestrator. Also having a single DB where business services talk to can be scaled using DB replication as having one primary DB and multiple replica DB.Also I have a question , why would you host the DB on the same pod/container ? Why not have DB on a diff container ? This is better for scaling your services .
can we say SOA and Microservices architectures are quite similar except one thing which is SOA used same database across all the independent services while in microservices architecture each services used different database or same database but different schema ....please correct me if i am wrong thanks
Although a good video, it isn't technically correct to say SOA was restricted to one database. Many SOA systems had one database per service. Martin Fowler has a great video where he talks about how Microservices are nothing new, just SOA re-badged.
This is pure gold!, no, more than that, the examples are so great, being able to see differences between 3 architectures and knowing pros and cons is very cool, honestly I thought monolothic architecture was garbage but it is still useful, it's just different, thank you for the great explanation.
very good explanation, but for me it will be more helpfull if it is in English...If you do it in English will be benifited to many number of people rather than doing it in hindi.
