Hi ES team, ATM there is no proper architecture and guidance about how to distribute ES Store and ES Publisher components separately, as we are in middle of G-Reg GC and API-M 2.0 works it's better to look into this now so that we have enough time to discuss and finalize the architecture before the G-Reg GA release.
According to my understanding followings need to be happen. - Create 2 carbon profiles as "store", "publisher" in ES and product that embed ES ( G-Reg, API-M). - Share Registry DB. - Share social DB Anything else or any concern ? Also we need to consider the fact that Store will be deployed in DMZ in some use cases. Thanks ! -- Sagara Gunathunga Architect; WSO2, Inc.; http://wso2.com V.P Apache Web Services; http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
