titanoboa

Thanks for the kind words! Yes, I would still be careful with passwords in the public beta. It goes via SSL and you get a unique UUID URL so all-in-all it is kinda secured (plus time-to-live of the instance is only 3 hours which limits any time to hack it) but still this is not 100% secure and I would not recommend it for any kind of production use (including any use of passwords you dont want exposed). The free instances are not (yet) password protected (other then the UUID) - this on the other hand is useful if you want to share the envrionment with somebody, just send them the link... This is just a beginning of the public hosting so I will need to think through further improvements that would go into the hosting, security-wise and other aspects as well. My main objective at this stage for the free hosted instances was to give people

This is a very good point. My current line of thinking is: A workflow is a workflow is a workflow. Titanoboa is built the way that pretty much everything it shuffles is data - and either it can be big (Airflow) or the steps can have side effects (iPaaS/Zapier). The "no code" is achievable since adding more predefined steps is not that hard (there's not that many at the moment though) - see for instance https://github.com/mikub/titanoboa/wiki/Getting-Started-with... - you dont code, you just fill in properties, so it is very straightforward, pretty much like Zappier. My aim in the iPaaS space is more at the enterprise level, where the predefined steps won't do anymore and you have to custom develop them anyway - so in that are I think Titanoboa shines since you really can rapidly prototype steps on the fly, a bit like Repl.it and Zapier to

You can check out https://github.com/mikub/titanoboa-tasklets And also https://github.com/mikub/titanoboa-sample-workflows There are few blog posts I wrote about some sample workflows, e.g.: https://github.com/mikub/titanoboa/wiki/Getting-Started-with... https://www.titanoboa.io/using-titanoboa-for-it-automation.h... https://www.titanoboa.io/using-titanoboa-for-cloud-integrati... https://www.titanoboa.io/java-repl.html

Hi HN peeps! I single-handedly built Titanoboa (a workflow automation for JVM) and now I am experimenting with hosting dockerized Titanoboa instances - so I built a free hosting service. If you want to play with Titanoboa in your browser without installing anything, give it a try. Feel free to check out Titanoboa on Github: https://github.com/mikub/titanoboa Also: This is an early beta so please do let me know if something breaks or you spot a bug. Atm I have load-balancers set up only on West coast and in Europe, so apologies to folks from down under & similar locations, let me know if it's too laggy :)

Hi HN peeps! I single-handedly built Titanoboa (a workflow automation for JVM) and now I am just experimenting with hosting dockerized Titanoboa instances - so if you want to play with Titanoboa in your browser without installing anything, give it a try. Feel free to check out Titanoboa on Github: https://github.com/mikub/titanoboa Also: This is an early beta so please do let me know if something breaks or you spot a bug. Atm I have load-balancers set up only on West coast and in Europe, so apologies to folks from down under & similar locations, let me know if it's too laggy :)

Looks really nice! Looking forward to playing with it a bit. Shameless plug: I built something similar as a part of my workflow platform for JVM (for Java and Clojure): https://github.com/mikub/titanoboa The main focus of my tool is enterprise integration and data processing, but I still love to play and experiment with the ideas of developing code directly in browser and how to visualize its execution flow. So I built a live coding / visualization also as a part of my tool. This becomes non-trivial if you apply it to languages other then js (so browser integration becomes a bit harder). I also think the main challenge here is the server-side part of things, especially when you make such solution distributed - i.e. how you achieve high availability and assure everything gets executed (at least) once even in case of failover, how you cate

This may be of interest: https://github.com/mikub/titanoboa