Microservices, or microservice architecture, may not be something you’re seeking, but it is definitely something you could use. But what is it?
A technologist might explain microservices as an independently deployable service, or as building cloud-native applications directly in the cloud versus creating VMs (virtual machines) or SQL servers in the cloud. Still confused?
Here’s an easy way to understand it:
If you use online banking, either through a website or an app, you may have tried to check your accounts only to be stymied by some version of a “come back later” message.
That’s because banks often use direct server architecture that requires regular maintenance. During these maintenance periods, customers must be locked out of the system. This causes front-end users to be unable to access accounts, information, or features due to service interruption. Conversely, a site built using microservices, such as Amazon, uses incremental maintenance that never impacts the consumer.
Similarly, an application on a mobile device can individually update without impacting the functionality of other applications and the phone itself. Multiple applications can update in the background simultaneously and you may never even notice. This is another example of microservice architecture at work.
In the case of online banking, you may just grin and bear these service interruptions. But if their frequency continues to hinder your access and becomes problematic, you may decide to change banks. If enough customers also jump ship, that’s a problem much bigger than an IT hindrance.
So, while you may not be seeking microservices in name, the value microservices brings may be exactly what you are looking for.
Curious to learn more? Stay tuned as we explore more about microservices. For a general overview, visit our microservices service page or get in touch with us to learn more.
