Service Oriented Architecture (SOA), microservices, and cloud best practices can result in the creation of loosely coupled complex systems with many potential points-of-failure. At Impact Makers, we observe many customers dealing with service outages, which are difficult to diagnose and more importantly, difficult to recover from quickly. Service outages have significant financial impact; therefore, it is incumbent upon software architects and engineers to find ways to prove the systems we build and deploy make it easy to detect and recover from failures.
Infrastructure-as-Code (IaC) is the practice of defining templates that can be used to provision technology infrastructure to support software and applications. Traditionally, physical hardware configuration of network switches/routers, servers, network-attached storage, etc. has been a time-consuming and difficult task that not only was prone to human error—but was also not easily repeatable. Even after the advent of virtualization and the automated software configuration revolution, technology infrastructure was still built on a backbone of (usually) manually-managed hypervisors overseen by IT operations staff.
Ever heard the saying, “The Cloud is just someone else’s computer”? This is one of the many arguments I encountered as I became an early adopter in 2010. While it is technically true, it misses the point: the inherent flexibility and benefits of the “Cloud” maximize the chances of differentiating your company from its competitors, especially in financial services.
Amazon Web Services (AWS) published a case study on Impact Makers’ project with MedStar Health. Impact Makers used AWS to support a new digital presence for MedStar. The collaboration with AWS provides a state-of-the-art platform that is highly secure, scalable and cost-effective.