>>Mm. >>Amdocs is a leader in providing software and services to some key industries, like telecommunications, media and financial services. In our next session, >>we >>welcome Cedric Jay Gould, who is the head of technical product at Amdocs. And we'll learn about Amdocs modernisation journey and how it added value for their end customers. Cedric. Welcome. >>Welcome. Good. >>Thank you. So describe your modern application, your portfolio, and you know what you're delivering for customers. >>So home dogs is B s s S s players who we are providing a food digital suite for customers. Uh, our customers are communication service providers, which are have to deploy a full digital sweets customer experience. Um, we're for the full os BSS, BSS tax. So, actually, Amdocs is one of the leader in this kind of digital transformation. >>So of course you talk about this as and BS. I mean, you're talking about some really hardened, uh, stacks, right? Uh, telco industry. Uh, say what you want about it, but, boy, the phone works when you dial it. So So you've got this sort of a decades old, you know, platform that you guys have been evolving over the over the years. described this modernisation journey and and the role that couch base played. What value does this offer This modernisation offer to your organisation. And where does Couch based fit? >>Yeah, exactly the same. So that so. Basically what, uh, all solution is You know, it's a broad for you of a large number of components which have to deal with funds, uh, experience of the user and from and then dealing all the, uh, activation of the services in the network in order to deliver a solution, Uh, your services, like mobile services or communication services to, uh, Susan users. So we have a full suites, which, uh, was previously based on, you know, on technology is based on the oracle with web logic and things like that. And what we did is that we do a modernisation of, uh, this something, like, six years ago. A bit more than six years ago. We start to modernisation and transformation of our product into a creative solution. Collaborative solutions. So, uh, and when we did that, we start with Coach base as a partner, uh, to provide the nominative database. So we are actually delivery. We have a guarantee of more than 8000 people developing this product. It's a product which is used by more than 300 customers. Uh, so So it's it's real product that needs to be very flexible. That needs to address many kind of use cases from, uh, Telco or customers, which RCs PS usually till 0 to 1 telco. So we what we wanted to build is a food creative solution that can work on any cloud, then can can skill very, very easily and can address multiple use cases. Okay, And that's why, Coach Base, when we selected Coach Basit, it matched a lot of requirements and criteria as we had. And when we decided to modernise our product, we decided to work with >>you. So you had a lot of experience and and legacy with Oracle and Web logic. I'm curious just to follow up. Why didn't you stay with Oracle? You mentioned? Gotta run any cloud. You gotta be flexible. But could you could you double click on what Couch based delivered from a requirement standpoint, that was such a good fit? >>Well, there's there's a good fit with technology that such as, uh, coach basis. First it's a noise school detonates, right? So it's in terms of performance for some of the youth case that we have. It's very important to have, you know, technology which are are done and optimised for the noise secure use cases. That's the first thing. The second thing as I mentioned the scalability, the fact that you can, almost indefinitely infinitely you can increase the size of your cluster. You can have more, uh, servers and and and And this will skill, you know, very rapidly. And also what we're very interesting to have from coach bases the ability to have something which can be replicated across multiple sites. So with visual technology from coach base, which enable to build, you know, very modern architecture with deployment on multiple agents to have disaster recovery, active, active sites, you know, things like that which are very becoming like the main requirement for more customers now. >>Okay, so I'm presuming there were parts of your application portfolio that you weren't gonna touch and throw away that you had to collect or connect the new with the old. That's always, you know, you know, a challenge. I'm wondering what advice you give to an organisation. That's kind of investing in a similar path, trying to deliver the best digital experiences to customers. You know what? What would you say are the modernisation you gotta have must have, whether it's architecture, internal culture, what are some of those items? >>So so that yes, you're right. I think the integration with the legacy systems is actually, you know, very, very important topic in all domain in the domain. But we we made a very, uh, will see drastic choice or brave choice choice. When, uh, 60 years from now, when we decided to reformat to re platforms are completely or portfolio. Okay, So we we changed more than 95% of our portfolio and 95% of the portfolio today, Arklow native. Which means that they can be deployed on any cloud that actually, they are fully scalable and and and still, we did this transformation. Now, when we do the digital transformation of the, uh, customer system, then we need to integrate with legacy systems, and we need to help our customers to migrate from the legacy systems to creative solutions and doing so, it's important to have in the database domain. It's very important to have a solution which is very flexible in terms of, uh, what kind of data I can manage. And I can, as I said, skill easily, for sure. But also, it's sexual. Okay, Because when you are moving the data from a legacy system or record based or whatever to, uh, another type of, uh, database, you want to be sure that you are you can do it securely, and you're you're not, uh, compromising in any sense, Uh, in terms of security scalability, uh, etcetera. Right. So So, um, in this case, I mean, I will say And then in this opportunities journey, uh, this was very, very, very, very important component in, uh, you know, in our strategy, for all the reasons I mentioned right, it's very coordinative. It's scalable, It's secure. Uh, it's another product, uh, grade. So? So that's that's why it really is. So there's there's a chest back to you. >>You know, this notion that 90 per you really re platform 90% of your portfolio and made a cloud native. That's that's a It's a brave move because a lot of companies do that that I've talked to. They will build an abstraction layer and microservices and make that piece cloud native and then have that kind of overlay. You decided not to do that. Why is that? Was that for performance reasons? You were worried about just bringing along technical debt. I mean, that really must have been an interesting discussion internally in your company. >>Yeah, it's true. I mean, the main motivation, the main driver was business flexibility. Because now we live in a world where our customers, what they need is to be able to test the new feature quickly. And they need to be able to scale the system in a matter of hours. Okay, so we are not in a domain anymore. Where you you when you have to upgrade something, you need to take a few days. It needs to be done in a very, very quickly. And the only way to achieve those, uh, requirements business requirements is to be creative. It's to build microservices and to really realise one of those per cent of, uh, micro services architecture because this is the only way you will have the business flexibility. You will be able to have a resilient architecture. Uh, you know, you can, uh you can deploy this with full high availability across multiple zones, multiple regions and feeling that so, uh, any modern architecture today that that is competing with us, Actually, a micro services based architecture. There is no other way to achieve, uh to to to meet the requirement of the market today, and especially when five g is coming, things will become much more complex. Will become much more, uh, distributed. Uh, you cannot work anymore with the model it architecture. And again, I think the database is nowhere different. Needs to follow the same kind of architecture needs to follow the same principles. So that's that's why am I mean another another point about Yeah, >>So if I If I summarised, it sounds like your top three requirements would be flexibility, which you're getting from the cloud native and microservices piece the scale and the security. Is that right? That I get that right? The three top >>That's right. And the resilience as well. I mean the fact that now you know, with micro services architecture, if one of the system is done, he knows how to self to restart it himself. Right itself. Sorry. So So that's this kind of architecture that we built. It's an architecture which can be resilient in a sense that it can sense itself, and it can ensure full availability. And if something is going down, is not working properly, then on some kind of mechanisms will happen in order to go back to a stable state. >>Yeah. So you've got that automation in there. So you don't doesn't require the labour that it might have 10 years ago. So you're obviously embracing cloud native microservices. So you're on that jury. I'm curious. What are you doing with that? You're you're freeing up. You guys used to bring in lab coats and dig in and figure out what's wrong or restart the system. Where are you in your journey, and how are you? Sort of reallocating those resources. And where do you see that going? >>Yeah, Okay, so that's that's a very good point. Because actually, we when we build this new system, which is unable to do, you know, to self heal himself, right? Uh, actually, the question was more about how we can improve the system, even know how we can be sure that, uh, you know, issues that we we any issues which we are we are facing will not happen again. Well, not actual again. Okay. And this is a, uh, principle. Okay, Practise that we have now people are walking on automation. They're building automation around all these recovery procedures about, uh, fixing. So they're not actually digging into the application now anymore into the system, they learn how the system is walking and buildings all the right automation task to ensure that the system is constantly, constantly resilient. Alright, so that's the necessary practises organisation is now built around. You know, this kind of this approach developed computer develops being fully a geologically having sa reorganisation SRE oriented organisation. And, uh and that's the only way you know you can reach very high, uh, in terms of availability. >>So the big problem that your traditional telco customers have is the amount of data that they're servicing going through the roof and the cost per bit is sinking like that. And you have all the over the top providers coming in creating these customer experiences with modern applications and they've owned the customer data. You mentioned five g. So I'm interested in what the future of modern apps looks like for Amdocs and your customers because five G gives your traditional telco customers the ability if they can have these flexible systems that you're providing to now have better relationships with customers and actually kind of reclaim, you know, some of that that value that they've lost to a lot of competitors, your thoughts on the future. >>So first, you know, technically speaking, we we we will have two challenges. One is about data, and other one is about distribution of the work. Okay, because when we are speaking about five g, we're speaking about the age. We're speaking about the fact that an application may be located very closely to the network because it needs to be to to achieve, you know, to to deliver a very short latency, and, uh and this application can move. Okay, so you you you you will have to be able to distribute completely your your solutions. Okay. And that's why we are working closely with, uh, club providers at the US as you Google and because we we need to be sure that the applications of the systems that we are building will be able to distribute the application as close as possible to the end users. Okay, so that's that's one of the key challenges. Which means that the application is to be very possible and he'd be very scalable, and then it needs to be able to move very quickly from one place to another. That's really what is what What, what? What is happening now and what will become, uh, with five G? The other challenge is behind the communication of all these components is really the data, because now we will capture more and more that are coming from the different systems. And I'm not speaking only about the consequence the customer that are who they are, what they what they like and what they want to do, etcetera. And speaking also about, uh, monitoring that of the systems. Okay, so we will generate a lot of information and this this information needs to be traded very quickly, needs to be stored in very large data lake, and we need to have extraction and manipulation of the data very, very quickly to to give the right information to the applications. Um, in this case, okay, it's very important to have application to have databases that can as I said, skill very quickly. But also we'll be able to have very ideal city note, you know, sense that they with a certain amount of memory or sentiment of storage, you can store a lot of data. And this is where we are always, you know, checking what is the best technologies. And so far, not coach bases, technologies that we're using for for stalking, storing all the data. Because because it's it's a ratio in terms of, uh, performance on the number of data you can store, Uh is very high. Okay, so that's that's another challenge that we're addressing. Of course, God is not the only solution, but it's another another one. >>Excellent. Okay, we're gonna leave it there. Cedric, Thanks so much. A great storey and really appreciate your insights. >>You're welcome. Thank you very much. >>Okay, that's it for today. I hope you've enjoyed the application. Modernisation summit made possible by Couch Base. We shared some fresh survey data and got the perspectives of three expert analysts. We got an outstanding roadmap from Ravi Meyer. Um, who's the CEO of Couch base? And of course, we got the customer angle from Cedric. So look, Maybe you're an organisation going through a modernisation initiative. And if you're thinking about what the future of applications looks like cheque out couch. Based on the road this summer, the application modernisation summit is hitting the road traversing North America and Europe. Find out where they will be where they will be near you by visiting couch based dot com slash roadshow. Ravi is gonna be there along with other thought leaders and peers who will be sharing learnings and best practises on how to modernise now and for the future. And you'll get a chance to interact with some of those piers, something that everyone I know is looking forward to. This is Day Volonte. Thanks for joining us today. And thanks for watching the Cube. Mhm. Yeah. Mm, yeah.