3 ms·
"One main reason for using services as components (rather than libraries) is that services are independently deployable. If you have an application [4] that con
by protomyth 13y ago
"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.
- dangrossman 13y agoCalling 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.
- dignan 13y agoThat depends quite a bit on the machine. For example servers.
- protomyth 13y ago"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.
- deleted 13y ago[deleted]
- deleted 13y ago[deleted]
- antocv 13y agoSure you can with OSGi/Java. Its made for this, osgi is component oriented programming. Its awesome.
- protomyth 13y agoI 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.
- antocv 13y agoJava osgi can. weird my other comment dissapeared anf you have dups.
- twic 13y agoEven 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.
- dragonwriter 13y agoSimply 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.