Application Service Adapter uses different buildpacks than Tanzu Application Service, which you need to know when moving applications between the two platforms. This topic describes the differences between the two buildpack systems.
Application platforms such as Tanzu Application Service and Tanzu Application Platform use buildpacks to transform application source code and other assets into a self-contained artifact, such as a Cloud Foundry droplet or an Open Container Initiative container image. The platform then deploys this artifact to run instances of the application.
Tanzu Application Service uses Cloud Foundry buildpacks and provides a collection of system buildpacks that process many common languages and frameworks for cloud-native web applications. For more information about Cloud Foundry buildpacks, see How Buildpacks Work in the Tanzu Application Service documentation.
Tanzu Application Platform instead uses Tanzu Buildpacks, which implement the later Cloud Native Buildpack specification to process application source code. For more information about Cloud Native Buildpacks, see the Cloud Native Buildpacks project website.
An installation of Tanzu Application Platform provides a default collection of Tanzu Buildpacks, and Application Service Adapter uses this same set of Tanzu Buildpacks to stage Cloud Foundry applications. Although this collection of Tanzu Buildpacks processes many of the same application languages and frameworks that the Tanzu Application Service system buildpacks do, there are some differences in the set of languages it can process, as well as differences in how certain buildpacks detect application code or accept configuration parameters.
Tanzu Application Service provides the following system buildpacks for Linux-based applications:
- Binary buildpack
- Go buildpack
- Java buildpack
- .NET Core buildpack
- NGINX buildpack
- Node.js buildpack
- PHP buildpack
- Python buildpack
- R buildpack
- Ruby buildpack
- Staticfile buildpack
For many applications using these buildpacks on Tanzu Application Service, the suite of Tanzu Buildpacks contains a cloud-native buildpack that can process its language, frameworks, and build configuration. Tanzu Buildpacks are not currently available for R applications, although community-based solutions might be available.
Applications that use the binary buildpack in Tanzu Application Service should use the Tanzu Procfile Buildpack with Application Service Adapter. Applications must include a Procfile that defines the process types and their start commands if they do not already.
Applications that use the Go buildpack in Tanzu Application Service should use the Tanzu Go Buildpack with Application Service Adapter.
Applications that use the Java buildpack in Tanzu Application Service should use the Tanzu Java Buildpack or the Tanzu Java Native Image Buildpack with Application Service Adapter.
Applications that use the .NET Core buildpack in Tanzu Application Service should use the Tanzu .NET Core Buildpack with Application Service Adapter. For more information about migrating an application to use this buildpack, see Migrating to the Tanzu .NET Core Buildpack in the Tanzu Buildpacks documentation.
Applications that use the NGINX buildpack in Tanzu Application Service should use the Tanzu NGINX Buildpack with Application Service Adapter.
Applications that use the Node.js buildpack in Tanzu Application Service should use the Tanzu Node.js Buildpack with Application Service Adapter. For more information about migrating an application to use this buildpack, see Migrating to the Tanzu Node.js Buildpack in the Tanzu Buildpacks documentation.
Applications that use the PHP buildpack in Tanzu Application Service should use the Tanzu PHP Buildpack with Application Service Adapter. For more information about migrating an application to use this buildpack, see Migrating to the Tanzu PHP Buildpack in the Tanzu Buildpacks documentation.
Applications that use the Python buildpack in Tanzu Application Service should use the Tanzu Python Buildpack with Application Service Adapter.
Applications that use the Ruby buildpack in Tanzu Application Service should use the Tanzu Ruby Buildpack with Application Service Adapter.
Applications that use the Staticfile buildpack in Tanzu Application Service should use the Tanzu Web Servers Buildpack with Application Service Adapter.