Comments on: Azure – Performance, IoC, and Instances

By: Shaq

Shaq — Fri, 05 Mar 2010 13:26:55 +0000

I am not clear what does really an ‘instance’ comprise? What are inside an instance? Why Azure needs at least two instances for 99.95% uptime guarantee? What is the catch here?

My understanding is that creating instance is to create a VM – but the question is what size of VM – small, medium etc. So when we create two instances then what combinations of VM size we need to configure.

Please let me know your thoughts.

Regards/Shaq

By: alafdia

alafdia — Tue, 10 Nov 2009 03:06:43 +0000

Sorry for interrupting you… buy nolvadex online http://www.stumbleupon.com/stumbler/med-brother/ buy mexican clenbuterol nolvadex online Remember me to your wife.

Good evening! buy cheap nolvadex online buy cheap nolvadex
buy mexican clenbuterol nolvadex online See you tomorrow!

By: Nicholas Blumhardt

Nicholas Blumhardt — Sun, 13 Sep 2009 14:39:38 +0000

Hi,

>> Autofac – Works great in medium trust under Azure, easy to configure, but doesn’t support registering arguments for constructor injection at configuration time. You have to specify them when you resolve the service.

This is incorrect, Autofac allows constructor parameters to be specified at configuration time either through code or XML.

Cheers,

Nick

By: Dan Vanderboom

Dan Vanderboom — Wed, 04 Mar 2009 20:42:33 +0000

For those IoC containers that didn’t work in medium trust, it would be good to know what techniques they use cause them to fail…

By: jack johnson: LINKBLOG for February 20, 2009 « HopeyArd

jack johnson: LINKBLOG for February 20, 2009 « HopeyArd — Sat, 28 Feb 2009 20:59:18 +0000

[...] Azure – Performance, IoC, and Instances – Jason Young [...]

By: HowTo: Hello "Cloud-Computing" | Code-Inside Blog International

HowTo: Hello "Cloud-Computing" | Code-Inside Blog International — Tue, 24 Feb 2009 01:11:51 +0000

[...] Azure – Performance, IoC, and Instances [...]

By: Kazi Manzur Rashid

Kazi Manzur Rashid — Sat, 21 Feb 2009 04:47:48 +0000

@admin: If the CSL page even say so it is still wrong, anyone can write application w/o deciding the DI with it. The benifit is you can later replace your container without modifying your application code.

By: Scott Watermasysk

Scott Watermasysk — Fri, 20 Feb 2009 14:08:59 +0000

Ninject and StructureMap will both work on Azure: http://simpable.com/code/iofc-on-azure/

By: admin

admin — Fri, 20 Feb 2009 03:50:36 +0000

John, from that page:
“Once you’ve decided on a container that suits your project, there’s not a whole lot of benefit from writing your whole application in a way that can switch containers.”

I hadn’t decided on a container yet!

My application doesn’t care about which container it’s using, so at this point I think it makes sense. Down the road if I need to take advantage of specific features, I may commit to a product specific implementation.

I’m not saying that everyone has to use the common service locator, I just think that it’s important to be aware of it. The hope is to eventually have something similar built into the BCL.

By: John Teague

John Teague — Fri, 20 Feb 2009 01:19:12 +0000

wrt to your comment about the Common Service Locator. Please read this page on the codeplex site: http://tinyurl.com/bhbkkt

Specifically, the CSL is intended for libraries that are consumed by line of business applications. It is very unlikely you need to use the CSL. You will have a better experience if you use a specific container so that you can use all of the features available.