Hi Zheng, We’re currently discussing multiple scenarios. In the “all in one” if would definitely make sense to do that and to improve the Camel PLC4X component while at it.
In general, we’re thinking of an application, that starts an IoTDB server embedded as well as something that pumps data into it and some sort of API frontend with which industry solutions can communicate with. But it’s not even decided IF we use Camel … just wanted to ask you folks here, if you think it’s a good idea and if it’s a good idea, if anyone wants to join in 😉 Chris From: Zheng Feng <[email protected]> Date: Wednesday, 7. December 2022 at 14:31 To: [email protected] <[email protected]> Subject: Re: Using Camel as backend in a new Apache "spinoff" project? It looks interesting and will it run a camel router with PLC4X component as an agent of IoTDB to collect data and send them directly to a server? On Wed, Dec 7, 2022 at 8:59 PM Christofer Dutz <[email protected]> wrote: > Hi, > > we’re currently discussing potentially using Apache Camel for building a > product based on Apache PLC4X, Apache IoTDB to build a Historian solution > for industrial use-cases. > We’re planning on making this less a framework, but more a product, based > on open-source frameworks and as soon as we have something, to bring it > back into Apache as a new project. > > Now I brought up the Idea of using Apache Camel as the communication layer > between all. > > I am admittedly a bit hesitant to introduce Kafka into the game as we aim > at building something we can run as installable product, adding Kafka would > complicate this, so I’d be happy to use something like Camel for this > usecase. > > What are your thoughts on this? How do camel routes perform when we’re > talking hundreds of thousands to millions of events a minute? > > And … anyone interested into joining this initiative? If yes, please ping > me off-list and I’ll add you. > > > Chris > > >
