are microservices a meme?
>>60128539
you're a meme
>>60128539
it's only soa with different services / appliction server granularity + utility services like service discovery and load balancing to make having lots of servers not too much of a pain
it's a pretty gud architectural design despite being a buzword
>>60128608
how does one learn this stuff without working with it everyday?
asking for a frontend dev friend
>>60128681
if you are interested in architeture design and whatnot just pick some books. up, they mostly are dry and theoritical tho
soa is mostly about defining groups for your domain objects to be in and services that would be called from the ui to perform various use cases by executing business logic and acting on domain objects.
you group services and related domain obects together in a somewhat cohesive manner as to limit inter dependencies between different service blocks. This is supposed to make these blocks loosely coupled and easier to change and upgrade.
Then instead of hosting these services on a monolithic application server interacting on one database you can embrace the memes and host each service / service group on its own application server with its own database. Then by using a loadbalancer and other tools you can set it up so that you can identify which part of the system is causing performance bottlenecks and just add more copies of the related server, if some servers are unavailable you can detect it and set more servers up etc
>>60128968
these tools seem to be designed by big companies to handle their mass scaling and availability constraints, such overengineered designs probably are overkill for most small applications
but i bet you could find some neat tutorials to make demo projects using your preferred web development stack
just look how to use the netflix stuff or other similar projects (eureka, zuul, hystrix and whatever)