February 2010 Entries

Multi-tenancy in ASP.NET MVC - Controller Actions (Part I)

Previous entries in the series Why we want it Breaking it down + Themes Views  In the last entry, we covered how and why we might want to replace existing views and partial views from the core application with our own from modules. We also covered that with this ability it was possible to add entirely new views and partial views. However, views need actions and actions come from controllers. If we add a new view to the application and the core application does not support that path with an...

DDD8 Feedback... feedback

The feedback from DDD8 has come in, in anonymous form and for the most part I'm completely overwhelmed by the positive response the talk garnered from the people who attended the talk. However, I get the feeling my talk managed to polarise the room somewhat and I'd like to respond to those that went completely the opposite way with their responses and apologise if I went a different direction to what they expected! Varied Demos Okay, no defence here at all - showing you all the same website over and over again until I got around to showing the final product of the...

Multi-tenancy in ASP.NET MVC - Views

Previous entries in the series Why we want it Breaking it down + Themes One of the requirements of our multi-tenant application, is having the ability to replace or add new pages (or parts of pages) in the system for each of our modules. While a customer may ask for an entirely new 'area' on the site (MVC2 covers this), the chances are they just want the addition of a single page or replacement of what is already provided in the stock product. The obvious port of call for change of this kind are the...

Multi-tenancy in ASP.NET MVC - DDD8 Video

The video is now up of my talk at DDD8, I've reviewed it and determined that while it's a bit fast ("Like listening to a podcast at double speed" according to @lukesmith) it's not too embarrassing. Unfortunately the audio gets a bit out of sync towards the code, so you'll have to use your imagination until what I'm talking about shows up ;-) Multi-tenant ASP.NET MVC Projects (Or 30 very different customers and a single codebase) - Rob Ashton - DeveloperDeveloperDevel from Phil Winstanley on Vimeo.

Multi-tenancy in ASP.NET MVC - Breaking it down

Previous entries in the series Why do we want multi-tenancy In the last entry, we covered the basics of what I consider multi-tenancy to be, and why we might perhaps want to write our ASP.NET MVC web application with multi-tenancy in mind. The "ASP.NET MVC" component (or front-end) of your multi-tenant application probably only covers a small fraction of your entire codebase but is also the first and often only contact your customer has with your application, so ends up being their first point of call when asking for changes to your system. It also ends up being the most...

Multi-tenancy in ASP.NET MVC - Why do we want it?

I'll be gratuitously "borrowing" a lot  of material from my DDD8 slides in this post, it seemed like the right thing to do given that this series is a write-up and then continuation of that talk. When dealing with more than one customer in the desktop market, it is customary to have a single product which is extendable through the use of plug-ins and an API, and often you can leave it up to your consumer base to write those plug-ins and add to your product in a manner they see fit. In the web world it's a bit different, and you...

Copyright © Rob Ashton

Design by Rob Ashton, Based On A Design By Bartosz Brzezinski