Can I share IIS virtual directory among multiple web servers without impacting performance - iis-7

I am hosting a web application on a scaled environment of N servers (Web01, Web02, ... , Web0N) and I have 2 options for deployment:
Deploy binaries to each server.
Deploy binaries to one server (let's say Web01) and share them with other servers.
The only benefit from option 2 is to ensure consistency among servers and avoid deploying different binaries on any of the servers.
However, I assume this creates I/O and Network bottlenecks on server Web01 as all servers access the same DISK through NETWORK to load binaries and configurations.
My Questions Are:
Can anybody confirm or contradict my assumption?
Is there a way to apply a POC and compare the results in numbers?

Related

Wordpress site extremely slow after migrating to Azure App Service and Azure Database for MySQL Flexible Sever

I was previously running both my wordpress application and the mysql database server installation inside the same Linux Virtual Machine on Azure. I recently migrated both to Azure App Service and Azure Database for MySQL Flexible Server respectively in the same region - East US. Unfortunately, this has really slowed down the application and page load times have increased to an average of 11 s from 1 s. I served all static files from a CDN but to no avail. Checking the network waterfall, the scripts blocking the page are calls to admin-ajax.php. Increasing the compute of both services to a ridiculous size (there is no traffic right now) only improves the speed to 6 s. Since, both services are in the same region I do not believe there can be such a significant network latency between the server and db. What additional steps can I take to troubleshoot the issue?
If you isolate the slowness endpoints and if its due to SQL then I suggest to configure VNET integration with app service and use service endpoint, Microsoft.SQL at subnet of app service integrated subnet such that some of limitation regarding number of sockets and network latency rule out and should observe performance gain. Parallelly you need to check SQL execution time either using profiling of queries or using Performance recommendations.

Should BizTalk Enterprise Single Sign-On be running on non-cluster servers?

Should BizTalk Enterprise Single Sign-On be running on non-cluster servers?
We have 4 BizTalk servers, two of which are in a cluster, and are running EntSSO, FTP and POP hosts
I've noticed that the other two BTS servers are still running EntSSO
Is this right?
YES. But, it must be running on clustered servers as well.
Meaning, Enterprise Single Sing-On must be running on every BizTalk Host Computer regardless of whether or not there are clustered Hosts.
The two situations are actually completely unrelated.
Huge Note: This is also completely different from clustering the Master Secret Server. The MSS should never be clustered on BizTalk Host Computers.
BizTalk depends on Enterprise Single Sign On. The hosts cannot be started without it.
The mechanics hasn't changed since BizTalk 2004. For further information see:
Installing Enterprise Single Sign-On in a BizTalk Server Environment

ASP.NET - deploying application to local IIS

There is an intranet based ASP.NET application that is deployed to a server (IIS) and a group of clients (about ten). The end user can then decide to either connect to the local application (deployed to their local machine) or the server version. I do not understand the reasoning for doing this. My question is: is this common practice?
yes, it is a common practice to verify the performance of the application. Each client will have their own settings and as per process, application should not break in any kind of environment. it is always beneficial to put a server version and a local version.
If the clients are laptops, and the application supports disconnected data sets and synchronization, it would make sense. Typically you'd see something like this when the client machines are taken off-network to be used at a remote work site.

Security groups and UDP on Heroku

Has anyone experienced running multiple collaborating applications on Heroku? For example, an admin application to manage another application; or a stats server observing another application?
On Amazons' EC2 platform you can use security groups to restrict access to servers, creating a virtual network between your application or server instances. Is there any such way to do this on Heroku? If so, can you open UDP as well as TCP connections?
Thanks
Robbie
The comment from #elithrar is correct. To talk between applications you either need to define an API, or used shared resources. For example you can have 2 applications connect to the same database by manually copying and pasting the DATABASE_URL from one app to another. This has the downside that should we need to roll credentials (very rare) your manually copied configuration will break.
The same pattern can be used with any add-ons, such as https://addons.heroku.com/redistogo or https://addons.heroku.com/iron_mq to share a message bus or queue between two applications.

windows service cannot access a webservice

We have two servers, both are containing a local application connecting to local web service, applications and services are identical on both servers.
One of the servers work just fine,
The other one is just dead, I have impression the the security configuration are different on those servers.
What prevents an application X from connecting a web-service, given that another application y on the same server can connect to it. and X is a windows service.
What I should check, what is chances?
Thanks
Check if there is any firewall that might need to some ports opened up.
Could there be any kind of AntiVirus or similar set up on one of the servers?
Basic troubleshooting of loosely-coupled applications means independent testing/verification of those services.
Can you access the web service locally through a different application, i.e. a web browser? If you can't reach the service through the browser, then the server configurations (at some level) are not identical.
Only after you're certain the service is reachable should you look into issues with the windows service.

Resources