Skip to Content
Product Information

Which SAP Cloud Platform environment to choose: Cloud Foundry or Neo?

Which SAP Cloud Platform environment to choose: Cloud Foundry or Neo?

 

SAP Cloud Platform, as a major PaaS(Platform as a service) offer in the market, provides different operating systems, programming-language execution environments: Cloud Foundry and Neo.

For SAP Cloud Platform customers, the first decision need to make is: which environment to choose?

In this blog,I would like to give you a brief introduction on these 2 environments as follows.

  • Cloud Foundry Environment

SAP is a key member and contributor of the Cloud Foundry community-based platform – one of the most dynamic open source projects on the market today.

In SAP Cloud Platform, you could leverage a multitude of build packs, including community innovations and self-developed build packs. It also integrates with SAP HANA extended application services, advanced model (SAP HANA XSA). This run-time platform enables you to develop and deploy web applications, supporting multiple run times, programming languages, libraries, and services.

Application developers can use the Cloud Foundry environment to enhance SAP products and to integrate business applications, as well as to develop entirely new enterprise applications based on business APIs that are hosted on SAP Cloud Platform. The Cloud Foundry environment allows you to use multiple programming languages such as Java, Node.js, and community/bring-your-own language options. We recommend that you use the Cloud Foundry environment for 12-factor and/or micro-services-based applications, for Internet of Things and machine learning scenarios, and for developing applications using SAP HANA extended application services, advanced model (SAP HANA XSA).

  • Neo Environment

Neo is a feature-rich and easy-to-use development environment, allowing you to develop Java, SAP HANA XS, and HTML 5 applications. We recommend that you use the Neo environment to develop HTML 5 and complex Java applications and for complex integration and extension scenarios.

The following table provides an overview of the features, capabilities, and restrictions of each environment:

Criteria Cloud Foundry Environment Neo Environment
Best used for 12-factor- and/or microservice-based applications and services, IoT and machine learning scenarios, and XSA applications. Allows you to use multiple programming languages such as Java, Node.js, and community / bring-your-own language options. HTML5-based, SAP HANA XS, and complex Java applications.
Buildpacks/programming languages supported by SAP SAP-Java, Node.js., Node.js security buildpack (Beta) Java, HTML5, SAP HANA XS.
Additional buildpacks

Java, Python, Staticfile, Ruby, Go, PHP, Binary,etc.

 

*Note Support for additional buildpacks is limited. SAP regularly upgrades to new versions of the Cloud Foundry environment. Any fixes provided in updated versions of the buildpacks are available after the relevant upgrade. You can report issues with these buildpacks to SAP. Issues detected in the buildpacks are addressed to the relevant community, however, SAP only fixes issues that are related to SAP Cloud Platform itself.

Not available.
Maximum memory consumption of a single application instance 4 GB 16 GB
SAP HANA programming model SAP HANA extended application services, advanced model (SAP HANA XSA). SAP HANA extended application services, classic model (SAP HANA XS).
Virtual machines Not available. Available in selected regions.
Docker support Docker with Diego. Not available.
Certification Not available. ISO 27001, SOC1 Type 2, SOC2 Type 2.
On-premise connectivity HTTP on-premise connectivity is available.

The following is available:

·       HTTP on-premise connectivity

·       Service channels on-premise to cloud

·       LDAP integration

·       RFC on-premise connectivity.

Extension development Only selected scenarios. Available for SAP SuccessFactors and SAP S/4HANA.

 

The new Cloud-based transport management service (Beta) could be very interesting for customers who need to transport application development content between CF and Noe; or migrate application-specific content (SaaS scenarios).

Please check out this matrix to find out specific SCP service availabilities in different Environment and regions: SAP Cloud Platform Regions and Service Portfolio

Further steps: You could test the SAP Cloud Platform capacities in both Cloud Foundry and Neo Environment by creating Trial Accounts.

Configuring Your Neo Environment

Configuring Your Cloud Foundry Environment

Please read SAP Cloud Platform Road Map to discover SAP Cloud Platform new features.

Your comments would be very much appreciated.

2 Comments
You must be Logged on to comment or reply to a post.