#multi-tenancy

[learnerscript]

Moodle Multi-Tenancy Course Profile Reporting | LearnerScript IOMAD Course Profile Report

[lmspulse]

LMS Multitenancy Guide — Why You Might Want It, And Best-Of-Breed Solutions

LMS Multitenancy (or is it "Multi Tenancy"?) Guide — Why You Might Want It, And Best-Of-Breed Solutions

On its surface, multitenancy or “multi tenancy” is the ability to manage several instances (ehm, “Tenants”) of a system from a central place. In LMS terms, the multitenancy puzzle has 3 pieces:

One host and between 2 and infinite tenants. Each tenant has their own set of learners, content and unique visual identities.

A shared pool of resources. From pieces of content —think single videos,…

View On WordPress

[odnenbo-blog]

Multi-tenancy

Multi-tenancy is an architecture in which a single instance of a software application serves multiple customers. Each customer is called a tenant. Tenants may be given the ability to customize some parts of the application, such as color of the user interface (UI) or business rules, but they cannot customize the application's code.

Multi-tenancy can be economical because software development and maintenance costs are shared. It can be contrasted with single-tenancy, an architecture in which each customer has their own software instance and may be given access to code. With a multi-tenancy architecture, the provider only has to make updates once. With a single-tenancy architecture, the provider has to touch multiple instances of the software in order to make updates.

In cloud computing, the meaning of multi-tenancy architecture has broadened because of new service models that take advantage of virtualization and remote access. A software-as-a-service (SaaS) provider, for example, can run one instance of its application on one instance of a database and provide web access to multiple customers. In such a scenario, each tenant's data is isolated and remains invisible to other tenants.

http://whatis.techtarget.com/definition/multi-tenancy

Multitenancy is a reference to the mode of operation of software where multiple independent instances of one or multiple applications operate in a shared environment. The instances (tenants) are logically isolated, but physically integrated. The degree of logical isolation must be complete, but the degree of physical integration will vary. The more physical integration, the harder it is to preserve the logical isolation. The tenants (application instances) can be representations of organizations that obtained access to the multitenant application (this is the scenario of an ISV offering services of an application to multiple customer organizations). The tenants may also be multiple applications competing for shared underlying resources (this is the scenario of a private or public cloud where multiple applications are offered in a common cloud environment).

http://www.gartner.com/it-glossary/multitenancy

The term "software multitenancy" refers to a software architecture in which a single instance of software runs on a server and serves multiple tenants. A tenant is a group of users who share a common access with specific privileges to the software instance. With a multitenant architecture, a software application is designed to provide every tenant a dedicated share of the instance - including its data, configuration, user management, tenant individual functionality and non-functional properties. Multitenancy contrasts with multi-instance architectures, where separate software instances operate on behalf of different tenants.

Krebs, Rouven (2012). "Architectural Concerns in Multi-tenant SaaS Applications" (PDF). Proceedings of the 2nd International Conference on Cloud Computing and Services Science (CLOSER 2012). Conference on Cloud Computing and Services Science. SciTePress.

https://en.wikipedia.org/wiki/Multitenancy

Multi-tenancy is a situation in which many different users access the same system and the system architecture is defined to allow the efficient sharing of system resources. However, it must appear to each user that they have the sole use of the system. Multi-tenancy involves designing the system so that there is an absolute separation between the system functionality and the system data. You should, therefore, design the system so that all operations are stateless. Data should either be provided by the client or should be available in a storage system or database that can be accessed from any system instance. Relational databases are not ideal for providing multi-tenancy and large service providers, such as Google, have implemented a simpler database for user data. A particular problem in multi-tenant systems is data management. The simplest way to provide data management is for each customer to have their own database, which they may use and configure as they wish. However, this requires the service provider to maintain many different database instances (one per customer) and to make these available on demand. This is inefficient in terms of server capacity and increases the overall cost of the service. As an alternative, the service provider can use a single database with different users being virtually isolated within that database

Sommerville, I. (2011). Software Engineering 9.

[mkassas-world]

Sorry, you don't have a licence to use Project Web App In Multi-Tenant Project Server

Sorry, you don’t have a licence to use Project Web App In Multi-Tenant Project Server

I am working on Multi-Tenant Project Server environment,I tried to provision a new PWA Site that has been provisioned successfully,but unfortunately When I tried to browse the PWA site I got the following error,

Sorry, you don't have a licence to use Project Web App

Cause: (more…)

View On WordPress

[turingwithgeorge-blog]

Turing 061 - Right Back To It!

Our first day back from break and its like the ball never stopped rolling. We are immediately immersed in our next project, The Pivot. In The Pivot, we are gifted with “legacy code” from one of the group members’ Little Shop repositories and add multi-tenancy aspects to it. 

My team members for this will be Chris Cenatiempo, and David Stinette. 

We inherited David and his Little Shop team’s code. It was an app about drone food delivery. We also got first pick for how we wanted to “pivot” the app and chose to make it serve multiple local farmers markets. 

David and I peer pressured Chris into being our team lead. When he said he wasn’t sure he was comfortable in that role, we quote Jeff Casimir at him, “If you feel uncomfortable, then you definitely should be doing it!” It’s better to practice here in a relatively safe place. 

We started with a talk about project expectations. We all wanted to focus on TDD (per usual). Chris would not accept the “if you are uncomfortable...” speech again and asked to stay away from front end as much as possible. David wanted to try his hand at DevOps and I offered to provide help if he had any difficulties. I didn’t have any specific goals for the project besides making sure we take it slow enough so everyone learns what they need to for the project. 

We were given the rest of the day to start planning out our app, Fast-Flying-Farm-Fresh-Food!  

[mscoders-madrid]

Mesa redonda sobre Multi-tenancy

¡Hola a todos!.

En esta ocasión vamos a hacer una mesa redonda diferente, ya que vamos a tratar un tema que nunca antes lo habíamos tratado, arquitecturas multi-tenancy en proyectos reales.

Para ello, vamos a contar con la inestimable ayuda de Enrique Blanco Sanz (@enriquin).

En esta mesa redonda debatiremos y hablaremos sobre aplicaciones Multi-tenancy, desde como diseñar la base de datos, gestionar múltiples configuraciones, formularios personalizables, jerarquía tenants, personalizaciones por cliente, cloud, escalabilidad... todo ello desde un punto de vista práctico.

Tanto si tienes experiencia como sino en el desarrollo de aplicaciones Multi-tenancy acércate y pasaremos un buen rato juntos compartiendo conocimientos y haciendo networking.

¡No os olvidéis registraros en el enlace que indicamos más abajo!.

Fecha: Jueves 19 de Febrero de 2015

Hora: de 19:00 horas a 21:00 horas.

Lugar:

Microsoft Ibérica

Sala Severo Ochoa

Centro Empresarial La Finca - Paseo del Club Deportivo, 1

Pozuelo de Alarcón 28223 España

Enlace al registro

¡Os esperamos!

[allerint]

Check out How to approach Multi-tenancy in Rails by Allerin

[diegoalvareznogueira]

Utilizando cache em apps multi-tenancy

Recentemente tive um problema ao utilizar cache em uma aplicação multi-tenancy. Como teria uma aplicação com vários banco de dados, precisaria também dividir meus caches, para não misturar informações de clientes.

Estou utilizando a gem apartment, o qual me disponibiliza um método Apartment::Database.current_database, para capturar o nome da database levando em conta o cliente atual ( domínio ).

Após várias tentativas, consegui fazer funcionar sobrescrevendo o método responsável pelo namespace.

Cache default do rails:

# config/initializers/multi_tenancy_cache.rb module ActiveSupport module Cache class Store def options @options.merge(namespace: Apartment::Database.current_database) end end end end

Utilizando a gem dalli:

# config/initializers/multi_tenancy_cache.rb module Dalli class Client private def namespace Apartment::Database.current_database end end end

OBS: Tanto o cache padrão do rails, quanto a gem dalli oferecem configuração para namespace, porém não achei nenhuma forma de utilizar de forma dinâmica.

Abraços, Diego