Have Geek Brain

Network application / web server separation

In the Java world, I often see a separation between the web server and the application server. The idea is to easily shrink your "relatively" cheap web server and grow your application server if needed.

However, I don't see this setting in the .NET / Windows 2008 world so much, why? One of the arguments against this architecture in the .NET world would be the cost of IIS7 / W28 licensing. Is there a reason why .net developers / architects don't go after this design?

+2


a source to share


2 answers


There was no clear concept of Application Server in .NET. Also .NET is very well "integrated" with the OS. We can say that up until now the Application Server role has been in IIS and Windows. You get pretty much everything you need packaged in the .NET framework.



Also note that as of April 2010, you can use AppFabric, which is Application Server. I started to rate this product and it looks really good. So if you're interested in .NET Application Server, check out AppFabric.

+2


a source


This is because it brings complexity to your architecture with minimal benefit. You will see much larger gains in application performance by growing your database.



0


a source






More articles:


All Articles