Our client is one of Australia's largest facility services providers. Like many diverse organisations today, this client's highly effective business operations relied on a small number of mission-critical IT applications. They had identified a major risk in one of their cloud services and invited Kodez to propose a solution.
The client is one of Australia’s largest providers of integrated facilities management services with an extensive client portfolio spanning many public and private locations.
Like many diverse organisations in Australia today, their highly effective business operations relied on a small number of mission-critical IT applications.
One such application was found to have only a single cloud service instance that relied on a single database instance.
Many people believe that “cloud” is a universal panacea for all IT problems, but few appreciate the skills and effort required for a successful cloud implementation.
When the client identified that they had a single-point-of-failure in their cloud implementation, they contacted Kodez to help them re-architect the implementation and implement disaster recovery measures.
Modern data centres are engineered to ensure high levels of resilience and availability. But an organisation such as this client could not accept the business risk of one mission-critical IT application ever going off-line, no matter how rare this might be.
Kodez took immediate action to establish a second cloud instance of the application at a separate location. Geographic separation and physical redundancy are the most common and simplest ways to avoid a single-point-of-failure.
The client required this second cloud instance to be implemented in a Microsoft Azure environment. Kodez configured the two SQL Azure databases and implemented the application stack as a REST API in a .Net framework.
Where the skills and experience of Kodez delivered the greatest value to the client was in how Kodez established the inter-working of the two cloud instances of the same mission-critical application.
Following a review of business requirements, as well as the application performance history, Kodez recommended that the two cloud sites work in an active/passive configuration. There was no compelling business case to implement a more expensive active/active or hot standby configuration. Both cloud sites had their own application instance and database instance
Kodez implemented a Traffic Manager that would direct all transaction processing to the active cloud site unless there was a failure when all transactions would then be directed to the backup site.
For disaster recovery, Kodez worked with technical and business stakeholders to establish the optimum Recovery Time Objective (RTO) and Recovery Point Objective (RTO) for the application in question.
The client determined that Kodez proposed the simplest and most cost effective solution that will meet all the business requirements and objectives. With this approach, solutions are identified and implemented rapidly with a minimum of fuss. Kodez have strong capabilities in both major cloud environments; Microsoft Azure and Amazon Web Services (AWS). We are also well versed in disaster recovery configurations across different compute, storage services. Let Kodez help your organisation leverage the true benefits of cloud computing in your preferred environment.
The DR solution provided by Kodez not only mitigated the risk of single point of failure, it opened up opportunities for them to manage their deployments faster with minimal impact to their core customer base.
.png)
