You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2020/08/10 20:48:19 UTC

[GitHub] [camel-website] ppalaga opened a new pull request #454: Blog post: Camel Quarkus 1.0.0

ppalaga opened a new pull request #454:
URL: https://github.com/apache/camel-website/pull/454


   An early version. Any feedback is welcome!


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] ppalaga commented on pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
ppalaga commented on pull request #454:
URL: https://github.com/apache/camel-website/pull/454#issuecomment-672786586


   54e8265: addressed the comments of @davsclaus and adopted all changes (thanks!) from @aldettinger 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] jamesnetherton commented on a change in pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
jamesnetherton commented on a change in pull request #454:
URL: https://github.com/apache/camel-website/pull/454#discussion_r468337652



##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,77 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-07-07
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+Apache Camel community celebrates the release 1.0.0 of Camel Quarkus!
+
+## What is Camel Quarkus?
+
+Camel Quarkus brings the outstanding integration capabilities of Apache Camel to [Quarkus](https://quarkus.io/) - the
+toolkit for writing subatomically small and supersonically fast Java, Kotlin and Scala applications.
+
+It is suitable not only for creating long living services and potentially short living serverless applications
+but also for [command-style applications](https://camel.apache.org/blog/2020/07/command-line-utility-with-camel-quarkus/)
+that execute some task and exit.
+
+## Developer joy
+
+Writing integrations has never offered more developer joy than with Camel Quarkus:
+
+* Easy to start with: either via [code.quarkus.io](https://code.quarkus.io/) or using `mvn quarkus:create`
+* The "live coding" feature, a.k.a. `mvn compile quarkus:dev` shortens your development iterations
+* Easy to test using JUnit 5 extensions
+* Shields from the complexity of the native compilation using [GraalVM](https://www.graalvm.org/) or

Review comment:
       ```suggestion
   * Hides the complexity of the native compilation using [GraalVM](https://www.graalvm.org/) or
   ```

##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,77 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-07-07
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+Apache Camel community celebrates the release 1.0.0 of Camel Quarkus!
+
+## What is Camel Quarkus?
+
+Camel Quarkus brings the outstanding integration capabilities of Apache Camel to [Quarkus](https://quarkus.io/) - the
+toolkit for writing subatomically small and supersonically fast Java, Kotlin and Scala applications.
+
+It is suitable not only for creating long living services and potentially short living serverless applications
+but also for [command-style applications](https://camel.apache.org/blog/2020/07/command-line-utility-with-camel-quarkus/)
+that execute some task and exit.
+
+## Developer joy
+
+Writing integrations has never offered more developer joy than with Camel Quarkus:
+
+* Easy to start with: either via [code.quarkus.io](https://code.quarkus.io/) or using `mvn quarkus:create`
+* The "live coding" feature, a.k.a. `mvn compile quarkus:dev` shortens your development iterations
+* Easy to test using JUnit 5 extensions
+* Shields from the complexity of the native compilation using [GraalVM](https://www.graalvm.org/) or
+  [Mandrell](https://github.com/graalvm/mandrel)
+
+
+## The journey to 1.0.0
+
+[Luca](https://github.com/lburgazzoli) and [Guillaume](https://github.com/gnodet) started porting Camel to
+[Quarkus](https://github.com/quarkusio/quarkus) very early while Quarkus was still in the stealth mode at Red Hat.
+The work started around November 2018 and was
+[merged to Quarkus master](https://github.com/quarkusio/quarkus/commit/549c74d74f4ae6af83854e51f14db429adef7483) on Feb.
+28, 2019 - shortly before Quarkus was
+[publicly announced](https://developers.redhat.com/blog/2019/03/07/quarkus-next-generation-kubernetes-native-java-framework/)
+on March 7, 2019. At that time, Quarkus
+[supported just a handful of Camel components](https://github.com/quarkusio/quarkus/tree/0.11.0/extensions/camel)
+
+The next important milestone was donating the Camel specific bits from the main Quarkus source tree to Apache Software
+Foundation (ASF). This happened around July 2019 and the current
+[GitHub home of the project](https://github.com/apache/camel-quarkus) is the result.
+
+Under the new home, the project attracted a fair amount of new contributors which in turn brought a lot of
+contributions.
+
+## Where are we now?
+
+Since the early beginnings the number of supported Camel bits went up substantially. These are the numbers of Camel
+components supported on Quarkus as of Quarkus 1.0.0 and Camel 3.4:
+
+* 155 out of 350 Camel components (44%)
+* 27 out of 43 Camel data formats (63%)
+* 13 out of 17 Camel languages (76%)
+* 17 out of 42 miscellaneous Camel components (40%)
+
+The complete list is [here](https://camel.apache.org/camel-quarkus/latest/list-of-camel-quarkus-extensions.html)
+
+## Who is using Camel Quarkus?
+
+While we mostly have only indirect information about the usage via
+[GitHub issues](https://github.com/apache/camel-quarkus/issues), there is one prominent user, we are especially proud
+of: [Camel K](https://camel.apache.org/camel-k/latest/index.html). As of
+[Camel K 1.0](https://camel.apache.org/blog/2020/06/camel-k-release-1.0.0#fast-startup-and-low-memory), Camel Quarkus is
+one of the two supported runtimes and is "is expected to be the default underlying runtime in the next release".
+
+## Highlights of the release 1.0.0
+
+TODO:
+bootstrapping methods
+reflectionless

Review comment:
       > reflectionless
   
   We can't really make that claim yet as https://github.com/apache/camel-quarkus/issues/1108 wont be fixed until we get an updated Camel release.

##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,77 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-07-07
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+Apache Camel community celebrates the release 1.0.0 of Camel Quarkus!

Review comment:
       ```suggestion
   The Apache Camel community celebrates the 1.0.0 release of Camel Quarkus!
   ```




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] aldettinger commented on pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
aldettinger commented on pull request #454:
URL: https://github.com/apache/camel-website/pull/454#issuecomment-672727320


   @ppalaga well done :+1 Looks good overall. I proposed changes in the 2nd commit, feel free to take what you like.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] zregvart commented on pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
zregvart commented on pull request #454:
URL: https://github.com/apache/camel-website/pull/454#issuecomment-671599491


   > > a featured image is missing
   > 
   > Any hints where to get one?
   
   Have a look at [unsplash](https://unsplash.com/s/photos/camel)


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] ppalaga commented on a change in pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
ppalaga commented on a change in pull request #454:
URL: https://github.com/apache/camel-website/pull/454#discussion_r468439072



##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,77 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-07-07
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+Apache Camel community celebrates the release 1.0.0 of Camel Quarkus!
+
+## What is Camel Quarkus?
+
+Camel Quarkus brings the outstanding integration capabilities of Apache Camel to [Quarkus](https://quarkus.io/) - the
+toolkit for writing subatomically small and supersonically fast Java, Kotlin and Scala applications.
+
+It is suitable not only for creating long living services and potentially short living serverless applications
+but also for [command-style applications](https://camel.apache.org/blog/2020/07/command-line-utility-with-camel-quarkus/)
+that execute some task and exit.
+
+## Developer joy
+
+Writing integrations has never offered more developer joy than with Camel Quarkus:
+
+* Easy to start with: either via [code.quarkus.io](https://code.quarkus.io/) or using `mvn quarkus:create`
+* The "live coding" feature, a.k.a. `mvn compile quarkus:dev` shortens your development iterations
+* Easy to test using JUnit 5 extensions
+* Shields from the complexity of the native compilation using [GraalVM](https://www.graalvm.org/) or
+  [Mandrell](https://github.com/graalvm/mandrel)
+
+
+## The journey to 1.0.0
+
+[Luca](https://github.com/lburgazzoli) and [Guillaume](https://github.com/gnodet) started porting Camel to
+[Quarkus](https://github.com/quarkusio/quarkus) very early while Quarkus was still in the stealth mode at Red Hat.
+The work started around November 2018 and was
+[merged to Quarkus master](https://github.com/quarkusio/quarkus/commit/549c74d74f4ae6af83854e51f14db429adef7483) on Feb.
+28, 2019 - shortly before Quarkus was
+[publicly announced](https://developers.redhat.com/blog/2019/03/07/quarkus-next-generation-kubernetes-native-java-framework/)
+on March 7, 2019. At that time, Quarkus
+[supported just a handful of Camel components](https://github.com/quarkusio/quarkus/tree/0.11.0/extensions/camel)
+
+The next important milestone was donating the Camel specific bits from the main Quarkus source tree to Apache Software
+Foundation (ASF). This happened around July 2019 and the current
+[GitHub home of the project](https://github.com/apache/camel-quarkus) is the result.
+
+Under the new home, the project attracted a fair amount of new contributors which in turn brought a lot of
+contributions.
+
+## Where are we now?
+
+Since the early beginnings the number of supported Camel bits went up substantially. These are the numbers of Camel
+components supported on Quarkus as of Quarkus 1.0.0 and Camel 3.4:
+
+* 155 out of 350 Camel components (44%)
+* 27 out of 43 Camel data formats (63%)
+* 13 out of 17 Camel languages (76%)
+* 17 out of 42 miscellaneous Camel components (40%)
+
+The complete list is [here](https://camel.apache.org/camel-quarkus/latest/list-of-camel-quarkus-extensions.html)
+
+## Who is using Camel Quarkus?
+
+While we mostly have only indirect information about the usage via
+[GitHub issues](https://github.com/apache/camel-quarkus/issues), there is one prominent user, we are especially proud
+of: [Camel K](https://camel.apache.org/camel-k/latest/index.html). As of
+[Camel K 1.0](https://camel.apache.org/blog/2020/06/camel-k-release-1.0.0#fast-startup-and-low-memory), Camel Quarkus is
+one of the two supported runtimes and is "is expected to be the default underlying runtime in the next release".
+
+## Highlights of the release 1.0.0
+
+TODO:
+bootstrapping methods
+reflectionless

Review comment:
       Indeed, let me remove it.




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] ppalaga commented on a change in pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
ppalaga commented on a change in pull request #454:
URL: https://github.com/apache/camel-website/pull/454#discussion_r469155511



##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,131 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-08-10
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+<sub><sup>Original image by <a href="https://commons.wikimedia.org/wiki/User:99of9">Toby Hudson</a> <a href="https://creativecommons.org/licenses/by-sa/3.0">CC BY-SA 3.0</a> via <a href="https://en.wikipedia.org/wiki/Camel_racing#/media/File:CamelRacingCamelCup2009Heat.JPG">Wikipedia</a></sup></sub>
+
+The Apache Camel community celebrates the release 1.0.0 of Camel Quarkus!
+
+## What is Camel Quarkus?
+
+Camel Quarkus brings the outstanding integration capabilities of Apache Camel to [Quarkus](https://quarkus.io/) - the
+toolkit for writing subatomically small and supersonically fast Java, Kotlin and Scala applications. In addition to
+memory consumption and start time improvements on stock JVMs, Quarkus also allows for compiling applications to
+[native executables](https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html#_package_and_run_the_application)
+thus improving the performance characteristics even more.
+
+Camel Quarkus is suitable not only for creating long living services and potentially short living serverless
+applications but also for
+[command-style applications](https://camel.apache.org/blog/2020/07/command-line-utility-with-camel-quarkus/)
+that execute some specific task (or wait for some specific condition) and exit.
+
+## Developer joy
+
+Writing integrations has never been more joyful for developers than with Camel Quarkus:
+
+* Easy to start with: either via [code.quarkus.io](https://code.quarkus.io/) or using `mvn quarkus:create`
+* The "live coding" feature, a.k.a. `mvn compile quarkus:dev` shortens your development iterations - check
+  [this 2 mins video](https://www.youtube.com/watch?v=4lXSf8DBQkQ)
+* Easy to test using JUnit 5 extensions
+* Hides the complexity of the native compilation using [GraalVM](https://www.graalvm.org/) or
+  [Mandrell](https://github.com/graalvm/mandrel)
+
+Check our https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html[User guide]!
+
+## Camel components coverage
+
+Since the [early beginnings](https://github.com/quarkusio/quarkus/tree/0.11.0/extensions/camel) the number of supported
+Camel bits went up substantially. As of Quarkus 1.0.0 and
+Camel 3.4, Camel Quarkus supports:
+
+* 155 out of 350 Camel components (44%)
+* 27 out of 43 Camel data formats (63%)
+* 13 out of 17 Camel languages (76%)
+* 17 out of 42 miscellaneous Camel components (40%)
+
+Some of these are supported in JVM mode only - please refer to the
+[complete list](https://camel.apache.org/camel-quarkus/latest/list-of-camel-quarkus-extensions.html) for details.
+
+## Bootstrapping methods
+
+There are two ways to bootstrap and configure Camel Quarkus:
+
+1. Bare
+2. With Camel Main
+
+Both methods configure and start a Camel Context for you. The main difference is in how much the resulting Camel Context
+obeys the conventions known from Camel on other platforms. If you like to configure your routes using
+`camel.component.*` properties, then you need to add the `camel-quarkus-main` dependency and the properties
+will work as usual on Camel standalone or Camel SpringBoot. Of course, this brings some overhead. You may prefer this
+option if you used Camel before or if you are migrating from other platform.
+
+If you rather come from the Quarkus side and you never wrote Camel integrations before, you may choose to use the bare

Review comment:
       > > It reads as if it is two "big" alternatives, that you cannot use CDI with Camel Main, and vice versa.
   > 
   > Good point, the text should not awake that impression.
   
   Adding `You can configure Camel using CDI even if you have Camel Main in your application.`




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] ppalaga commented on a change in pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
ppalaga commented on a change in pull request #454:
URL: https://github.com/apache/camel-website/pull/454#discussion_r469110992



##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,131 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-08-10
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+<sub><sup>Original image by <a href="https://commons.wikimedia.org/wiki/User:99of9">Toby Hudson</a> <a href="https://creativecommons.org/licenses/by-sa/3.0">CC BY-SA 3.0</a> via <a href="https://en.wikipedia.org/wiki/Camel_racing#/media/File:CamelRacingCamelCup2009Heat.JPG">Wikipedia</a></sup></sub>
+
+The Apache Camel community celebrates the release 1.0.0 of Camel Quarkus!
+
+## What is Camel Quarkus?
+
+Camel Quarkus brings the outstanding integration capabilities of Apache Camel to [Quarkus](https://quarkus.io/) - the
+toolkit for writing subatomically small and supersonically fast Java, Kotlin and Scala applications. In addition to

Review comment:
       OK, let's remove Scala. Although there is scala extension and scala should work, it is not especially promoted from the Quarkus side.




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] ppalaga merged pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
ppalaga merged pull request #454:
URL: https://github.com/apache/camel-website/pull/454


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] oscerd commented on a change in pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
oscerd commented on a change in pull request #454:
URL: https://github.com/apache/camel-website/pull/454#discussion_r468177530



##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,77 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-07-07

Review comment:
       Isn't it 08?




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] zregvart commented on a change in pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
zregvart commented on a change in pull request #454:
URL: https://github.com/apache/camel-website/pull/454#discussion_r469108752



##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,130 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-08-10
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+<sub><sup>Original image by <a href="https://commons.wikimedia.org/wiki/User:99of9">Toby Hudson</a> <a href="https://creativecommons.org/licenses/by-sa/3.0">CC BY-SA 3.0</a> via <a href="https://en.wikipedia.org/wiki/Camel_racing#/media/File:CamelRacingCamelCup2009Heat.JPG">Wikipedia</a></sup></sub>

Review comment:
       Might make sense to add [manual summary](https://gohugo.io/content-management/summaries/#front-matter-summary), this bit ends up in the [blog post list](https://deploy-preview-454--camel.netlify.app/blog/).




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] ppalaga commented on pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
ppalaga commented on pull request #454:
URL: https://github.com/apache/camel-website/pull/454#issuecomment-671598569


   > a featured image is missing
   
   Any hints where to get one?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] ppalaga commented on pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
ppalaga commented on pull request #454:
URL: https://github.com/apache/camel-website/pull/454#issuecomment-672221725


   5f484b7
   
   * Removed the history paragraph
   * Fixed the issues found by @oscerd  and @jamesnetherton 
   * More text
   * Good to merge from my PoV
   
   Please re-review


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] zregvart commented on a change in pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
zregvart commented on a change in pull request #454:
URL: https://github.com/apache/camel-website/pull/454#discussion_r469464091



##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,132 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-08-10
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: The first stable release of Camel Quarkus
+summary: Walk through the highlights of the first stable release: Developer joy, Camel component coverage, Bootstrap, CDI, native mode and more!

Review comment:
       Looks [good](https://deploy-preview-454--camel.netlify.app/blog/).




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] ppalaga commented on pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
ppalaga commented on pull request #454:
URL: https://github.com/apache/camel-website/pull/454#issuecomment-672798618


   1c79c88: added double quotes to summary value


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] davsclaus commented on a change in pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
davsclaus commented on a change in pull request #454:
URL: https://github.com/apache/camel-website/pull/454#discussion_r469087553



##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,131 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-08-10
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+<sub><sup>Original image by <a href="https://commons.wikimedia.org/wiki/User:99of9">Toby Hudson</a> <a href="https://creativecommons.org/licenses/by-sa/3.0">CC BY-SA 3.0</a> via <a href="https://en.wikipedia.org/wiki/Camel_racing#/media/File:CamelRacingCamelCup2009Heat.JPG">Wikipedia</a></sup></sub>
+
+The Apache Camel community celebrates the release 1.0.0 of Camel Quarkus!
+
+## What is Camel Quarkus?
+
+Camel Quarkus brings the outstanding integration capabilities of Apache Camel to [Quarkus](https://quarkus.io/) - the
+toolkit for writing subatomically small and supersonically fast Java, Kotlin and Scala applications. In addition to
+memory consumption and start time improvements on stock JVMs, Quarkus also allows for compiling applications to
+[native executables](https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html#_package_and_run_the_application)
+thus improving the performance characteristics even more.
+
+Camel Quarkus is suitable not only for creating long living services and potentially short living serverless
+applications but also for
+[command-style applications](https://camel.apache.org/blog/2020/07/command-line-utility-with-camel-quarkus/)
+that execute some specific task (or wait for some specific condition) and exit.
+
+## Developer joy
+
+Writing integrations has never been more joyful for developers than with Camel Quarkus:
+
+* Easy to start with: either via [code.quarkus.io](https://code.quarkus.io/) or using `mvn quarkus:create`
+* The "live coding" feature, a.k.a. `mvn compile quarkus:dev` shortens your development iterations - check
+  [this 2 mins video](https://www.youtube.com/watch?v=4lXSf8DBQkQ)
+* Easy to test using JUnit 5 extensions
+* Hides the complexity of the native compilation using [GraalVM](https://www.graalvm.org/) or
+  [Mandrell](https://github.com/graalvm/mandrel)
+
+Check our https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html[User guide]!
+
+## Camel components coverage
+
+Since the [early beginnings](https://github.com/quarkusio/quarkus/tree/0.11.0/extensions/camel) the number of supported
+Camel bits went up substantially. As of Quarkus 1.0.0 and
+Camel 3.4, Camel Quarkus supports:
+
+* 155 out of 350 Camel components (44%)
+* 27 out of 43 Camel data formats (63%)
+* 13 out of 17 Camel languages (76%)
+* 17 out of 42 miscellaneous Camel components (40%)
+
+Some of these are supported in JVM mode only - please refer to the
+[complete list](https://camel.apache.org/camel-quarkus/latest/list-of-camel-quarkus-extensions.html) for details.
+
+## Bootstrapping methods
+
+There are two ways to bootstrap and configure Camel Quarkus:
+
+1. Bare
+2. With Camel Main
+
+Both methods configure and start a Camel Context for you. The main difference is in how much the resulting Camel Context
+obeys the conventions known from Camel on other platforms. If you like to configure your routes using
+`camel.component.*` properties, then you need to add the `camel-quarkus-main` dependency and the properties
+will work as usual on Camel standalone or Camel SpringBoot. Of course, this brings some overhead. You may prefer this

Review comment:
       Spring Boot (there is a space between)

##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,131 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-08-10
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+<sub><sup>Original image by <a href="https://commons.wikimedia.org/wiki/User:99of9">Toby Hudson</a> <a href="https://creativecommons.org/licenses/by-sa/3.0">CC BY-SA 3.0</a> via <a href="https://en.wikipedia.org/wiki/Camel_racing#/media/File:CamelRacingCamelCup2009Heat.JPG">Wikipedia</a></sup></sub>
+
+The Apache Camel community celebrates the release 1.0.0 of Camel Quarkus!
+
+## What is Camel Quarkus?
+
+Camel Quarkus brings the outstanding integration capabilities of Apache Camel to [Quarkus](https://quarkus.io/) - the
+toolkit for writing subatomically small and supersonically fast Java, Kotlin and Scala applications. In addition to
+memory consumption and start time improvements on stock JVMs, Quarkus also allows for compiling applications to
+[native executables](https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html#_package_and_run_the_application)
+thus improving the performance characteristics even more.
+
+Camel Quarkus is suitable not only for creating long living services and potentially short living serverless
+applications but also for
+[command-style applications](https://camel.apache.org/blog/2020/07/command-line-utility-with-camel-quarkus/)
+that execute some specific task (or wait for some specific condition) and exit.
+
+## Developer joy
+
+Writing integrations has never been more joyful for developers than with Camel Quarkus:
+
+* Easy to start with: either via [code.quarkus.io](https://code.quarkus.io/) or using `mvn quarkus:create`
+* The "live coding" feature, a.k.a. `mvn compile quarkus:dev` shortens your development iterations - check
+  [this 2 mins video](https://www.youtube.com/watch?v=4lXSf8DBQkQ)
+* Easy to test using JUnit 5 extensions
+* Hides the complexity of the native compilation using [GraalVM](https://www.graalvm.org/) or
+  [Mandrell](https://github.com/graalvm/mandrel)
+
+Check our https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html[User guide]!

Review comment:
       In preview then this link looked broken.

##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,131 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-08-10
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+<sub><sup>Original image by <a href="https://commons.wikimedia.org/wiki/User:99of9">Toby Hudson</a> <a href="https://creativecommons.org/licenses/by-sa/3.0">CC BY-SA 3.0</a> via <a href="https://en.wikipedia.org/wiki/Camel_racing#/media/File:CamelRacingCamelCup2009Heat.JPG">Wikipedia</a></sup></sub>
+
+The Apache Camel community celebrates the release 1.0.0 of Camel Quarkus!
+
+## What is Camel Quarkus?
+
+Camel Quarkus brings the outstanding integration capabilities of Apache Camel to [Quarkus](https://quarkus.io/) - the
+toolkit for writing subatomically small and supersonically fast Java, Kotlin and Scala applications. In addition to

Review comment:
       I am not so sure Quarkus is well known for fast Scala applications. I dont think the Scala community think of Quarkus as a Scala framework they are using. I dont think you can find Scala mentioned on the quarkus website.
   
   I would remove Scala. 

##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,131 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-08-10
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+<sub><sup>Original image by <a href="https://commons.wikimedia.org/wiki/User:99of9">Toby Hudson</a> <a href="https://creativecommons.org/licenses/by-sa/3.0">CC BY-SA 3.0</a> via <a href="https://en.wikipedia.org/wiki/Camel_racing#/media/File:CamelRacingCamelCup2009Heat.JPG">Wikipedia</a></sup></sub>
+
+The Apache Camel community celebrates the release 1.0.0 of Camel Quarkus!
+
+## What is Camel Quarkus?
+
+Camel Quarkus brings the outstanding integration capabilities of Apache Camel to [Quarkus](https://quarkus.io/) - the
+toolkit for writing subatomically small and supersonically fast Java, Kotlin and Scala applications. In addition to
+memory consumption and start time improvements on stock JVMs, Quarkus also allows for compiling applications to
+[native executables](https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html#_package_and_run_the_application)
+thus improving the performance characteristics even more.
+
+Camel Quarkus is suitable not only for creating long living services and potentially short living serverless
+applications but also for
+[command-style applications](https://camel.apache.org/blog/2020/07/command-line-utility-with-camel-quarkus/)
+that execute some specific task (or wait for some specific condition) and exit.
+
+## Developer joy
+
+Writing integrations has never been more joyful for developers than with Camel Quarkus:
+
+* Easy to start with: either via [code.quarkus.io](https://code.quarkus.io/) or using `mvn quarkus:create`
+* The "live coding" feature, a.k.a. `mvn compile quarkus:dev` shortens your development iterations - check
+  [this 2 mins video](https://www.youtube.com/watch?v=4lXSf8DBQkQ)
+* Easy to test using JUnit 5 extensions
+* Hides the complexity of the native compilation using [GraalVM](https://www.graalvm.org/) or
+  [Mandrell](https://github.com/graalvm/mandrel)
+
+Check our https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html[User guide]!
+
+## Camel components coverage
+
+Since the [early beginnings](https://github.com/quarkusio/quarkus/tree/0.11.0/extensions/camel) the number of supported
+Camel bits went up substantially. As of Quarkus 1.0.0 and
+Camel 3.4, Camel Quarkus supports:
+
+* 155 out of 350 Camel components (44%)
+* 27 out of 43 Camel data formats (63%)
+* 13 out of 17 Camel languages (76%)
+* 17 out of 42 miscellaneous Camel components (40%)
+
+Some of these are supported in JVM mode only - please refer to the
+[complete list](https://camel.apache.org/camel-quarkus/latest/list-of-camel-quarkus-extensions.html) for details.
+
+## Bootstrapping methods
+
+There are two ways to bootstrap and configure Camel Quarkus:
+
+1. Bare
+2. With Camel Main
+
+Both methods configure and start a Camel Context for you. The main difference is in how much the resulting Camel Context
+obeys the conventions known from Camel on other platforms. If you like to configure your routes using
+`camel.component.*` properties, then you need to add the `camel-quarkus-main` dependency and the properties
+will work as usual on Camel standalone or Camel SpringBoot. Of course, this brings some overhead. You may prefer this
+option if you used Camel before or if you are migrating from other platform.
+
+If you rather come from the Quarkus side and you never wrote Camel integrations before, you may choose to use the bare

Review comment:
       I would say from CDI side - its not really Quarkus side. CDI is a bit "coding heavy" in terms of configuration as this requires Java coding and adding annotations and whatnot.
   
   It reads as if it is two "big" alternatives, that you cannot use CDI with Camel Main, and vice versa. 
   

##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,131 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-08-10
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+<sub><sup>Original image by <a href="https://commons.wikimedia.org/wiki/User:99of9">Toby Hudson</a> <a href="https://creativecommons.org/licenses/by-sa/3.0">CC BY-SA 3.0</a> via <a href="https://en.wikipedia.org/wiki/Camel_racing#/media/File:CamelRacingCamelCup2009Heat.JPG">Wikipedia</a></sup></sub>
+
+The Apache Camel community celebrates the release 1.0.0 of Camel Quarkus!
+
+## What is Camel Quarkus?
+
+Camel Quarkus brings the outstanding integration capabilities of Apache Camel to [Quarkus](https://quarkus.io/) - the
+toolkit for writing subatomically small and supersonically fast Java, Kotlin and Scala applications. In addition to
+memory consumption and start time improvements on stock JVMs, Quarkus also allows for compiling applications to
+[native executables](https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html#_package_and_run_the_application)
+thus improving the performance characteristics even more.
+
+Camel Quarkus is suitable not only for creating long living services and potentially short living serverless
+applications but also for
+[command-style applications](https://camel.apache.org/blog/2020/07/command-line-utility-with-camel-quarkus/)
+that execute some specific task (or wait for some specific condition) and exit.
+
+## Developer joy
+
+Writing integrations has never been more joyful for developers than with Camel Quarkus:
+
+* Easy to start with: either via [code.quarkus.io](https://code.quarkus.io/) or using `mvn quarkus:create`
+* The "live coding" feature, a.k.a. `mvn compile quarkus:dev` shortens your development iterations - check
+  [this 2 mins video](https://www.youtube.com/watch?v=4lXSf8DBQkQ)
+* Easy to test using JUnit 5 extensions
+* Hides the complexity of the native compilation using [GraalVM](https://www.graalvm.org/) or
+  [Mandrell](https://github.com/graalvm/mandrel)
+
+Check our https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html[User guide]!
+
+## Camel components coverage
+
+Since the [early beginnings](https://github.com/quarkusio/quarkus/tree/0.11.0/extensions/camel) the number of supported
+Camel bits went up substantially. As of Quarkus 1.0.0 and
+Camel 3.4, Camel Quarkus supports:
+
+* 155 out of 350 Camel components (44%)
+* 27 out of 43 Camel data formats (63%)
+* 13 out of 17 Camel languages (76%)
+* 17 out of 42 miscellaneous Camel components (40%)
+
+Some of these are supported in JVM mode only - please refer to the
+[complete list](https://camel.apache.org/camel-quarkus/latest/list-of-camel-quarkus-extensions.html) for details.
+
+## Bootstrapping methods
+
+There are two ways to bootstrap and configure Camel Quarkus:
+
+1. Bare
+2. With Camel Main
+
+Both methods configure and start a Camel Context for you. The main difference is in how much the resulting Camel Context
+obeys the conventions known from Camel on other platforms. If you like to configure your routes using
+`camel.component.*` properties, then you need to add the `camel-quarkus-main` dependency and the properties
+will work as usual on Camel standalone or Camel SpringBoot. Of course, this brings some overhead. You may prefer this
+option if you used Camel before or if you are migrating from other platform.
+
+If you rather come from the Quarkus side and you never wrote Camel integrations before, you may choose to use the bare
+bootstrap and configure your routes using CDI.
+
+See the [Bootstrap section](https://camel.apache.org/camel-quarkus/latest/user-guide/bootstrap.html) of the User guide
+for more details.
+
+## CDI
+
+CDI plays a central role in Quarkus and Camel Quarkus offers a first class support for it too. You may use `@Inject`,
+`@ConfigProperty` and other annotations e.g. to inject beans and configuration values to your Camel RouteBuilder's.
+See the [CDI section](https://camel.apache.org/camel-quarkus/latest/user-guide/cdi.html) of the User guide for more
+details.
+
+## Native mode
+
+As mentioned above, Quarkus brings the option to compile an application to native executable. Compared to running on
+JVM, native applications start faster, require less memory at runtime and are also smaller on disk.
+
+However, the native compilation with GraalVM is all but easy and straightforward. First, there are
+[limitations](https://github.com/oracle/graal/blob/master/substratevm/LIMITATIONS.md) for what your code and all your
+dependencies may or may not do. Second, the native compiler needs to be configured through many options that may

Review comment:
       may or may not be easy -> not easy
   
   I dont think anything with graalvm is easy for the average user.

##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,131 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-08-10
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+<sub><sup>Original image by <a href="https://commons.wikimedia.org/wiki/User:99of9">Toby Hudson</a> <a href="https://creativecommons.org/licenses/by-sa/3.0">CC BY-SA 3.0</a> via <a href="https://en.wikipedia.org/wiki/Camel_racing#/media/File:CamelRacingCamelCup2009Heat.JPG">Wikipedia</a></sup></sub>
+
+The Apache Camel community celebrates the release 1.0.0 of Camel Quarkus!
+
+## What is Camel Quarkus?
+
+Camel Quarkus brings the outstanding integration capabilities of Apache Camel to [Quarkus](https://quarkus.io/) - the
+toolkit for writing subatomically small and supersonically fast Java, Kotlin and Scala applications. In addition to
+memory consumption and start time improvements on stock JVMs, Quarkus also allows for compiling applications to
+[native executables](https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html#_package_and_run_the_application)
+thus improving the performance characteristics even more.
+
+Camel Quarkus is suitable not only for creating long living services and potentially short living serverless
+applications but also for
+[command-style applications](https://camel.apache.org/blog/2020/07/command-line-utility-with-camel-quarkus/)
+that execute some specific task (or wait for some specific condition) and exit.
+
+## Developer joy
+
+Writing integrations has never been more joyful for developers than with Camel Quarkus:
+
+* Easy to start with: either via [code.quarkus.io](https://code.quarkus.io/) or using `mvn quarkus:create`
+* The "live coding" feature, a.k.a. `mvn compile quarkus:dev` shortens your development iterations - check
+  [this 2 mins video](https://www.youtube.com/watch?v=4lXSf8DBQkQ)
+* Easy to test using JUnit 5 extensions
+* Hides the complexity of the native compilation using [GraalVM](https://www.graalvm.org/) or
+  [Mandrell](https://github.com/graalvm/mandrel)
+
+Check our https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html[User guide]!
+
+## Camel components coverage
+
+Since the [early beginnings](https://github.com/quarkusio/quarkus/tree/0.11.0/extensions/camel) the number of supported
+Camel bits went up substantially. As of Quarkus 1.0.0 and
+Camel 3.4, Camel Quarkus supports:
+
+* 155 out of 350 Camel components (44%)
+* 27 out of 43 Camel data formats (63%)
+* 13 out of 17 Camel languages (76%)
+* 17 out of 42 miscellaneous Camel components (40%)
+
+Some of these are supported in JVM mode only - please refer to the
+[complete list](https://camel.apache.org/camel-quarkus/latest/list-of-camel-quarkus-extensions.html) for details.
+
+## Bootstrapping methods
+
+There are two ways to bootstrap and configure Camel Quarkus:
+
+1. Bare
+2. With Camel Main
+
+Both methods configure and start a Camel Context for you. The main difference is in how much the resulting Camel Context
+obeys the conventions known from Camel on other platforms. If you like to configure your routes using
+`camel.component.*` properties, then you need to add the `camel-quarkus-main` dependency and the properties
+will work as usual on Camel standalone or Camel SpringBoot. Of course, this brings some overhead. You may prefer this

Review comment:
       Of course this brings some overhead? What overhead and why of course. From end user perspectice this may actually be easier. Its more flexible and works better for externalized configuration.
   
   I would tone down this as it seems you are saying "dont do this".




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] ppalaga commented on a change in pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
ppalaga commented on a change in pull request #454:
URL: https://github.com/apache/camel-website/pull/454#discussion_r469157255



##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,130 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-08-10
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+<sub><sup>Original image by <a href="https://commons.wikimedia.org/wiki/User:99of9">Toby Hudson</a> <a href="https://creativecommons.org/licenses/by-sa/3.0">CC BY-SA 3.0</a> via <a href="https://en.wikipedia.org/wiki/Camel_racing#/media/File:CamelRacingCamelCup2009Heat.JPG">Wikipedia</a></sup></sub>

Review comment:
       Let me add a summary




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] ppalaga commented on a change in pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
ppalaga commented on a change in pull request #454:
URL: https://github.com/apache/camel-website/pull/454#discussion_r468194937



##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,77 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-07-07

Review comment:
       Yes, thanks for catching it! A copy-and-paste problem :)




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] lburgazzoli commented on a change in pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
lburgazzoli commented on a change in pull request #454:
URL: https://github.com/apache/camel-website/pull/454#discussion_r469134043



##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,131 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-08-10
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+<sub><sup>Original image by <a href="https://commons.wikimedia.org/wiki/User:99of9">Toby Hudson</a> <a href="https://creativecommons.org/licenses/by-sa/3.0">CC BY-SA 3.0</a> via <a href="https://en.wikipedia.org/wiki/Camel_racing#/media/File:CamelRacingCamelCup2009Heat.JPG">Wikipedia</a></sup></sub>
+
+The Apache Camel community celebrates the release 1.0.0 of Camel Quarkus!
+
+## What is Camel Quarkus?
+
+Camel Quarkus brings the outstanding integration capabilities of Apache Camel to [Quarkus](https://quarkus.io/) - the
+toolkit for writing subatomically small and supersonically fast Java, Kotlin and Scala applications. In addition to
+memory consumption and start time improvements on stock JVMs, Quarkus also allows for compiling applications to
+[native executables](https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html#_package_and_run_the_application)
+thus improving the performance characteristics even more.
+
+Camel Quarkus is suitable not only for creating long living services and potentially short living serverless
+applications but also for
+[command-style applications](https://camel.apache.org/blog/2020/07/command-line-utility-with-camel-quarkus/)
+that execute some specific task (or wait for some specific condition) and exit.
+
+## Developer joy
+
+Writing integrations has never been more joyful for developers than with Camel Quarkus:
+
+* Easy to start with: either via [code.quarkus.io](https://code.quarkus.io/) or using `mvn quarkus:create`
+* The "live coding" feature, a.k.a. `mvn compile quarkus:dev` shortens your development iterations - check
+  [this 2 mins video](https://www.youtube.com/watch?v=4lXSf8DBQkQ)
+* Easy to test using JUnit 5 extensions
+* Hides the complexity of the native compilation using [GraalVM](https://www.graalvm.org/) or
+  [Mandrell](https://github.com/graalvm/mandrel)
+
+Check our https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html[User guide]!
+
+## Camel components coverage
+
+Since the [early beginnings](https://github.com/quarkusio/quarkus/tree/0.11.0/extensions/camel) the number of supported
+Camel bits went up substantially. As of Quarkus 1.0.0 and
+Camel 3.4, Camel Quarkus supports:
+
+* 155 out of 350 Camel components (44%)
+* 27 out of 43 Camel data formats (63%)
+* 13 out of 17 Camel languages (76%)
+* 17 out of 42 miscellaneous Camel components (40%)
+
+Some of these are supported in JVM mode only - please refer to the
+[complete list](https://camel.apache.org/camel-quarkus/latest/list-of-camel-quarkus-extensions.html) for details.
+
+## Bootstrapping methods
+
+There are two ways to bootstrap and configure Camel Quarkus:
+
+1. Bare
+2. With Camel Main
+
+Both methods configure and start a Camel Context for you. The main difference is in how much the resulting Camel Context
+obeys the conventions known from Camel on other platforms. If you like to configure your routes using
+`camel.component.*` properties, then you need to add the `camel-quarkus-main` dependency and the properties
+will work as usual on Camel standalone or Camel SpringBoot. Of course, this brings some overhead. You may prefer this

Review comment:
       I think this just boils down how you want to use camel-quarkus: as a library or as an application runtime.
   
   IMHO, camel-quarkus-core is for embedding camel functionalities with full control, whereas camel-quarkus-main is mainly for application.
   




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] ppalaga commented on a change in pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
ppalaga commented on a change in pull request #454:
URL: https://github.com/apache/camel-website/pull/454#discussion_r469163390



##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,132 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-08-10
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: The first stable release of Camel Quarkus
+summary: Walk through the highlights of the first stable release: Developer joy, Camel component coverage, Bootstrap, CDI, native mode and more!

Review comment:
       @zregvart I hope this would work as a summary?




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] ppalaga commented on a change in pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
ppalaga commented on a change in pull request #454:
URL: https://github.com/apache/camel-website/pull/454#discussion_r469155150



##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,131 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-08-10
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+<sub><sup>Original image by <a href="https://commons.wikimedia.org/wiki/User:99of9">Toby Hudson</a> <a href="https://creativecommons.org/licenses/by-sa/3.0">CC BY-SA 3.0</a> via <a href="https://en.wikipedia.org/wiki/Camel_racing#/media/File:CamelRacingCamelCup2009Heat.JPG">Wikipedia</a></sup></sub>
+
+The Apache Camel community celebrates the release 1.0.0 of Camel Quarkus!
+
+## What is Camel Quarkus?
+
+Camel Quarkus brings the outstanding integration capabilities of Apache Camel to [Quarkus](https://quarkus.io/) - the
+toolkit for writing subatomically small and supersonically fast Java, Kotlin and Scala applications. In addition to
+memory consumption and start time improvements on stock JVMs, Quarkus also allows for compiling applications to
+[native executables](https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html#_package_and_run_the_application)
+thus improving the performance characteristics even more.
+
+Camel Quarkus is suitable not only for creating long living services and potentially short living serverless
+applications but also for
+[command-style applications](https://camel.apache.org/blog/2020/07/command-line-utility-with-camel-quarkus/)
+that execute some specific task (or wait for some specific condition) and exit.
+
+## Developer joy
+
+Writing integrations has never been more joyful for developers than with Camel Quarkus:
+
+* Easy to start with: either via [code.quarkus.io](https://code.quarkus.io/) or using `mvn quarkus:create`
+* The "live coding" feature, a.k.a. `mvn compile quarkus:dev` shortens your development iterations - check
+  [this 2 mins video](https://www.youtube.com/watch?v=4lXSf8DBQkQ)
+* Easy to test using JUnit 5 extensions
+* Hides the complexity of the native compilation using [GraalVM](https://www.graalvm.org/) or
+  [Mandrell](https://github.com/graalvm/mandrel)
+
+Check our https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html[User guide]!
+
+## Camel components coverage
+
+Since the [early beginnings](https://github.com/quarkusio/quarkus/tree/0.11.0/extensions/camel) the number of supported
+Camel bits went up substantially. As of Quarkus 1.0.0 and
+Camel 3.4, Camel Quarkus supports:
+
+* 155 out of 350 Camel components (44%)
+* 27 out of 43 Camel data formats (63%)
+* 13 out of 17 Camel languages (76%)
+* 17 out of 42 miscellaneous Camel components (40%)
+
+Some of these are supported in JVM mode only - please refer to the
+[complete list](https://camel.apache.org/camel-quarkus/latest/list-of-camel-quarkus-extensions.html) for details.
+
+## Bootstrapping methods
+
+There are two ways to bootstrap and configure Camel Quarkus:
+
+1. Bare
+2. With Camel Main
+
+Both methods configure and start a Camel Context for you. The main difference is in how much the resulting Camel Context
+obeys the conventions known from Camel on other platforms. If you like to configure your routes using
+`camel.component.*` properties, then you need to add the `camel-quarkus-main` dependency and the properties
+will work as usual on Camel standalone or Camel SpringBoot. Of course, this brings some overhead. You may prefer this

Review comment:
       I decided to remove the sentence. Thanks for the feedback.




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] ppalaga commented on pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
ppalaga commented on pull request #454:
URL: https://github.com/apache/camel-website/pull/454#issuecomment-672791306


   b6f138e: added a summary


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] ppalaga commented on a change in pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
ppalaga commented on a change in pull request #454:
URL: https://github.com/apache/camel-website/pull/454#discussion_r468817016



##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,77 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-07-07
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+Apache Camel community celebrates the release 1.0.0 of Camel Quarkus!

Review comment:
       +1




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] zregvart commented on pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
zregvart commented on pull request #454:
URL: https://github.com/apache/camel-website/pull/454#issuecomment-672281259


   We need #455 merged for the build to succeed.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] ppalaga commented on a change in pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
ppalaga commented on a change in pull request #454:
URL: https://github.com/apache/camel-website/pull/454#discussion_r469129233



##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,131 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-08-10
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+<sub><sup>Original image by <a href="https://commons.wikimedia.org/wiki/User:99of9">Toby Hudson</a> <a href="https://creativecommons.org/licenses/by-sa/3.0">CC BY-SA 3.0</a> via <a href="https://en.wikipedia.org/wiki/Camel_racing#/media/File:CamelRacingCamelCup2009Heat.JPG">Wikipedia</a></sup></sub>
+
+The Apache Camel community celebrates the release 1.0.0 of Camel Quarkus!
+
+## What is Camel Quarkus?
+
+Camel Quarkus brings the outstanding integration capabilities of Apache Camel to [Quarkus](https://quarkus.io/) - the
+toolkit for writing subatomically small and supersonically fast Java, Kotlin and Scala applications. In addition to
+memory consumption and start time improvements on stock JVMs, Quarkus also allows for compiling applications to
+[native executables](https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html#_package_and_run_the_application)
+thus improving the performance characteristics even more.
+
+Camel Quarkus is suitable not only for creating long living services and potentially short living serverless
+applications but also for
+[command-style applications](https://camel.apache.org/blog/2020/07/command-line-utility-with-camel-quarkus/)
+that execute some specific task (or wait for some specific condition) and exit.
+
+## Developer joy
+
+Writing integrations has never been more joyful for developers than with Camel Quarkus:
+
+* Easy to start with: either via [code.quarkus.io](https://code.quarkus.io/) or using `mvn quarkus:create`
+* The "live coding" feature, a.k.a. `mvn compile quarkus:dev` shortens your development iterations - check
+  [this 2 mins video](https://www.youtube.com/watch?v=4lXSf8DBQkQ)
+* Easy to test using JUnit 5 extensions
+* Hides the complexity of the native compilation using [GraalVM](https://www.graalvm.org/) or
+  [Mandrell](https://github.com/graalvm/mandrel)
+
+Check our https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html[User guide]!
+
+## Camel components coverage
+
+Since the [early beginnings](https://github.com/quarkusio/quarkus/tree/0.11.0/extensions/camel) the number of supported
+Camel bits went up substantially. As of Quarkus 1.0.0 and
+Camel 3.4, Camel Quarkus supports:
+
+* 155 out of 350 Camel components (44%)
+* 27 out of 43 Camel data formats (63%)
+* 13 out of 17 Camel languages (76%)
+* 17 out of 42 miscellaneous Camel components (40%)
+
+Some of these are supported in JVM mode only - please refer to the
+[complete list](https://camel.apache.org/camel-quarkus/latest/list-of-camel-quarkus-extensions.html) for details.
+
+## Bootstrapping methods
+
+There are two ways to bootstrap and configure Camel Quarkus:
+
+1. Bare
+2. With Camel Main
+
+Both methods configure and start a Camel Context for you. The main difference is in how much the resulting Camel Context
+obeys the conventions known from Camel on other platforms. If you like to configure your routes using
+`camel.component.*` properties, then you need to add the `camel-quarkus-main` dependency and the properties
+will work as usual on Camel standalone or Camel SpringBoot. Of course, this brings some overhead. You may prefer this
+option if you used Camel before or if you are migrating from other platform.
+
+If you rather come from the Quarkus side and you never wrote Camel integrations before, you may choose to use the bare

Review comment:
       > I would say from CDI side
   
   Good idea.
   
   > It reads as if it is two "big" alternatives, that you cannot use CDI with Camel Main, and vice versa.
   
   Good point, the text should not awake that impression.




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] zregvart commented on a change in pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
zregvart commented on a change in pull request #454:
URL: https://github.com/apache/camel-website/pull/454#discussion_r468196437



##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,77 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-07-07

Review comment:
       I usually take one from [unsplash](https://unsplash.com/s/photos/camel)




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] ppalaga commented on a change in pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
ppalaga commented on a change in pull request #454:
URL: https://github.com/apache/camel-website/pull/454#discussion_r469129773



##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,131 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-08-10
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+<sub><sup>Original image by <a href="https://commons.wikimedia.org/wiki/User:99of9">Toby Hudson</a> <a href="https://creativecommons.org/licenses/by-sa/3.0">CC BY-SA 3.0</a> via <a href="https://en.wikipedia.org/wiki/Camel_racing#/media/File:CamelRacingCamelCup2009Heat.JPG">Wikipedia</a></sup></sub>
+
+The Apache Camel community celebrates the release 1.0.0 of Camel Quarkus!
+
+## What is Camel Quarkus?
+
+Camel Quarkus brings the outstanding integration capabilities of Apache Camel to [Quarkus](https://quarkus.io/) - the
+toolkit for writing subatomically small and supersonically fast Java, Kotlin and Scala applications. In addition to
+memory consumption and start time improvements on stock JVMs, Quarkus also allows for compiling applications to
+[native executables](https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html#_package_and_run_the_application)
+thus improving the performance characteristics even more.
+
+Camel Quarkus is suitable not only for creating long living services and potentially short living serverless
+applications but also for
+[command-style applications](https://camel.apache.org/blog/2020/07/command-line-utility-with-camel-quarkus/)
+that execute some specific task (or wait for some specific condition) and exit.
+
+## Developer joy
+
+Writing integrations has never been more joyful for developers than with Camel Quarkus:
+
+* Easy to start with: either via [code.quarkus.io](https://code.quarkus.io/) or using `mvn quarkus:create`
+* The "live coding" feature, a.k.a. `mvn compile quarkus:dev` shortens your development iterations - check
+  [this 2 mins video](https://www.youtube.com/watch?v=4lXSf8DBQkQ)
+* Easy to test using JUnit 5 extensions
+* Hides the complexity of the native compilation using [GraalVM](https://www.graalvm.org/) or
+  [Mandrell](https://github.com/graalvm/mandrel)
+
+Check our https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html[User guide]!
+
+## Camel components coverage
+
+Since the [early beginnings](https://github.com/quarkusio/quarkus/tree/0.11.0/extensions/camel) the number of supported
+Camel bits went up substantially. As of Quarkus 1.0.0 and
+Camel 3.4, Camel Quarkus supports:
+
+* 155 out of 350 Camel components (44%)
+* 27 out of 43 Camel data formats (63%)
+* 13 out of 17 Camel languages (76%)
+* 17 out of 42 miscellaneous Camel components (40%)
+
+Some of these are supported in JVM mode only - please refer to the
+[complete list](https://camel.apache.org/camel-quarkus/latest/list-of-camel-quarkus-extensions.html) for details.
+
+## Bootstrapping methods
+
+There are two ways to bootstrap and configure Camel Quarkus:
+
+1. Bare
+2. With Camel Main
+
+Both methods configure and start a Camel Context for you. The main difference is in how much the resulting Camel Context
+obeys the conventions known from Camel on other platforms. If you like to configure your routes using
+`camel.component.*` properties, then you need to add the `camel-quarkus-main` dependency and the properties
+will work as usual on Camel standalone or Camel SpringBoot. Of course, this brings some overhead. You may prefer this
+option if you used Camel before or if you are migrating from other platform.
+
+If you rather come from the Quarkus side and you never wrote Camel integrations before, you may choose to use the bare
+bootstrap and configure your routes using CDI.
+
+See the [Bootstrap section](https://camel.apache.org/camel-quarkus/latest/user-guide/bootstrap.html) of the User guide
+for more details.
+
+## CDI
+
+CDI plays a central role in Quarkus and Camel Quarkus offers a first class support for it too. You may use `@Inject`,
+`@ConfigProperty` and other annotations e.g. to inject beans and configuration values to your Camel RouteBuilder's.
+See the [CDI section](https://camel.apache.org/camel-quarkus/latest/user-guide/cdi.html) of the User guide for more
+details.
+
+## Native mode
+
+As mentioned above, Quarkus brings the option to compile an application to native executable. Compared to running on
+JVM, native applications start faster, require less memory at runtime and are also smaller on disk.
+
+However, the native compilation with GraalVM is all but easy and straightforward. First, there are
+[limitations](https://github.com/oracle/graal/blob/master/substratevm/LIMITATIONS.md) for what your code and all your
+dependencies may or may not do. Second, the native compiler needs to be configured through many options that may

Review comment:
       Yeah, shorter is better.




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] ppalaga commented on a change in pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
ppalaga commented on a change in pull request #454:
URL: https://github.com/apache/camel-website/pull/454#discussion_r469127607



##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,131 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-08-10
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+<sub><sup>Original image by <a href="https://commons.wikimedia.org/wiki/User:99of9">Toby Hudson</a> <a href="https://creativecommons.org/licenses/by-sa/3.0">CC BY-SA 3.0</a> via <a href="https://en.wikipedia.org/wiki/Camel_racing#/media/File:CamelRacingCamelCup2009Heat.JPG">Wikipedia</a></sup></sub>
+
+The Apache Camel community celebrates the release 1.0.0 of Camel Quarkus!
+
+## What is Camel Quarkus?
+
+Camel Quarkus brings the outstanding integration capabilities of Apache Camel to [Quarkus](https://quarkus.io/) - the
+toolkit for writing subatomically small and supersonically fast Java, Kotlin and Scala applications. In addition to
+memory consumption and start time improvements on stock JVMs, Quarkus also allows for compiling applications to
+[native executables](https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html#_package_and_run_the_application)
+thus improving the performance characteristics even more.
+
+Camel Quarkus is suitable not only for creating long living services and potentially short living serverless
+applications but also for
+[command-style applications](https://camel.apache.org/blog/2020/07/command-line-utility-with-camel-quarkus/)
+that execute some specific task (or wait for some specific condition) and exit.
+
+## Developer joy
+
+Writing integrations has never been more joyful for developers than with Camel Quarkus:
+
+* Easy to start with: either via [code.quarkus.io](https://code.quarkus.io/) or using `mvn quarkus:create`
+* The "live coding" feature, a.k.a. `mvn compile quarkus:dev` shortens your development iterations - check
+  [this 2 mins video](https://www.youtube.com/watch?v=4lXSf8DBQkQ)
+* Easy to test using JUnit 5 extensions
+* Hides the complexity of the native compilation using [GraalVM](https://www.graalvm.org/) or
+  [Mandrell](https://github.com/graalvm/mandrel)
+
+Check our https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html[User guide]!
+
+## Camel components coverage
+
+Since the [early beginnings](https://github.com/quarkusio/quarkus/tree/0.11.0/extensions/camel) the number of supported
+Camel bits went up substantially. As of Quarkus 1.0.0 and
+Camel 3.4, Camel Quarkus supports:
+
+* 155 out of 350 Camel components (44%)
+* 27 out of 43 Camel data formats (63%)
+* 13 out of 17 Camel languages (76%)
+* 17 out of 42 miscellaneous Camel components (40%)
+
+Some of these are supported in JVM mode only - please refer to the
+[complete list](https://camel.apache.org/camel-quarkus/latest/list-of-camel-quarkus-extensions.html) for details.
+
+## Bootstrapping methods
+
+There are two ways to bootstrap and configure Camel Quarkus:
+
+1. Bare
+2. With Camel Main
+
+Both methods configure and start a Camel Context for you. The main difference is in how much the resulting Camel Context
+obeys the conventions known from Camel on other platforms. If you like to configure your routes using
+`camel.component.*` properties, then you need to add the `camel-quarkus-main` dependency and the properties
+will work as usual on Camel standalone or Camel SpringBoot. Of course, this brings some overhead. You may prefer this

Review comment:
       The additional dependency brings both build time and runtime overhead. That's true for almost any dependency and that's why I said 'of course'. I admit I do not have any exact data and I admit the overhead might be negligible for basic applications. IIRC, less overhead was one of the motivations for not including main by default. I fully second the UX argument, and based on that, I was rather opposing not including main by default. It is definitely good that we discuss how to present this option. Let me think how to formulate it better.




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] lburgazzoli commented on a change in pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
lburgazzoli commented on a change in pull request #454:
URL: https://github.com/apache/camel-website/pull/454#discussion_r469134043



##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,131 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-08-10
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+<sub><sup>Original image by <a href="https://commons.wikimedia.org/wiki/User:99of9">Toby Hudson</a> <a href="https://creativecommons.org/licenses/by-sa/3.0">CC BY-SA 3.0</a> via <a href="https://en.wikipedia.org/wiki/Camel_racing#/media/File:CamelRacingCamelCup2009Heat.JPG">Wikipedia</a></sup></sub>
+
+The Apache Camel community celebrates the release 1.0.0 of Camel Quarkus!
+
+## What is Camel Quarkus?
+
+Camel Quarkus brings the outstanding integration capabilities of Apache Camel to [Quarkus](https://quarkus.io/) - the
+toolkit for writing subatomically small and supersonically fast Java, Kotlin and Scala applications. In addition to
+memory consumption and start time improvements on stock JVMs, Quarkus also allows for compiling applications to
+[native executables](https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html#_package_and_run_the_application)
+thus improving the performance characteristics even more.
+
+Camel Quarkus is suitable not only for creating long living services and potentially short living serverless
+applications but also for
+[command-style applications](https://camel.apache.org/blog/2020/07/command-line-utility-with-camel-quarkus/)
+that execute some specific task (or wait for some specific condition) and exit.
+
+## Developer joy
+
+Writing integrations has never been more joyful for developers than with Camel Quarkus:
+
+* Easy to start with: either via [code.quarkus.io](https://code.quarkus.io/) or using `mvn quarkus:create`
+* The "live coding" feature, a.k.a. `mvn compile quarkus:dev` shortens your development iterations - check
+  [this 2 mins video](https://www.youtube.com/watch?v=4lXSf8DBQkQ)
+* Easy to test using JUnit 5 extensions
+* Hides the complexity of the native compilation using [GraalVM](https://www.graalvm.org/) or
+  [Mandrell](https://github.com/graalvm/mandrel)
+
+Check our https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html[User guide]!
+
+## Camel components coverage
+
+Since the [early beginnings](https://github.com/quarkusio/quarkus/tree/0.11.0/extensions/camel) the number of supported
+Camel bits went up substantially. As of Quarkus 1.0.0 and
+Camel 3.4, Camel Quarkus supports:
+
+* 155 out of 350 Camel components (44%)
+* 27 out of 43 Camel data formats (63%)
+* 13 out of 17 Camel languages (76%)
+* 17 out of 42 miscellaneous Camel components (40%)
+
+Some of these are supported in JVM mode only - please refer to the
+[complete list](https://camel.apache.org/camel-quarkus/latest/list-of-camel-quarkus-extensions.html) for details.
+
+## Bootstrapping methods
+
+There are two ways to bootstrap and configure Camel Quarkus:
+
+1. Bare
+2. With Camel Main
+
+Both methods configure and start a Camel Context for you. The main difference is in how much the resulting Camel Context
+obeys the conventions known from Camel on other platforms. If you like to configure your routes using
+`camel.component.*` properties, then you need to add the `camel-quarkus-main` dependency and the properties
+will work as usual on Camel standalone or Camel SpringBoot. Of course, this brings some overhead. You may prefer this

Review comment:
       I think this just boils down how you want to use camel-quarkus: as a library or as an application runtime.
   
   IMHO, camel-quarkus-core is for embedding camel functionalities with full control whereas camel-quarkus-main is mainly for application
   




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [camel-website] ppalaga commented on a change in pull request #454: Blog post: Camel Quarkus 1.0.0

Posted by GitBox <gi...@apache.org>.
ppalaga commented on a change in pull request #454:
URL: https://github.com/apache/camel-website/pull/454#discussion_r468438853



##########
File path: content/blog/2020/08/camel-quarkus-release-1.0.0/index.md
##########
@@ -0,0 +1,77 @@
+---
+title: "Camel Quarkus 1.0.0 Released"
+date: 2020-07-07
+authors: ["ppalaga"]
+categories: ["Releases", "Camel Quarkus"]
+preview: What's new in Camel Quarkus 1.0.0
+---
+
+Apache Camel community celebrates the release 1.0.0 of Camel Quarkus!
+
+## What is Camel Quarkus?
+
+Camel Quarkus brings the outstanding integration capabilities of Apache Camel to [Quarkus](https://quarkus.io/) - the
+toolkit for writing subatomically small and supersonically fast Java, Kotlin and Scala applications.
+
+It is suitable not only for creating long living services and potentially short living serverless applications
+but also for [command-style applications](https://camel.apache.org/blog/2020/07/command-line-utility-with-camel-quarkus/)
+that execute some task and exit.
+
+## Developer joy
+
+Writing integrations has never offered more developer joy than with Camel Quarkus:
+
+* Easy to start with: either via [code.quarkus.io](https://code.quarkus.io/) or using `mvn quarkus:create`
+* The "live coding" feature, a.k.a. `mvn compile quarkus:dev` shortens your development iterations
+* Easy to test using JUnit 5 extensions
+* Shields from the complexity of the native compilation using [GraalVM](https://www.graalvm.org/) or

Review comment:
       Thanks!




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org