You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "John Omernik (JIRA)" <ji...@apache.org> on 2016/04/16 02:32:25 UTC

[jira] [Commented] (METRON-105) Define architecture for multi tenancy

    [ https://issues.apache.org/jira/browse/METRON-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15243899#comment-15243899 ] 

John Omernik commented on METRON-105:
-------------------------------------

This is a very interesting discussion, as a security practitioner, having a quick flexible platform to work with security is critical.  Metron has a lot of promise to be "fast fail" in that an architecture where things can be extremely modular is preferred, especially in the security space.  

Having worked on similar architectures, and knowing that the primary users of a security architecture are not data architects, but security practitioners, giving though to the users of such a platform is very important. How will users interact and share the architecture? Do they need to be "big data" experts in order to bring something new to the platform? Etc.  Lots of questions, I look forward to more conversations around this. 

John

> Define architecture for multi tenancy 
> --------------------------------------
>
>                 Key: METRON-105
>                 URL: https://issues.apache.org/jira/browse/METRON-105
>             Project: Metron
>          Issue Type: Bug
>            Reporter: James Sirota
>
> Work with the Metron community to define the architecture for multitenancy  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)