ASP.NET Hosting

Storm Internet supports all currently-supported versions of ASP.NET. At the time of writing this includes:

• Version 6.0
• Version 7.0

Older versions of ASP.NET can be installed on your Storm Internet server at your discretion, and will receive best-effort support from your dedicated SupportPod.

These terms refer to the type of server environment in which your ASP.NET site is hosted. Here’s a quick breakdown of the different server environments:

Shared ASP.NET hosting

ASP.NET shared hosting, much like other types of shared hosting, implies that the resources of a server are shared between several websites, or ‘tenants’. Each tenant is assigned a portion of the processing power, memory, storage space, and bandwidth. In most cases processing power, memory, and bandwidth cannot be increased.

Shared hosting is an ideal solution for starter ASP.NET websites and applications that do not require substantial resources, and expect low volumes of traffic.

ASP.NET cloud server

An ASP.NET public cloud server shares the same physical infrastructure with other servers or ‘tenants’. However, unlike conventional shared hosting, cloud servers are assigned more resources out of the box. These resources can also be increased or decreased as needed to ensure that there’s always enough – even for demanding ASP.NET websites and applications. When needed, more ASP.NET cloud servers can be created permanently or only for as long as needed.

ASP.NET cloud servers are ideal for websites and applications that require the resources of a physical server, but without the associated cost.

ASP.NET dedicated server

A dedicated server is a physical server dedicated to one tenant. All the processing power, memory, disk space, and bandwidth of the server are available to you. Unlike cloud servers, however, dedicated servers come with the added benefit of privacy. ‘Privacy’ in this case refers to some of the security concerns inherent to physical infrastructure shared by multiple tenants.

Dedicated servers are ideal for sites that require a combination of performance and privacy. Where a dedicated server has unused resources sitting idle, it can host multiple virtual private servers, each with its own unique purpose.

ASP.NET private cloud

An ASP.NET private cloud combines the privacy of a dedicated server with the scalability and flexibility of the cloud. The resources of the entire cloud is at the disposal of a single tenant, which means it allows for the creation of entire server environments and virtualised IT infrastructure.

Of the many ways to migrate your ASP.NET website to Storm Internet, migration as a service and manual migration are the most often used:

Migration as a Service

Hosts that offer migration as a service, manage the entire migration on behalf of the customer. The database and all website files are backed up and transferred to the new server. This is often the preferred method of migration since custom configurations, complex dependencies, and other nuances become the responsibility of the hosting provider.

Manual migration

With manual migration you need to backup your site’s database and website files, and move them to your new server. In many cases this is a straightforward process. Any custom configurations, dependencies, and other customisations required for your ASP.NET site to run will have to be applied to the server and tested before DNS changes are made.

Keeping your ASP.NET website or application running optimally requires a combination of coding best practices, server configurations, and regular maintenance. Here are some best practices to consider:

• Optimise Code:
  • Use Caching: Implement caching strategies using ASP.NET’s built-in caching features. Cache frequently accessed data to reduce database hits.
  • Avoid Blocking Calls: Use asynchronous programming (async/await) to handle I/O-bound operations without blocking the main thread.
  • Minimise ViewState: If using Web Forms, be judicious about what you store in ViewState, as it can bloat the page size.
• Database Optimization:
  • Use Indexes: Ensure that your database tables are properly indexed to speed up query performance.
  • Connection Pooling: Utilise connection pooling to manage and reuse database connections efficiently.
  • Regular Maintenance: Schedule regular database maintenance tasks like defragmenting indexes and updating statistics.
• Content Optimization:
  • Minify and Bundle: Use tools to minify and bundle JavaScript and CSS files, reducing the number of requests and the size of the files.
  • Optimise Images: Compress images without compromising on quality. Consider using modern formats like WebP.
• Monitoring and Profiling:
  • Regular Monitoring: Use tools to monitor server health, application performance, and error rates.
  • Profiling: Use profiling tools to identify bottlenecks in your application and optimise accordingly.
• Security:
  • Use HTTPS: Secure your website with SSL/TLS to protect data in transit.
  • Regular Backups: Schedule regular backups of your website and database.
  • Input Validation: Always validate and sanitise user input to protect against SQL injection, cross-site scripting, and other vulnerabilities.
• Responsive Design:
  • Optimise for Mobile: Ensure your website is responsive and performs well on mobile devices.
  • Test on Multiple Browsers: Ensure consistent performance across different web browsers.
• Content Management:
  • Purge Old Content: Regularly remove or archive outdated content, especially if it’s resource-intensive.
  • Optimise Dynamic Content: If your site relies heavily on dynamic content generation, consider strategies like lazy loading.
• Regular Maintenance:
  • Schedule Downtimes: If necessary, schedule downtimes during off-peak hours for maintenance tasks.
  • Review Logs: Regularly review server and application logs to identify and address potential issues.
• Scalability:
  • Plan for Traffic Spikes: If you expect traffic spikes (e.g., during promotions or events), ensure your hosting setup can scale resources as needed.
  • Load Balancing: Consider using load balancers to distribute incoming requests across multiple servers.

By following these best practices, you can ensure that your ASP.NET website or application remains fast, reliable, and secure, providing an optimal experience for your users.