wp-mail-logging
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114broken-link-checker
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114health-check
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114updraftplus
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114wp-extended-search
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114rocket
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114For some time now, the French national research and education network (NREN) RENATER<\/a> is testing Nextcloud. Together with our team they have deployed it in testing for over 40 organizations already.<\/p>\n Those organizations who would like to provide this to their employees and students will be able to use the service from RENATER. You can read our press release announcement here.<\/a><\/p>\n While Nextcloud has of course signed hundreds of customers this year, including the French Ministry of Interior, RENATER is special because their Nextcloud Global Scale deployment would be the first in the world to connect a single on-premises cloud instance to the identity providers (IDP’s) of hundreds of organizations.<\/p>\n Our mission at RENATER is enabling seamless collaboration between over a thousand research and education institutions in France in order to protect the security and confidentiality of data. We study and experiment deeply Nextcloud Global Scale for its highly scalability capacities and its reliability that fit the needs of our project.<\/p><\/blockquote>\n — Alexandre Salvat, Drive Project Manager – P\u00f4le Projets Transverses et Innovation (P2TI)<\/p>\n Let’s step back for a second, what are Global Scale and how does it fit with identity providers?<\/p>\n In late 2016, Nextcloud recognized that, to deliver the most scalable solution in the file sync and share world, work was needed on the ‘top end’ of the scale. Nextcloud runs on Raspberry Pi devices up to large clusters at universities and companies. The largest Nextcloud cluster node has 250.000 users on a single instance – but this customer already has far more users, delivering file sync and collaboration to tens of millions of users across several continents today! This single installation, thus, is part of a larger architecture we devised for the multi-million-user scale: Global Scale.<\/a><\/p>\n Global Scale removes the major limitations a Nextcloud instance has at large scale: database and storage. As a PHP application, Nextcloud handles each ‘request’ to the server as an independent process, scaling essentially without limitations: if you need to handle twice the number of users logging in simultaneously, you just double your processing power by adding, for example, a second server. Double again? Go to four, ten, how many you need.<\/p>\n However, each of these Nextcloud application servers will have to talk to the same database and storage, and that is where the problems begin. At large scale, these become expensive, as scaling databases and storage isn’t anywhere near as easy as scaling Nextcloud. At even larger scale, even a data center can become a limitation: the connection to the internet backbone can only handle so much, after all!<\/p>\n Global Scale solves these issues in an elegant way by distributing users and data over separate, independent Nextcloud nodes. These are then ‘wired together’ with a number of mediating services, to facilitate authentication, sharing and more. The benefits go beyond scalability: it can also allow you to keep data closer to users to improve performance or keep data in specific countries to comply with local regulations.<\/p>\n Watch this youtube video to get a graphical overview of how Global Scale works.Global Scale and identity providers<\/h2>\n
Global Scale<\/h3>\n
limits to scalability: database, storage, data center!<\/h3>\n
\n