4 ms·
>If yes, please, create a library. Assuming you want to force everyone to use the same technology stack. And redeploy every application every time the interna
by skwirl 11y ago
>If yes, please, create a library.
Assuming you want to force everyone to use the same technology stack. And redeploy every application every time the internals of the library change.
That may well be OK for what you are doing. Or not.
- marcosdumay 11y agoThe possibility to not redeploy instantly when the library changes may be the biggest win one get from not using services. Also, a library does not force people into the same technology stack. It makes it easier to work with the same programing language, but it's still possible to not do so. Microservices also often have complex data structures that only work well when created and parsed by the same set of tools. There is some difference, but much less than you are claiming.
- jessaustin 11y agoIf a library dictates a "technology stack", then maybe it's more of a "framework" than a "library"? I think we're supposed to deprecate those now.
- icebraining 11y agoA library dictates a stack since it's hard to use a Python library in an Haskell application.
- jessaustin 11y agoMany libraries have functional equivalents in other languages. Is there some python library that's so awesome it would have no equivalent in Haskell? (If you say "NumPy" I think you're veering into framework territory.)
- codygman 11y agoInterestingly I found these for using python libraries in Haskell: https://github.com/Russell91/pyfi https://github.com/Russell91/pyfi