I want to open a discussion around adding Apache Knox to our architecture. I believe there are some benefits it offers in a couple different areas:
1. It provides a proxy to endpoints for commonly used Hadoop-ecosystem components that we use. This would simplify our web architecture by allowing clients to communicate with a single gateway. 2. We could delegate many of our security needs to Knox, making our REST application smaller and easier to maintain. 3. Knox offers an SSO solution that would benefit Metron Does anyone agree that adding Apache Knox makes sense? Are there other alternatives we should consider? If we do decide it is a good idea, I can see a couple features that could be added shortly after. It would be nice to add our REST application as a service in Knox, allowing our UIs to communicate with a single endpoint. It would also be nice to put an SSO strategy in place and simplify authentication in our UIs. Thoughts?
