NOVEMBER 2019CIOAPPLICATIONS.COM8In My ViewMoving traditional microservices into Service MeshPOLERIO T. BABAO III, SR. TECHNOLOGY ARCHITECT, US BANKWhat is a traditional microservice?In the year 2000, the technology landscape was already following the three-tier architectural approach. The idea on how to migrate from monolithic applications to medium and large-scale companies has been clear. Monolithic applications are used by some companies to jumpstart their ideas and get a fast turnaround time for their products or proof of concepts.The three-tier approach follows the architectural pattern of separating the presentation tier, application tier, and data tier. Presentation tier can be a browser-based website that uses AngularJSor React JavaScript libraries. Desktop-based applications uses Java Swing or .Net applications. Mobile-based applications uses Android or iPhone native dependencies. Application-tier handles the business logic and is usually created in Java, .Net, Ruby, PHP, Python, etc. Application-tier communicates to the data tier or another application-tier. Data tier can be a form of Relational Databases, NoSQL Databases, Messaging System, Notification System, File Transfer System, etc. Application tier and presentation tier are usually called Microservices as they satisfy minimum business requirements as part of a bigger interconnected applications.Microservices are architectural style that structures an application as a collection of services that are highly maintainable and stable. Microservices are also loosely coupled, independently deployable, organized around business capabilities, and owned by a small team. Traditional microservices are also heavily supporting resiliency features to ensure that applications are always available. Circuit breakers, retries, and fallbacks are additional microservices features that are usually coded within the microservices. In 2010, while making the microservices more resilient, the infrastructure landscape has changed as companies are dealing with multi-cloud and multi-datacenter installation. On-premise application interacts with cloud-based applications and vice-versa. The introduction of smartphones and tablets have also contributed into the infrastructure management complexity as the number of transactions has increased. Applications can be accessed not just on workstations, but also on smartphones and tablets. The requirements for microservices to satisfy resiliency have become more complicated. One of the resilient mechanisms introduced are the use of load balancing and autoscaling capabilities. It is helping companies in saving infrastructure cost as during peak or non-peak hours as infrastructure can be scaled up or down dynamically.At present time, the technology and infrastructure landscape that Developers and Operations community have been maintaining have become more complicated. Companies are maintaining virtual machines in Cloud, and bare metal machines in on-premise installation. In addition to it, now they are dealing with Containers. A container is a standard unit of software that packages its code and all its Polerio Babao is very passionate about security, and recently earned his Master's in Cybersecurity and Information Assurance along with a couple of certifications in security space. He is known by most of his colleagues as an SME on Microservices, APIs, Cloud, and DevOps. POLERIO, an extremely seasoned and successful professional exclusively talks to CIO Applications for a special edition of API.
< Page 7 | Page 9 >