Hi Willem,
well I am working in the automation Industry for quite a few yers now.
Unfortunately they don’t seem to understand the concept of buying services, but
more buying products.
So, I’ve been seeing everywhere, that the folks in the automation industry are
using so-called Historians, whic
I used to address the camel performance issue 6 years ago, which led
me to find a use case for collecting millions of performance data as a
SaaS service.
In that case, camel leverages Kafka to persist received messages. I
don't think the in-memory queue could address the problem.
@ Chris, Can you
+1 (binding)
Thanks Zineb!
On Fri, Dec 9, 2022 at 9:41 AM Alexandre Gallice
wrote:
> +1 (binding)
>
> Thanks for cutting the release Zineb :)
> Alex
>
> On Fri, Dec 9, 2022 at 6:04 AM Jean-Baptiste Onofré
> wrote:
>
> > +1 (binding)
> >
> > Regards
> > JB
> >
> > On Thu, Dec 8, 2022 at 8:05 PM
Hi,
I'm wondering if it wouldn't be better to position the 3.20 LTS release
along with JDK 17 as a better stopgap for them ... What do you think?
The JDK 17 is such a great release with so many interesting features. I am
afraid that by still focusing on JDK 11 with Camel 4 we may limit ourselves
+1 (binding)
Thanks for cutting the release Zineb :)
Alex
On Fri, Dec 9, 2022 at 6:04 AM Jean-Baptiste Onofré wrote:
> +1 (binding)
>
> Regards
> JB
>
> On Thu, Dec 8, 2022 at 8:05 PM Zineb Bendhiba
> wrote:
> >
> > Hello,
> >
> > This is a vote to release Apache Camel Quarkus 2.15.0.
> >
> >
