About the talk
With hybrid cloud becoming the new norm, enterprises are increasingly looking at “lift and shift” or “modernize and shift” solutions for their modernization journey. APIs provide enterprises with a flexible, secure, and intelligent way to move their workloads to the public cloud.
Consumer applications are transparent to the migration as they use a consistent API interface during the migration and beyond. Google Cloud’s API management platform, Apigee, provides the ability to route traffic dynamically across legacy (on-premises) and modern cloud microservices. Services can be made internet ready by protecting them using Apigee security policies. Proactive detection of traffic and performance issues is a key component in the migration of services to the public cloud.
Hear an overview of modernization and migration to microservices using Google Cloud’s API management platform, Apigee and see how Pizza Hut is using the platform for their modernization effort.
Speakers: Abdul Kinadiyil, Chuck Rhoades
Google Cloud Next ’20: OnAir → https://goo.gle/next2020
Subscribe to the GCP Channel → https://goo.gle/GCP
product: Apigee; fullname: Abdul Kinadiyil;
event: Google Cloud Next 2020; re_ty: Publish;
Hello, Emma, Billiton Canadian solution. Architect at Google Cloud. Specialized in apogee, we are going to discuss how API management play. A critical role in your application modernization Journey from Pizza Hut in this session. Tramadol. I am truck roads. I am the director of e-commerce, technology for a Pizza Hut us. So they're doing a lot of work on modernizing our platforms and in particular implementing apogee is part of our Tech strategy to back you up to This is the agenda for today's
session. We will see the trends and pattern in application modernization. Moving to a micro Services architecture is essential in Airborne isolation Journey microservices then check will cover the use cases and some of the challenges, the team encountered in the modernization effort then we'll take a look at what API Management in a pudgy platform brings to the table when it comes to modernizing our application. Today's customer needs a seamless experience across devices,
start an e-commerce transaction on my smartphone and then later, I may move to a voice assistant such as Google home. Then I'm a complete that order on my Google Voice, at the end of the day, the customer is expecting seamless experience across these devices. Legacy applications that we have in the Enterprises are not meeting Tuesday match. What are the requirements for the modern applications? From the business perspective you want to increase revenue from the business channels and you
also want to open up new business dance, want to build application and deploy more frequently. We already saw the inducers one seamless experience across this device. That brings us to the compostable Enterprises. Every organization out there is embracing digital transformation, and moving to a combustible Enterprise. That means today, you may have a lot of more delete applications with business capabilities, to send developers Partners, will be able to leverage those business capabilities and create new experience to your end users.
How do you moderate your application? The answer is moving towards a microservices architecture. Let's see, one of the key aspects of Microsoft versus the first one is composed of Ricky and replaced with a p that means you can take this microservices. Back is them differently and give different experiences to end users who can replace one version of the micro series with other technology. That means you can develop microservices using different Technologies. One can be using Java and a little can be using python. You can scale this microservices
independently of each other and you are partitioning the big tasks to smaller pieces when you move to a micro Services architecture, You would have focused teams? Did he created to manage these microservices that will allow you to move faster and reduce the time tomorrow? The video of modernizing you are multiplication and moving to a micro Services architecture. This may be your future state that you are an investment for your application. You may have an e-commerce multiplication with you. I then use it all dedication order Management
in Ventra, look up, Etc and move to independent, microservices. But the reality could be somewhere in between meaning, you may still have to leverage some of the capabilities from the Legacy model multiplication. And some balance to capabilities, such as inventory, management, or order. Look up from the inventory. From the e-commerce application will be moved to a micro Services architecture. No, let me turn to chat and let's hear from Chad, how did the modernization journey start for Pizza Hut
and what are the challenges? The team pad in the early stage? Thanks Abdul much as I do as described. Yeah. Where we started out on her modernization journey was a mixture of a lot of the different worlds that Abdul has described and talked about in the center of our e-commerce platform was an e-commerce core monolith application on the service, all of the, the major purposes and components of e-commerce, technology, as well as a lot of back and Reporting capabilities, data ingestion, and things like that. I'm, in addition to that. We had started creating several internal
service, apis different components focused on some parts of our technology, like localizing customer to the appropriate store for deliveries or Carryout. In other things around delivery tracker and other pieces that we've built more recently in an Amor modern microservice Centric architecture. In addition, to that way of things like RBI platforms store, communication back of house systems. POS is I really a complicated and Wide spanning Technology stock making up all of our infrastructure for our Commerce business. In the beginning, where we started from these Technologies didn't have
a common way for us to use or access them. And so lots of connections exists between all of the different components and pieces. Are there many different ways of accessing different components? Some of them are through a modern idea of API summer, very older types of Technologies and approaches the TCP sockets or other transport Technologies with no standards around how we would access and utilize all of the services. So one of the first things we really focused on was creating an API that aside and security around her apis, we did that by implementing apogee. Which very
quickly gave us the ability to establish a common authentication structure and strategy. I would have Security office in Acacia model across all of the things that we were converting into a TI along with. That was building out an API layer over the top of the Commerce Court. So the week of the unplug, all of the functionality of that core into the new API Gateway layer that we had developed this key. Let us do two, things are really important for promoting the adoption of those apis. As we move forward, I want we were able to use aquage, he's built in developer portal technology
to very quickly and easily create a way to share the Swagger documentation and the API. Schema spec information around that with the consumers of the guy with in Pizza Hut. So any future client work. It was being done, could very quickly and easily adopt and take advantage of those new apis rather than going through the old ways of integrating of the system II. It allowed us to bring a really good. Clear point of view on what all of the apis and different technology points we had in the system and start planning for how we could modernize and bring No systems along the path of the coming
really futurestay, micro service-oriented architecture. Swear that we want to talk a little bit about what that modern is there she Journey can look like I there can be many pads of getting from where you are today and over onto cloud. Is it going to illustrate in this information here? You can start out on prym. But sometimes you start out with lifted and shifted Technologies sitting in a cloud where you taking a legacy Technologies stock. I'm, you may have moved it into a cloud provider, but you haven't really modernize that technology for Pizza Hut. We did a little bit of all of these.
We had fun places where we were very, we were in a position to take a service and go ahead and start from the ground up and breaking it down into micro services, in carrying it Forward, other places we needed a shift technology over into the cloud. I'm so that we could then begin doing the breakdown year. One of the really valuable things about having the API management layer in place, is it enables you to use all of these different Journeys, Orem Picture of them at the same time and back over to Abdul and he's going to talk to you a little bit more about API management. Thanks,
Jeff, you may have heard from Chad. Dad was a critical aspect in there. More night session effort allows you to establish a relationship between consumer developers and and your service 36. Such as Legacy application team, or cloud-native application team. Happy to allow you to expose your business capabilities, As Nice apis using the features such as security than body technician, mediation of protocol from soap to rest and rescue soap, and operation management. Do not report Alexa. The reporter is a key feature
with the apogee platform to interact with a p. I c the catalog of apis register with Madera portal and start consuming the aps. A first-class developer experience to your consumer developers on the day, one of your more nicer. No, let's see. What are the items when you are more nice in your application in this pattern, you have a legacy service running on your own provide data center and you are putting an API for sale on top of it and leveraging, the capabilities from the apigee API management platform such as API undertakes, then
Port addiction Edition excetra and then exposing a nice interface to a consumer developers. This gives a better experience for end users and consumers. The next one is hybrid application in which you have a legacy service. You may have rendered this Legacy service within your own promise data center using a modern infrastructure services, such as kubernetes in. And then, you may combine the experience with some of the good Technologies at Google Cloud offers such as data loss. Prevention cloud storage, artificial intelligence and
machine learning experience to our consumer developers and end-users. They're not actually aware of the fact that they are interacting with a legacy service behind the scene. The third pattern is cloud-native application. You may have Greenfield applications that you are developing using cloud-native Technologies infrastructure services such as Google, kubernetes engine, computer surveillance application using Cloud Drive. And then you can using route built. And here you can see leverage some of the cloud services such as artificial intelligence V store that cloud storage.
So in this case you're in consumer and then see what developers are getting a modern experience. Some applications. You may take this patterns as stages, the stage one, you have a legacy service and then you are modernizing it and moving to Stage 2 hybrid application, and the stage 3 trout native application directly Jam to Cloud native, or hybrid application, it is not one-size-fits-all. You can actually take my three parts to your destination. No, let's hear more
from Chad, how did the team at Pizza Hut? Decomposed a mortification and move towards a Microsoft versus architecture? Thanks Abdul, as we talked about before, we had once we had an API Gateway in place that we could use to bring all of our connections in traffic into our platform. That really enabled us to start looking at how we wanted to break that e-commerce core down and how he wanted to start transforming a lot of that into microservice technology. I think it has a lot of flexibility and doing so because once we establish that the side for what, that a p,
I was going to look like through the Gateway. How we enable that with the service is behind? It was much more flexible and had a lot more room for change. That's what we started by taking small pieces of that architecture that we could really make independent and run separately, I'm all the while. We could keep the functionality in the monolithic or that needed to stay there for a longer. Of time. In addition to this, that's a lot of society's platforms into the other services that we are running with her, internal service apis and platforms. I may still be able to control and
manage all of the traffic going through those API. As we went along, no one of the things you may have learned. If you've already been through a micro Services, migration yourself, or I'm some good good tip for you. As you move into that world is the visibility and management becomes a really important component of what you're doing with your microservices. As you move through one of these Journeys. I with all of these new Services interacting and coming together to provide data and capabilities to your customers, where that traffic goes and how it flows through your through.
Your system can become really complicated. Fortunately, we were able to use a lot of the capabilities in a pudgy along with some of the SRE principles around golden signals to capture the Telemetry we needed and get that to her logging infrastructure so that we can see exactly what is going on from service to service without using a pudgy and a combination of other Technologies. Were also able to manage that Nash and how those Services immigrate and interact with one another now dualism, Talk you through a few more things about some of the capabilities for service mesh Management, in a pudgy
available today. A lot of micro services that can become unmanageable and why is an open source company that is popular in service mesh and Microsoft versus World, actually allows you to dynamically, route to request, then distributed racing and then observability to your Microsoft Surface support for HTTP protocol. Grpc protocol excetra to enforce security policies across the board in a more consistent manner, using App keys and all that article. it will allow you to Charter the
micro services in a more consistent manner using distributed quarter you can collect and let its data across microservices running in clusters and regents Inside Mari, let's take a look at what are the some of the challenges that we have seen across the Summers? When they are modernizing the application? The first one is business continuity. When you are born, I seen your application so I can see what developers and end-users should be able to interact with your services without any disruption. Then
when you move the workloads from your own provides data center to the cloud, then the data can be located everywhere. That means under my data center public cloud or internet work. The security should not be compromised when you are more nice in your application, you should be able to know how much traffic is going to the Legacy services within your own provides data. Centers versus the order Microsoft pieces in clock. And then you should be able to enforce security policies across microservices and you should be able to travel to services without any prompt.
O, a b c can help you are a PC will allow you to collect between the Legacy service and microservices the modernization complexity from your end users and come see. You can enforce security policies more are consistent across the board. Allow you to mediate between Cloud protocol as well as Enterprise security protocol. You can integrate with existing ID systems that you have in your Enterprise. Visibility is the key aspect you can use apogee dashboard to view the
traffic that is going through your legacy Services versus microservices. Apple TV, allow you to put an API filstar in front of the micro services. So you are consumer developers, has a knife experience. Been interacting with those APS. You can manage your Microsoft offices in a more consistent manner by enforcing security policies, across clusters, and across the region using apogee and wire adapter. You can also collect analytics data and then view them in a single pane of glass, which is a pudgy dashboard. The weirdest
appvn.apk management fit in your technology stack for modernizing your application to use when you have more lice in your application. You can do everything fast accessories, such as Google kubernetes engine. Then you can leverage the dynamic routing capability distributed facing observe using the service mesh. And you can also double up the surveillance technology app using the cloud run. API management steps on top of this entire technology stack and you can build an echo system of your
consumer apps and developers, you can open up new business challenges, as you are exposing your business capabilities As Nice a p. I do to a platform with security operations capability, to manage your micro Services across regions and across clusters. Before we wrap up, let's take a look at. What are the key benefits that you get by leveraging a pain management in your application modernization. June 1st, you'll be able to discover you are exposing your business capabilities As Nice API,
and then you consume such as partners. Be able to use these apis and create new experiences for end-users that will open up new business channels for you. And then you got to come see what developers are getting a first-class developer experienced by coming to your developer portal and interacting with the apis on the day, one of your message. They are looking at your apis, interacting with them and registering and consume those API. You can access the Legacy and modern
Services seamlessly using API you can measure the cloud adoption and how much of a traffic is going to your legacy Services versus microservices that you are running in the club here from check. What are the key benefits? The team experienced, when do you say p.m. Management in there? More night session Journey, Thanks Abdul, all of the benefits of that bills discussed. I could, I could tell you how Pizza Hut has experienced this firsthand the key among those is really our ability to accelerate adoption and speed to Market with our API by having the API for
thought in place, I'm in a tables are supposed to launch new Services as well as my great old components into new services without affecting the downstream consumers, on top of that, having a developer portal available to expose those apis, to are consuming developers who can easily access the technology and be interacting really. Quickly has enabled us to deliver features, enter mobile platforms and website on with a greater speed than we ever have before. I'm so with that on, say thank you that dual for all of your hard work on the apogee team in Google. In general. I'm also thank you
Buy this talk
Buy this video
With ConferenceCast.tv, you get access to our library of the world's best conference talks.