News for hackers. Stuff that matters.
Re:Microservices by protomyth on Tuesday March 11, 2014 @07:25PM (#7382908)
"One main reason for using services as components (rather than libraries) is that services are independently deployable. If you have an application [4] that consists of a multiple libraries in a single process, a change to any single component results in having to redeploy the entire application."

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.

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.

Re:Microservices by protomyth on Tuesday March 11, 2014 @07:37PM (#7382976)
"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.

Re:Microservices by dignan on Tuesday March 11, 2014 @07:34PM (#7382964)
That depends quite a bit on the machine. For example servers.
Re:Microservices by twic on Tuesday March 11, 2014 @07:48PM (#7383025)
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.
Re:Microservices by antocv on Tuesday March 11, 2014 @07:36PM (#7382972)
Sure you can with OSGi/Java. Its made for this, osgi is component oriented programming. Its awesome.
Re:Microservices by protomyth on Tuesday March 11, 2014 @07:40PM (#7382987)
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.
Re:Microservices by antocv on Tuesday March 11, 2014 @07:37PM (#7382977)
Java osgi can.

weird my other comment dissapeared anf you have dups.