codbex

Kronos Edition

Source Code

Kronos Edition provides a compatible environment for SAP HANA Extended Application Services (XS) based applications. It is deployed outside of SAP HANA instance as a Docker a container on Kubernetes. Hence, some of the features can work against any other JDBC compliant RDBMS such as PostgreSQL. The compatibility stack is an extension of the Eclipse Dirigible cloud development platform.

This is the official fork of the Project “XSK”, which was discontinued by SAP in 2022.

Landscapes - Before and After Migration

The main difference is that the engine running the application is now outside HANA instance, hence it is possible to run it for scale on any Kubernetes or Containers as a Service offering - SAP or non-SAP.

Screenshot

Artefacts Handling

Native execution of the XS Classic artefacts acheiving near 100% compatibility and completeness is the main driving force behind the product.

Screenshot

XSJS Development Experience

Supporting further development experience brings limitless benefits for future applications enhancements.

Screenshot

ABAP Development Experience

ABAP development is introduced as an experimental feature by leveraging the Open ABAP and ABAP Lint frameworks.

Screenshot

Snowflake

Connecting and analyzing the massive amount of data in Snowflake cloud database is supported out of the box.

Screenshot

Development Experience

Aspect Scope Description
Preserve hdb* descriptors ✅  
Preserve XSJS code ✅  
Preserve XSOData descriptors ✅  
Preserve XSC development model ✅  
Preserve XSC security model ⚠️ Authentication is managed by the runtime container
Support for XSJS code ✅  

Life-cycle Management

Aspect Scope Description
End-to-end life-cycle management ✅  
Single-step migration ✅  
Can be deployed as a monolith ✅  
Can be deployed as a microservices ✅  
Can be deployed on Kubernetes ✅  
Can be deployed on Cloud Foundry ✅  

Artifacts Coverage

Aspect Scope Description
.xsjs ✅  
.xsjslib ✅  
.calculationview ⚠️  
.hdbprocedure ✅  
.hdbrole ❌  
.hdbsequence ✅  
.xsodata ⚠️  
.hdbdd ⚠️  
.xsaccess ✅  
.xsjob ✅  
.xssecurestore ✅  
.hdbti (+csv) ✅  
.xshttpdest ✅  
.hdbschema ✅  

XSJS APIs Coverage

Aspect Scope Description
$.session ⚠️ Represents an SAP HANA XS session
$.request ✅ Represents the client HTTP request currently being processed.
$.response ✅ Represents the HTTP response currently being populated.
$.hdb ✅ This namespace provides means for seamless HANA database access. It is intended to be a replacement of the older $.db namespace
$.db ✅ Namespace for HANA database access
$.util ✅ Util namespace
$.trace ✅ Trace namespace
$.import ✅ Imports a server-side JavaScript library artifact
$.net ✅ Network namespace
$.net.http ✅ HTTP namespace
$.util.codec ✅ Codec namespace
$.web ✅ Web namespace
$.security ✅ Security namespace

FAQ

  • How long will Kronos be supported?

    Kronos is an open source project with community support. Everyone can join and make a PR. In fact SAP discontinued official support to project “XSK”, and this fork maintained by the same developers is prove that the approach is viable and useful. The company codbex provide enterprise support for Kronos based runtimes.

  • Should future developments be based on Kronos?

    Yes, you can use Kronos for future development.

  • What about the tooling? Do we get state of the art tooling for maintaining and enhancing Kronos?

    Kronos tooling is based on Eclipse Dirigible and in the near future it will be possible to maintain Kronos projects with any modern IDE like VSCode, Eclipse Theia, etc.

  • What about the ops aspects - will Kronos be smoothly integrated into a state-of-the-art lifecycle and ops management (be it SAP-based or non-SAP based like GitHub Actions?

    Yes, the Kronos itself uses GitHub actions for CI/CD

  • Will there be limitations that will not be mitigated?

    You can get the up-to-date list of covered features as well as the limitations, cheat sheet and readiness.


Support depends on the plan you selected from Pricing.