Re:Microservices
by dangrossman on Tuesday March 11, 2014 @07:28PM
(#7382934)
Calling them components seems reasonable to me. You generally can't replace components of physical machines while they're running either.
Edit: By machines I meant the physical world we borrow our vocabulary for abstractions from, not servers. You can't change the tires on a car while driving it, or the belts on a vacuum while cleaning.
"You generally can't replace components of physical machines while they're running either."
For some servers and mainframes you most certainly can replace components on the fly. It is a requirement for some places.
That depends quite a bit on the machine. For example servers.
Even if it does mean redeploying the application, i don't see what the problem is. If you're doing continuous delivery, you've already solved the problem of quickly rebuilding and redeploying. If you haven't solved that problem, solve it. It's not actually terrifically difficult.
Re:Microservices
by dragonwriter on Tuesday March 11, 2014 @07:57PM
(#7383064)
Simply put: quickly rebuilding and redeploying is good enough for some applications, but standing up a new version of a component seemlessly is necessary (or at least "sufficiently highly desirable to be worth considering in architecture decisions") in others.
Sure you can with OSGi/Java. Its made for this, osgi is component oriented programming. Its awesome.
I figured there was examples out there other than erlang. It just seemed like there are better reason for microservices like what flurry pointed out with legacy systems.
Sounds like some time an research on why we call something a component and then cannot replace it at runtime. I understand erlang has some features in this area.