Camel K 1.0.0 announcement #387
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We can merge this when it's official |
oscerd
approved these changes
Jun 8, 2020
davsclaus
reviewed
Jun 9, 2020
| and performance. This post contains a list of cool stuff that you'll find in the 1.0 GA release. | ||
|
|
||
| First of all, if you're living under a rock and it's the first time you hear about Camel K, | ||
| you can read some introductory blog posts here ([1 - introducing camel k ](https://nicolaferraro.me/2018/10/15/introducing-camel-k/), [2 - camel k on knative](https://www.nicolaferraro.me/2018/12/10/camel-k-on-knative/)) |
| but a lightweight *integration* platform) and it's technically difficult to provide IDE support, such as code completion and other utilities, | ||
| to developers. | ||
|
|
||
| But now we've it. The Red Hat Integration tooling team has created some cool extensions for VS Code that make the development experience |
There was a problem hiding this comment.
The Integration tooling team
| Code completion works with Java code, but it's not only limited to it: you also have suggestions and documentation out of the box when writing the Camel URIs and property files. | ||
| And you also have many options to run integrations and interact with them, all integrated in the IDE. | ||
|
|
||
| Just install the VS Code [Extension Pack for Apache Camel by Red Hat](https://marketplace.visualstudio.com/items?itemName=redhat.apache-camel-extension-pack) to have all these features available. |
There was a problem hiding this comment.
Extension Pack for Apache Camel
|
|
||
| The **basic quickstart is [also available online](https://learn.openshift.com/middleware/courses/middleware-camelk/camel-k-basic)**, so you can have a look at how camel k works **without installing anything on your laptop**. | ||
|
|
||
| More examples are expected to come in the following months. You are also welcome if you want to help us by **contributing your own**. |
| More examples are expected to come in the following months. You are also welcome if you want to help us by **contributing your own**. | ||
| They are based on the [VSCode Didact](https://marketplace.visualstudio.com/items?itemName=redhat.vscode-didact) project, that provides an | ||
| awesome user experience. | ||
|
|
There was a problem hiding this comment.
We could also add a section about the misc examples we have here
https://github.com/apache/camel-k/tree/master/examples
I do like the tutorials but they kinda assume you have the time and want to use Visual Code.
For people that just want to hack from CLI and a plain text editor (notepad++, emacs etc) then I would like to point them to these standalone. We could in the future port them or some of them to that example git repo.
There are some good ones here we could point to at first:
kamel run Sample.java
kamel run hello.xml
kamel run simple.js
| kamel init Handler.java | ||
| ``` | ||
|
|
||
| You get a Java file with **all the boilerplate written for you** and you just have to write your integration routes. It works also with all other languages: Groovy, XML, YAML, Kotlin and JavaScript. |
There was a problem hiding this comment.
Add an example for another language, eg
kamel init foo.js
| kamel run -d mvn:org.my:lib:1.0.0 -d mvn:org.my:otherlib:2.0.0 -t quarkus.enabled=true Handler.java | ||
| ``` | ||
|
|
||
| Sometimes the number of command line parameters you've to add **can become too many**. For this reason we've added the possibility to specify them as **modeline options** in the integration file. |
There was a problem hiding this comment.
(done by adding a comment line with camel-k: as prefix)
| Whenever you have an integration route that must be running, at any point in time, in at most one single Camel instance, you need to use a master route. Master routes can be declared by simply prefixing the consumer endpoint by the 'master' keyword and a name that will be used to create a named lock, e.g. | ||
|
|
||
| ``` | ||
| from('master:lock:telegram:bots') |
| .to('log:info') | ||
| ``` | ||
|
|
||
| It can be used to print all messages that are sent to your Telegram bot. Since the Telegram API support a single consumer only, you can guard the route with a master prefix to have the guarantee that the consumer will be only one. |
There was a problem hiding this comment.
that there will be at most only one consumer at any given time
|
|
||
| You can see that keeping a container with a JVM running for a task that should be executed once every two minutes may be overkill (it is overkill for sure when the period is 2 hours). We live in a time where resources such as **memory and CPU are really valuable**. | ||
|
|
||
| So the Camel K operator automatically handles this situation by deploying your integration not as a Kubernetes deployment, but as a **Kubernetes CronJob**. This saves a lot of resources, especially when the period between executions is high. When it's time to run your integration code, a container starts, triggers the execution and then gracefully terminates. Everything is handled automatically by the Camel K runtime. |
There was a problem hiding this comment.
by the Camel K runtime -> by Camel K and Kubernetes.
|
Thanks @davsclaus , I think I've addressed all the points |
davsclaus
approved these changes
Jun 9, 2020
oscerd
approved these changes
Jun 9, 2020
|
Are we ok on merging this? @nicolaferraro @davsclaus |
|
+1 |
zregvart
reviewed
Jun 10, 2020
| but a lightweight *integration* platform) and it's technically difficult to provide IDE support, such as code completion and other utilities, | ||
| to developers. | ||
|
|
||
| But now we've it. The integration tooling team has created some cool extensions for VS Code that make the development experience |
There was a problem hiding this comment.
Perhaps:
Suggested change
| But now we've it. The integration tooling team has created some cool extensions for VS Code that make the development experience | |
| But now we've have it. The integration tooling team has created some cool extensions for VS Code that make the development experience |
| and performance. This post contains a list of cool stuff that you'll find in the 1.0 GA release. | ||
|
|
||
| First of all, if you're living under a rock and it's the first time you hear about Camel K, | ||
| you can read some introductory blog posts here ([1 - introducing camel k](https://nicolaferraro.me/2018/10/15/introducing-camel-k/), [2 - camel k on knative](https://www.nicolaferraro.me/2018/12/10/camel-k-on-knative/)) |
There was a problem hiding this comment.
Would be cool to cross post this to Camel blog as well
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.