16:56 <HZ> hi there, may I ask if we have an estimate on support for python 3?

19:44 <SeanTAllen> HZ: Hi. We don't have immediate Python 3 plans right now. Probably sometime before the end of the year. Most likely the latter half, but if we had a commercial client who was interested in Python 3, that would move it up in terms of priority. Its definitely something we plan on doing.

20:02 <HZ> thanks, was there any reason we picked python2 initially instead of python3?

20:03 <HZ> I mean any particular technical reason?

20:06 <HZ> also - neither Pony / Java is part of my current stack, what is the main thing (or maybe just 1 thing) I should consider Wallaroo instead of Flink apart from Wallaroo will have better commercial support?

21:42 <SeanTAllen> there's no technical reason HZ. we needed to start somewhere and the folks were were working with were using 2.7.

21:42 <SeanTAllen> supporting Python 3 should be relatively easy outside of the added maintenance overhead for documentation, testing etc (which is non-trivial).

21:43 <SeanTAllen> HZ: what sort of problems are you trying to solve? what do your use cases look like?

22:56 <HZ> I have large number of weather variables (forecast and measures) continuous inputs from various source - at the moment all of them are dump into sql sever but the database is being the major bottleneck (that prevent me to take more variables), so I am thinking of rebuild it with a framework that is more saleable but at the same time not too much more difficult than what I have now :)

22:59 <SeanTAllen> HZ: i assume you prefer to work in Python?

22:59 <SeanTAllen> is your current code in Python 3?

23:00 <HZ> yeah - everything I have at the moment is python 3. but python 2.7 should be OK as I have used 2.7 for a long time, but just I have switched to 3 recently

23:01 <HZ> so hoping not to maintain another set of "legacy new code" :)

23:01 <HZ> I found wallaroo quite similar to Flink in terms of functionalities?

23:02 <HZ> or there is some distinction that I should be aware of?

23:02 <SeanTAllen> Flink has been around for longer, so its more advanced on many fronts, for example windowing. However, we plan on catching up.

23:03 <SeanTAllen> Our goal is to make running large scale data applications as easy as writing a python script. I think that means that long term we are a better option for Python users.

23:03 <SeanTAllen> I find the ergonomics of writing Python API nicer with Wallaroo than Flink BUT... I am obviously biased.

23:03 <SeanTAllen> The Walaroo python API is very small, my suggestion is give it a try. Worst case scenario, you can easily move the code to another system.

23:04 <SeanTAllen> Its very easy to keep your code independent of Wallaroo.

23:05 <HZ> I dont actually worry about lacking fancy features as long as the core one is working well - I assume Wallaroo is prod-ready ?

23:06 <SeanTAllen> Everyone has a different definition of prod-ready, we have 2 customers who are working on going to production within the next 6 weeks.

23:06 <SeanTAllen> A startup's idea of prod-ready is going to be different than a large bank for example.

23:06 <SeanTAllen> I'm not dodging the question, I just want to give a realistic answer.

23:07 <SeanTAllen> I don't know what prod-ready means to you.

23:08 <SeanTAllen> Wallaroo under testing and various POC has handled billions and billions of messages across a variety of applications exercising a variety of code paths.

23:08 <SeanTAllen> What does prod-ready mean to you HZ?

23:08 <HZ> indeed - I think if there is already company running this on a prod-environment, then it means prod-ready to me

23:09 <SeanTAllen> there isnt right now, there will be soon.

23:09 <SeanTAllen> actually let me correct that, someone might be. we aren't aware of any. but know of 2 that we are working with that will be soon.

23:12 <SeanTAllen> And we are here to help you succeed HZ.

23:13 <HZ> @SeanTAllen I know it sounds crazy, but it make people feel safer if we see other company has started using it on prod (i.e. there is more comprehensive "test" done )

23:13 <HZ> @SeanTallen I know you might not be very familiar with Flink inside out, but from what I read, Wallaroo is supposed to be more performant than Flink ?

23:15 <HZ> @SeanTAllen may I ask what kind of size the two companies you are working with ?

23:40 <SeanTAllen> HZ: social proof makes sense to me

23:41 <SeanTAllen> HZ: both are small startups that are getting ready to go to prod. We are working with some larger companies as well but they have a longer time.