Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question about evolution of the nicobar. #45

Open
mhawrylczak opened this issue Oct 13, 2015 · 1 comment
Open

Question about evolution of the nicobar. #45

mhawrylczak opened this issue Oct 13, 2015 · 1 comment

Comments

@mhawrylczak
Copy link

Could you share with me (with us) the roadmap of the nicobar platform,
I wonder if you plan to upgrade to Hystrix > 1.4 and use HystrixObservableCommand,
or if you plan to use java 9 jigsaw for loading modules.
Do you, in Netflix, still use Nicobar in this form or the platform evolved but it is not published yet?

@vasanth-asokan
Copy link
Contributor

We still use Nicobar in its current form, but have no significant planned changes. We have another generic project, called Primer, that takes on the definition of module projects, and specifying inter module dependencies. It takes to the next level orchestration of module persistence, discovery and runtime module graph setup. The plan is to open source Primer very soon.

Nicobar was primarily used by the API platform and we are headed more towards a process isolated platform, rather than classloader isolation. That said, a classloader based module loader system like Nicobar is still relevant to many other application tiers. We did plan on seeing how to use Jigsaw when it is ready.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants