(Documentation) Roadmap

[charleswhchan]

I see the there are 1.x and 2.x branches under SCM.

Is it possible to document a roadmap or list of features in upcoming version?

Thanks.

[schrepfler]

Or a blog post.

[mhawthorne]

We are still getting our heads around what the full feature set will be for Zuul 2.x, particularly in terms of API changes.

Once we have something more concrete we will make it public. Whatever the migration path is from 1.x to 2.x, we will be going through the same process internally at Netflix - so we should be able to provide useful guidance.

[aivans]

Do you intend to support websockets?

Thanks

[mhawthorne]

@aivans The plan is for Zuul 2 to be backed by RxNetty for both incoming and outgoing traffic. So if RxNetty supports it, Zuul will support it also.

Relevant to RxNetty and Websockets:
ReactiveX/RxNetty#125

[aivans]

Sounds good.

We will start our API Gateway implementation based on Zuul 1.x.

[schrepfler]

OMG, I was investigating it for that purpose as well! Cool!
Any time frames? Is the 2.x branch in any way usable or should we wait? Will it be easy to migrate? Will it be possible to use Scala as well?

[mhawthorne]

@schrepfler can't give a time frame yet, other than "work has started". I would suggest staying away from the 2.x branch for awhile as many things are likely to change.

The pain of migration will depend on how many filters you have and what they are doing. If you are doing a lot of IO in your filters, then switching from BIO to NIO isn't straightforward. I expect some of the Filter APIs to change but can't give specifics yet.

I believe you can use Scala even in Zuul 1.x if you register your own DynamicCodeCompiler. But I have only ever tested Groovy and Java filters.

[pataprogramming]

It looks like there's been a fair amount of activity in the 2.x branch in the last two months. Would anyone on the Zuul team be able to provide some roadmap estimates at this point? Is the codebase nearing the point where it could be considered for production use, or is the recommendation still to hold off?

Thanks for all the work on this. We have found 1.x (which we're currently running in production) very useful.

[NiteshKant]

@pataprogramming We are currently testing Zuull 2.x inside Netflix. 2.x also depends on 0.5.x of RxNetty which itself is in a snapshot state (Zuul is part of the process of stabilizing RxNetty).

Hopefully, we should be able to release a candidate for 2.x by January end.

[schrepfler]

Fingers crossed!

[tunesmith]

There were hopes of a release candidate for Zuul 2 by end of January - it's six months later now and it doesn't look like there is a lot of activity on the 2.x branch. Is this work still in progress or has it been lowered in priority? Has the move to Falcor de-emphasized Zuul work? Thanks for any insight, we have been investigating Zuul as a possible option internally.

[kakawait]

Same as @tunesmith any news about possible RC?

[andrejvanderzee]

It looks like the RCs for 2.x and 3x are abandoned. Is it fair to say that Zuul is not actively maintained / developed anymore by Netflix?

[carl-mastrangelo]

Hi,

Zuul is actively maintained, but the focus is mainly on internal use-cases at the moment. I will add documentation as I am able, but I don't think we have a goal at the moment to do a full documentation sprint. I am going to close out this issue since I don't think there is more to do here; please file an issue for specific questions about documentation.