Micro Services and the Holy Grail: Part 2 Vintage code

Micro Services and the Holy Grail: Part 2 Vintage code
July 16, 2019 chris

Continuing from part 1 of the blog we see the current ‘Cloud’ as either Hybrid, where business use both private and public functionality or Native, where the business relies totally on a third-party provider and simply focuses on the code.

The business landscape is changing as new dynamic players emerge feeding off disruptive technology forcing traditional organisations to adapt or die. End user demand continues to drive a ‘continuous improvement’ model with new code emerging weekly or even daily.

To support this requirement the concept of containerised micro services emerged, a modular approach that structures an application into a collection of loosely coupled services (self-contained pieces of business functionality with clear interfaces). Services can be altered/developed/tested in parallel, drastically improving deployment timescales.

The packaging and distribution of these services can be performed by say Docker, whilst the coordination and scheduling left to the likes of Kubernetes or Spring Cloud.

From a business prospective there are obvious cost savings from the optimisation of computational resources but additional benefits lurk under the surface.

Monolithic code is harder to change and longer to upgrade, and may restrict businesses from adapting to market changes or implementing new products. Equally the demand surrounding a successful product may be negated as code fails to scale to meet end-user interests.

Micro service architectures allow for rapid deployment and scaling, whilst placing the business in the driving seat to adapt new emerging software trends.

Hence the drive towards micro services. But how easy is the migration?

Could we lift and shift?

Why. Why move to the cloud without considering how your code develops, how new functionality could augment the services and your business, and critically what exactly are we lifting in the first place?

Monolithic code (vintage code) resides either on physical servers or in virtual machines. The older the code the harder to update. The biggest challenge therefore to micro service migration is not the migration but the identification of the underlying eco-system. What actually makes this tick? Migration therefore is typically top heavy, with many man days required to document exactly what you are trying to migrating.

Then you need to prove/test that what you’ve migrated actually performs the same tasks as its monolithic cousin.

In many cases ‘consultants’ guide business away from micro-services migration altogether through ignorance or the underlying discovery costs.

After repeated end-user requests to solve this problem AnotherTrail identified and began initial partner recruitment for Evolute.io a revolutionary player in both the migration and operation of micro service-based architectures.

Evolute automates the entire discovery process providing a framework of operation for the target vintage code in both Linux and Microsoft environments. The partner can therefore present the target business with their codes entire eco-system and get sign-off for migration. Equally it can provide a reference point for post migration functionality checks.

This dramatically reduces the front-end partner costs and time-to-migrate. It also limits the licenses required (stay tuned on that topic in a later blog).

The resultant container based micro service can run stand-alone in Evolute’s Infrastructure wrap or in conjunction with IaC, IaaS and PaaS services across private and public container based environments.

It offers

• Single click predictable and repeatable deployments

• Interacts with additional services (Terraform, Pivitol, Dynatrace etc.)

• Version control across the estate

• Estate wide visibility of all elements

• Cloud optimisation, simple management, run time alerts and availability network and container metrics/health

• Stand-alone with or without Kubernetes

• For Edge compute (IoT, latency dependant code) simple distribution, geo-distribution optimised container deployment, and version control.

For more details on how to become an Evolute partner or to trial the software yourself, please contact us on info@anothertrail.com

In summary, micro services offer clear business advantages assuming they are underpinned by the correct technical and business resources and partners. Code that forms the core of existing services can now be easily migrated into this new world ensuring organisations grow market position and exploit new and disruptive technology concepts. What you do with your old code? transform it!


Leave a reply

Your email address will not be published. Required fields are marked *


Social media & sharing icons powered by UltimatelySocial