A UI is a really nice idea!
We're making progress with the `kamel` command line helper that allows
publishing files containing Camel routes in multiple supported languages, and
will allow soon to have instant redeploys (#34).
But for what concerns the future plans we had already in mind that crazy idea
of creating a web-based mini-IDE, where you can write (code) your routes, have
auto-completion through a backend language server, customize the integration
details (e.g. components, configuration properties, passwords), and run them,
with a immediate feedback on the UI through a log window.
With something like that in place, devs could iterate on integrations quickly:
change the code -> save -> instant redeploy.
This is what we have in mind now :)
Monitoring is the hardest part IMO. That's because currently we have a
`Deployment` per integration that is always active, but later on we will drop
this behavior to add the "scale to 0 feature". A simple example is a route like
`from("timer:job?period=1h").to("...")` that will be probably materialized as a
`CronJob`. This means there'll not be always a JVM with Jolokia to ask
information to.
I guess exporting metrics and tracing info will be the way, but I've not gone
into details at the moment.
Wdyt?
[ Full content available at: https://github.com/apache/camel-k/issues/77 ]
This message was relayed via gitbox.apache.org for [email protected]
