Last week we undertook some upgrades in the three client data centers where our cloud-hosted customer’s MIDAS systems reside.

These data centers are located Atlanta, Georgia (US East Coast Data Center), Seattle, Washington (US West Coast Data Center), and Amsterdam, Netherlands (European Data Center).

When a customer chooses a cloud-hosted edition of MIDAS, they can choose which of these data centers their booking system runs from. (We also offer a self-hosted edition too, for customers wishing to run MIDAS on their own infrastructure)

The upgrades to the sever ‘nodes’ where our cloud-hosted client’s MIDAS systems run include:

• Increased CPU cores by 50%
• Increased Memory capacity by 50%
• Increased port speed by 50%

These upgrades were performed seamlessly without any downtime or impact on customer’s MIDAS operations.

The result of these upgrades is that we can deliver more powerful client nodes, with improved network connections.

In turn, this translates to even more responsive MIDAS booking systems for our customers. It’s all part of the service and commitment we have to our end-users!

The post Cloud Infrastructure Upgrades – December 2024 appeared first on MIDAS - Room Booking System | Blog.

Data Centers exist all over the world. They’re used to stored all sorts of computer data, including websites and web apps, like MIDAS.

Does Data Center location matter?

Yes – The location of the data center that houses your cloud-hosted MIDAS system can have an impact on the quality of your overall experience.

One of the unavoidable aspects of long-distance internet communications is high latency.

What is latency and why is it important?

The term “latency” describes a measure of delay between two events. 

In the context of the internet, latency refers to the amount of time it takes for data to perform a round-trip between two points in a network. In the case of your MIDAS system, these two points are represented by your web browser and the server in a data center which runs your MIDAS system. 

The amount of time it takes for a unit of data to travel from the server in the data center to your browser is considered the latency of the network. This is usually measured in milliseconds and expressed as ms. This is also frequently referred to as the response time of a server.

We recently added two new data centers to our network, including one in Europe.

In our testing, we saw lower latency leading to an approximately 30% improvement in page loading times for Europe-based users accessing a MIDAS system in our EU data center vs our East Coast US location.

How does a data center’s location help reduce latency?

Being geographically closer to a data center can have several benefits, including:

• Lower Latency: When the distance between a user and a data center is shorter, the time required to transfer data is reduced. This results in lower latency and faster response times.
• Improved Performance: Lower latency can result in improved performance for applications and services hosted at the data center, such as faster loading times for websites, smoother streaming, and reduced lag in online gaming.
• Increased Reliability: By being geographically closer to a data center, users are less likely to experience network congestion, data loss, and other issues that can affect the reliability of their connections.
• Better Compliance: Data centers located in specific regions may be subject to local laws and regulations, such as data privacy and security standards, which can affect their suitability for hosting certain types of data. By being closer to a data center, organizations can more easily ensure compliance with these regulations.

How far should data centers be apart?

Having two data centers physically located next door to each other has little benefit. The whole reason to have data centers spread further apart is to reduce risk of downtime and to increase performance.

If two data centers are built next to each other and a natural disaster – like a hurricane or wildfire – hits that location, both data centers are at risk of suffering damage and outages. Whereas, if data centers are built several hundred – or indeed thousands – of miles apart, the risk of the same natural disaster hitting them all is negligible.

Similarly, in terms of performance, if a user is located in London, England, but a cloud-based application they’re using can be run from one of two data centers both located in San Fransisco, California, it will make very little difference to the client as to which data center their application is run from. However, if the client has a choice between a data center in California or a data center in the United Kingdom, there will likely be significantly lower latency from the UK data center.

So, how far apart should data centers be? They should be far enough apart as to minimize a potential disaster occurring at one location from impacting operations at other locations.

They should also be geographically distributed based upon the location that users will be connecting from. If all users will be connecting from within the US, it makes sense to use data centers around the US. If users will be connecting from all around the world, it makes sense to use data centers spread across the globe.

Our Data Centers

Earlier this year, we significantly expanded our network into new data centers.

We added new client nodes in a data center in Europe (in Amsterdam, Netherlands), and in a data center on the West Coast of the US (in Seattle, Washington).

These two new data center locations are in addition to our existing nodes residing in our East Coast US data center (in Atlanta, Georgia).

We then looked at the location of each organization with an active cloud-hosted MIDAS service. Those which were geographically closer to either our EU or West Coast US locations were seamlessly migrated to those data center locations.

Naturally, we provided customers with advance notice of proposed migrations, and allowed individual customers to opt-out, or to choose a different data center for their MIDAS system.

The client migrations went smoothly, and have lead to noticeable improvements through lower latency for many customers.

Because our cloud-hosted MIDAS systems can now be run out of three different geographic regions (US East, US West, and Europe), we now offer all new cloud-hosted customers a choice of data center where they’d like their MIDAS system to reside.

The post Why Does Data Center Location Matter? appeared first on MIDAS - Room Booking System | Blog.

This follows a desire expressed by a few of our customers to be able to have their cloud-hosted MIDAS systems accessible via a dedicated sub domain.

What is a subdomain?

A subdomain is a part of a website’s domain name that comes before the main domain name, separated by a dot.

It functions as a separate website, but still shares the same primary domain name.

Think of it like an apartment within a larger building: it has its own address and entrance, but it’s still part of the overall structure.

Here’s an example:
Main domain: mid.as
Subdomain: demo.mid.as

Subdomains for new hosted customers

At the start of this year (2016) we began providing this to all new customers who chose a cloud hosted edition of MIDAS.

Let’s assume that your company was called “My Organization”. If you subscribed to a cloud-hosted edition of MIDAS in 2016, you would have been able to choose the dedicated MIDAS subdomain https://my-organization.mid.as for your hosted booking system.

However, if you purchased a cloud-hosted MIDAS system prior to 2016, you’d instead have been accessing your system via https://mid.as/my-organization.

This was before dedicated mid.as subdomains were available.

Subdomains for all hosted customers

The good news is that from today, we’ve now rolled out dedicated mid.as subdomains to all our hosted customers who purchased prior to 2016 as well!

So, if you previously accessed your hosted MIDAS system via https://mid.as/my-organization, you’ll now have the dedicated subdomain https://my-organization.mid.as. Old mid.as/my-organization URL’s will continue to work and redirect to my-organization.mid.as for some time.

If you purchased a cloud-hosted MIDAS system prior to 2016, we’d like to encourage you to update your bookmarks and links. Going forward, they should now point to your new dedicated mid.as subdomain!

There are a few things to note when updating your bookmarks/links:

1. If your hosted MIDAS URL previously contained underscores (_), you’ll need to change these to hyphens (–) when updating your bookmarks and links.
   For example:
   https://mid.as/my_organization would now become https://my-organization.mid.as
   
2. If your hosted MIDAS URL previously contained a domain name (other than mid.as) i.e. .co.uk, .com, etc, you’ll need to remove the end part when updating your bookmarks and links.
   For example:
   https://mid.as/myorganization.com would now become https://myorganization.mid.as
   
3. If your hosted MIDAS URL previously contained any period characters (.) (other than the initial period in the primary “mid.as” domain), you’ll need to remove these when updating your bookmarks and links.
   For example:
   https://mid.as/my.organization would now become https://myorganization.mid.as

If you have any questions, or aren’t sure what the new dedicated subdomain for your hosted MIDAS system is, please don’t hesitate to contact us. Our team will be more than happy to help!

The post Dedicated sub domains for cloud-hosted customers appeared first on MIDAS - Room Booking System | Blog.