Level 3
Oct 14, 2015
5
Level 10
Micro Services Architecture
Hi,
I'm using Laravel 5.1 and some other Web API's such as Flickr, Stripe, Google Maps, Pusher etc for my application. Recently, a backend Engineer took a look at my app (not the code) and said I should focus on creating a Micro Service Architecture with JSON output for communication. I know Laravel and most of the API's that I'm using produces JSON outputs. So what exactly is he referring to? I didn't get an idea of Micro Service Architecture. Can anybody guide me?
Level 3
Level 48
The main idea with microservices is that instead of one large app you have many smaller apps that each do a small part and communicate with each other.
This can have a number of benefits.
Because each small piece is focused on only a small part they can be more lightweight and thus likely much faster performance-wise than a large app.
Pieces can be and often are written in different languages. You might have a small app written in Go, another using Python, etc...
In a large team you might have members assigned only to specific microservices reducing the need to understand the entire application.
There are also downsides to microservice architecture.
The more moving parts something has the more complex it gets and the harder it is to understand everything. Things like debugging get much harder and there are many more points pf failure.
Splitting an app up into microservices is sort of the "popular" thing to do right now regardless of whether it is actually a good fit for the particuar project. Everyone seems to like to think of their app as "enterprise" and wants to use the cool toys that come along with that like microservices, big data, event sourcing, and no-sql databases.
If your app is working fine as it is and the codebase is managable I wouldn't worry about microservices at this point. Maybe at some point it will be beneficial to split a piece or two out but I say wait until there is an actual benefit.
11 likes
Level 1
@spekkionu is 100% right. It's very time-consuming developing, maintaining (extending, updating and debugging) the APIs with micro-services architecture. But is a must for enterprise level applications where development teams are further split into smaller teams for particular microservice(s).
Link posted by @desdichado above has changed a little. New link on the same site is: https://blog.iron.io/creating-microservices-in-laravel-repost/ - Creating Microservices in Laravel (repost).
- updating old links and waking up the dead is my foremost priority so that the new zombies can relish the rusty chunks of bloody history engineered as we know it. ;P
my twitter handle: @QaziSalman1983 https://twitter.com/QaziSalman1983
1 like
Level 1
Implementing MicroServices Architecture using Laravel. https://medium.com/@munza/large-scale-laravel-application-9d52c3d38e51 Suggeting a link on how to structure, organize and plan to shift a domain to a new microservice with less hassle.
my twitter handle: @QaziSalman1983 https://twitter.com/QaziSalman1983
1 like
Please or to participate in this conversation.