Dependency management
As part of the original 12-factor principle, it mandates that an application's dependencies should be clearly defined and not rely on a system-wide packaging/location. For example, don't rely on some location on disk, like /usr/local/lib, or the Global Assembly Cache (GAC) for .NET Applications, where dependency location is known and expected to always exist. This is because these locations are unlikely to be set up or exist when migrating to a Cloud platform. In modern dependency management, we have Maven/Gradle/NuGet for Java and .NET applications, respectively, where dependencies are defined and are pulled in during a build. Later in Chapter 9, Buildpacks, we will explore the concept of buildpacks, which set up dependency ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access