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

[GitBox]

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:
us...@infra.apache.org