4 ms·
Interesting question arises here. Given most shops are now using interpreted languages, is it possible to make a change to say a .py file and ONLY deploy that .
by potbelly83 4y ago
Interesting question arises here. Given most shops are now using interpreted languages, is it possible to make a change to say a .py file and ONLY deploy that .py file to production? i.e. do incremental releases
- ar_lan 4y agoI don't know if "most shops are now using interpreted languages" is an accurate statement :) (I actually don't know). But I think that's definitely an interesting idea (likely with some small levels of extra caution with some specific high profile files, like an API definition/endpoint or something).
- potbelly83 4y agoHa no worries, to be fair most of my working life has been spent at C++ shops. I guess Windows does something similar via dlls.
- pojzon 4y agoThe issue was rather about the fact that changing that single .py file can have impact on a service A and service B which depend on service C where the file was changed. In microservice world, you have to run e2e tests because thats the only place where you can really guarantee the system will work as you expect. Pacts wont solve that, integration test - the same, units w/e. Running a monolith test is overall faster than spinning 20 microservices, beinging every db to specific atate and running tests.