3 ms·
I will respectfully disagree and say it's worth it in this case. Here's the reasons I see that makes it worth it: * It reduces the build time to less than 50%
by swsieber 10y ago
I will respectfully disagree and say it's worth it in this case.
Here's the reasons I see that makes it worth it:
* It reduces the build time to less than 50%
* They are doing this for 1000+ java applications
* The code vs library ratio is 1:100 (roughly) - that reduces the uploads from 50-100 GB cited in the article down to 50-100 MB.
- brianwawok 10y agoSo the real question is.. do they NEED 1000-2000 java applications? Or could it be much more sanely organized with say 15 or 20 applications? I know nothing about the codebase but it sounds like they may have nanoservices...
- HiJon89 10y agoIt's roughly 300 REST APIs and the rest are cron jobs, kafka workers, Hadoop or Spark jobs, etc. etc. Each part of the product gets its own API which is where most of them come from as our product is quite broad