Managing Modular Software for your NuGet, C++ and Java Development
summary
JFrog explains that real modular builds need a binary repo that stores artifacts plus the exact build metadata so builds remain reproducible; the demo ties Maven/Gradle, Visual Studio/NuGet and TeamCity into Artifactory and shows a plugin that publishes build info (env, dependency graph, build number) with each artifact, prevents accidental deletion of build-used jars, and enables searches and retention policies. Claim: teams deploy multiple times a day (he cites four releases per day), and the integrated single source of truth workflow (Artifactory+TeamCity+NuGet/Maven) demonstrably works.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker intro
- 3:43Why modular software matters
- 12:26Dependencies and binary repositories
- 28:12Single source of truth for builds
- 42:27Modular software across languages
- 56:28Demo of modular build system
- 1:18:39License compliance and security checks
- 1:22:17Q&A and closing remarks
related talks
59mMajestic Modular Monoliths
46mWe Solved All Modular Project Problems. Want the Same?
47mMigrating to Modules
37mModularization - flatten your graph and get the real benefits
46mFrom Chaos to Cohesion: Building Modular Monoliths in the Real World
21mGit submodules: we have monorepo at home
47mModular Monoliths
32mReimagining Trust in Software Releases: A New Approach to Supply Chain Integrity (Part 2)