Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
To understand the current state of migrating legacy apps to microservices, we spoke to IT executives from 18 different companies. We asked, "How has the migration of legacy apps to microservices changed?"
You may also like: TechTalks With Tom Smith: VMware Courts Developers
Here’s what we learned:
IT automation is the digitization of IT. It digitizes IT processes such as the provision of new servers, the installation of new software, and the delivery of applications. Successful implementation can lead to cost savings, increases in efficiency and a reduction in personnel costs. You should be paying just as much attention to IT automation as to digitization.
IT automation poses the same challenges as digitization and the added value is just as high.
As with digitization, it is important to know all of your processes and their results. These results are your (technical) IT services. IT automation describes these services in a computer-understandable schema. IT processes are mapped in programs that are executed using software (configuration management systems, infrastructure as code systems).
In the '90s, server software came in boxes containing floppies and CDs that required expert knowledge and hours of setup before it was production-ready. Nowadays, launching server application and infrastructure software is just a few clicks away in all of the major cloud vendors’ marketplaces. However, some fundamental platform challenges around standardization still need to be solved, and Kubernetes seems to be the likely solution to overcome these issues.
In the early days of computing, software and hardware were tightly coupled. Applications written for a specific computer would not work on machines from other vendors. Third-party application providers, also known as ISVs (Independent Software Vendors), that wanted to target multiple platforms typically had to rewrite or modify large chunks of their software to address differences in the underlying hardware. The arrival of cross-platform operating systems and languages changed all of this, allowing ISVs to write their software to a single set of APIs and offloading the responsibility of porting to different hardware platforms to the operating system vendor.