Level 3
I hope that Jeffery will notice this forum thread
Aug 3, 2022
7
Level 3
Why there are no screencasts for microservices
I was searching for a good resources showing the proper implemetation for microservices, and the communications between microservices and How the design of databases should be. I would ask Laracasts team to add a course to explain this topic.
Level 3
@jeffreyway Please read this
Level 5
Because in my opinion is overrated trend adopted by way to small teams/companies. I've done that same mistake, splitting my monoholic application into 5 microservices using laravel vapor. What I ended up was just confusion when wanted to change something, add something new. What a pain... I'm super happy that I was able to rewrite everything back to monoholic and put everything on one simple digital ocean server. When I will start hiring more than 70 developers, maybe I will come back to that idea, no sooner 🤣
1 like
Level 3
@monsterdream I'm curious about the best practices and techniques for implementation and interactions, Currenlty I'm not going to migrate my monolithic code to microservices, But in case we need to do so in the future so we can do it the right way.
Level 5
The topic is to complicated to give one simple solution and as always... It depends... And probably it's slow process, some day maybe you will realize that moving one part of your application make sense, after 3 years maybe you will realize that moving another make sense, and here you are 3 microservices at your service :-) Actually sorry, I was wrong, I left one app responsible only for generating pdf alone, that's work great but it needs some extra library installed on the server, that's why I left it probably. But don't bother, consume your energy on more important things. That's my advice.
1 like
Level 75
See https://aws.amazon.com/microservices/
A series isn't necessary as the coding is the same for example you may need to pull in some information from an API well that API could be classed as a microservice.
Not to mention there are far too many scenarios to attempt to cover.
One good example that I have seen is my doctor can pull up my list of medications but that is on a different server thus a microservice not even related to his system.
I believe the term is not even correct it should be called something like getting data from another source or a system, gdss. Just my opinion.
1 like
Level 80
@semicolon Because Laravel is a full stack framework and more suited to building monoliths than microservices.
1 like
Please or to participate in this conversation.