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

Jump to bottom

Multi tenancy architecture #15073

Closed
brunowego opened this issue Oct 29, 2019 · 3 comments
Closed

Multi tenancy architecture #15073

brunowego opened this issue Oct 29, 2019 · 3 comments
Labels
c: Documentation For issues related to in-app product help messages, or to the Matomo knowledge base. not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org.

Comments

@brunowego
Copy link
Contributor

brunowego commented Oct 29, 2019 •
edited

I'm working for Banco do Brasil, and here we have billions of access every month. We decide separate each product to collect in a dedicated Matomo.

After months working with Matomo (piwik), I really appreciate the platform and I love the architecture that this are builded.

So, already passed through the thought of separating each site into a separate database as a multi-tenant architecture? That makes sense? Thanks.
@mattab
Copy link
Member

mattab commented Oct 30, 2019

Hi @brunowego, we usually recommend that one Matomo instance tracks 500M pageviews or 1 billion actions per month. We haven't (yet) had opportunity to test on more than 500m-1billion range. Most features actually work well. Above 500m/1billion it is usually recommended to add all other sites to a separate new Matomo instance (or multiple). Because it's easy to create a new instance (there is an un-documented system using named config files), we're not planning multi-tenant architecture, but may do it later (probably a UI to connect all the different Matomo servers, and make it easy to view sites/users across instances)

How many pageviews and total actions are you currently tracking per month in your Matomo? and how many do you track more in the next 12 months?

@mattab mattab added the c: Documentation For issues related to in-app product help messages, or to the Matomo knowledge base. label Jan 21, 2020
@mattab
Copy link
Member

mattab commented Jan 21, 2020 •
edited

Any update @brunowego on your multi tenancy tests? happy to help, feel free to contact us at https://matomo.org/contact/

@brunowego
Copy link
Contributor Author

Hi @mattab, sorry for the delay. So, for this moment we decide for other alternative. We are a small team. I will close this, in future we open again. Thanks!

@mattab mattab added the not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org. label Jan 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c: Documentation For issues related to in-app product help messages, or to the Matomo knowledge base. not-in-changelog For issues or pull requests that should not be included in our release changelog on matomo.org.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@brunowego @mattab