The apache software foundation has the first major release to camel k, an apparently "lightweight" cloud integration platform, confirmed. It is based on the apache camel framework in version 3.3.0. The platform runs natively on kubernetes and openshift and is mainly designed for serverless and microservice architectures.
Camel k with visual studio code
Nicola ferraro, co-gallery of the platform, describes the development style of camel k as a minimalist. It is obviously sufficient to write just a single file in an integration environment, which then exports directly to kubernetes clusters. This kind of defining things is because of many function as-a-service platforms (faas). However, camel k is probably around "no right faas platform", but an integration platform.
The developers want to have managed to provide developers ide support such as code resistance and similar, which is probably difficult for faas platforms. Camel k hold here some extensions for visual studio code. Developers do not have to remember the camel dsl syntax, as the ide makes you suggest and emphasizes errors. The selection of programming languages is not only limited to java.
Serverless or not serverless – both go
Camel k can be used both as well as without serverless functions. To the platform "serverless" to use, the serverless profile in camel k has to be activated and the cunning must be installed. The developers indicate to have already added support for the latest developments in kniper in previous versions. Accordingly, camel k is well integrated into the native event broker. Developers are possible to create and use events from it. Apparently, only the following two lines code are apparently such as the example from the release notes shows:
Bridge.Groovy from (‘paho: mytopic?Brokerurl = tcp: // broker-address: 1883clientid = kniper bridge ‘) .To (‘knizer: event / device-event’)
If you write these two lines in a file and leaves you with camel run bridge.Groovy is apparently pushing data in the kniper broker. Camel k stops more functions, such as an embedded automatic scaling function and overworking on compatibility and performance.
Support for camel quarkus in jvm mode
Within the framework of the releases, ferraro refers to camel quarkus, a short-started subproject of apache camel. The project pursues the goal of running integrations on the framework quarkus. The present first major release of camel k supports camel quarkus in jvm mode. The developers are planning a native in cluster compilation for some dsl languages for the upcoming versions (z. B. Yaml) to integrate.
With camel k 1.0.0 must developer probably apply applications that run on kubernetes, not pack a container image. It is sufficient to provide the integration dsl for. The operator ames what is necessary to carry out the applications, including the creation of images directly in the cluster.
Interested parties can download and try the new camel k uber github. Further information can be found next to github in the release notes.