Video details

Jan Leemans: Cloud native Applications from Development to Production


Jan Leemans

Running your Cloud Native applications has never been easier! Learn how you can leverage the Application Development services that are available on the Oracle Cloud Platform to get started real fast, and scale up your application to production-grade enterprise workloads with ease.
Learn about Helidon Microservices, Serverless Functions and of course our Managed Kubernetes platform.


Hello, and this is Jan Leemans from Oracle. I hope you can all hear me. I know a colleague of mine is on the line. So today, if you can confirm that everything is green on your site. Everything is fine. Everybody, let's go crazy. OK. So let's get started. So welcome to this webinar on Cloud Nacre Application Development from development to Production. My name is Jan Leemans. I'm a business development director in the Oracle India Cloud Native Team, and I'm specifically focusing on our cloud application development platforms. Today we will talk about the cloud native space where Oracle has made some pretty big advances. And hopefully you will get a better view on that after this webinar. You can ask questions in the chat and at the end we will open up for Q&A, answering the questions that you've post in the chats and maybe even interactively. I'm actually new to this platform, so we will discover that together. So with that, let me get started. I hope you can see my screen. Should see my cloud native. Yes. I will talk about a few new products that are not yet released. So in that case, the Safe Harbor statement applies. Please do not base any buying decisions on future product announcements. But without further ado, let's dive into the topic of application development. There's been a big evolution in the industry. We moved from waterfall monolithic applications in data centers that customers to a pilot model using virtualization and agile methodologies, too. Now, dev ops or even the psych ops and micro services containers and the cloud cloud has really changed the game. And Oracle is making that move along with you, along with our customers, and offering you choice and options to move from that on premise worlds to cloud, to move from those monolithic applications that a lot of customers are still running to micro services and containers and all the cloud, the good cloud, native and open source stuff in the cloud. And that is basically what we're going to talk about here. And we use the term cloud native a lot. So basically, what do we mean with it? It's the ability to run a modular small scale applications in a very agile way, using smaller teams, being able to scale up and scale down real fast to use any language that you prefer in any framework that you prefer. I run that in open source environments. And the key examples of that technology are basically containers, docker containers and Cooper Nita's and functions. And these are the key technologies that we will leverage and build upon to deploy a much richer set of features that is based on top of that platform. So Docker, as the basis can Google Nita's as the orchestration framework to run those types of applications and then serverless applications and then project an open source project. Let's buy Oracle in particular, together with a bunch of open other open source technologies that we either embedded in our platform or new open source project that we launched from Oracle itself. Now some say Cloud Native is, but that might have been through like three or four years ago. But if we look at this survey from the Sincere Foundation, we see that we move from twenty three percent of the organization's running cloud native and production to sic 84, which is significant more than that. It's not only a large proportion of customers running that type of applications, it's also large scale deployments that are happening. If you look on the charts on the right, you'll see that more than half of them have more than 100 machines actually under this type of technology running. So it is very significant. And Oracle is making great strides to have an offering in that space. Why should you look at Oracle for this? Well, basically, we have a nice end to end cloud native and dev ops integrated platform to deploy any application. On top of that, with our history in the on premise world. We have a rich history of data management. I think we can say that we have the richest, richest offering in terms of data, persistency, databases, and a lot of those on premise applications today are actually running on Oracle. And so it is very easy to lift and shift them and reap the benefits of that cloud native world by running on Oracle. And then on top of that. We are now on what we call our Gentoo second generation infrastructure, which has real performance per dollar cost benefits. So from a cost perspective and from a management perspective, we offer Bonilla opensource standard industry standard frameworks like you would need this. But in a managed way, at a very, very competitive cost. So all in all, a very compelling platform to run your applications on both your existing applications on premise, live and ship them over to Oracle and then deploy your club native applications on that infrastructure because it's vanilla. Open source. You can run anything, obviously, on that. And I think this diagram nicely summarizes the offering that we have. We'll go into more detail as we go along. But basically, we have the cloud infrastructure layer, which I won't go too much into detail in, but basically computer search, networking and obviously security as a given spinning of these resources in a completely virtual way. But on top of that, we have a rich set of services, the cloud native being at the core of it with cubic meters and functions and a bunch of other services, allowing you to basically run any language and any framework that you are developing in that cloud. Native fashion, along with and I will detail that also your existing applications that you can also run on that platform. So lift and shift your existing model S to the cloud native environments and make them cohabitate with those cloud native services that we offer a number of tools, developer tools on the left, Oracle Incorporated, a few of them in the platform itself. But we're open to any of the industry flavors there, the data management aspect. Of course, I will go into a little bit more detail there and then the rich set of difficult dev ops environments that you can use. We have a bunch of them built in and I will demo. Hopefully I'll have time enough to build good to demo the visual builder tools still set that we have and a number of other elements, like for example, resource manager, which are the detail that is a terraform implementation that you'll get out of the box. So we're rich set of features. And as I said, we are really shifting from proprietary software to open source. We are bringing industry standard opensource to the cloud by running it as managed services. We participate, for example, for to this in the C NCF Foundation. If you're going to make a change, we submitted and we implement the vanilla SNCF version of Google Nita's, but we also bring our own open source projects to the community and then we run them as managed services at the feet. Obviously that's taking away the burden of actually running those platforms and I will detail that as we go along in the presentation. So without further ado, let's dive into a little bit more detail. Let's look at these cloud native components. I already mentioned that we have cubic meters, obviously. A managed service that allows you to spin that up in no time and take benefit of that immediately without having to worry about the underlying infrastructure combined with that. We have a private registry that allows you to deploy your containers close to the location where the actual application will be running on that Cuban leader's platform. And then a whole set of other services like functions, allowing you to just develop a piece of code and drove it on a on the on the cloud as a function streaming unabashed Kafka like dataflow service, if best to respond to infrastructure changes. For example, new files or events happening within your infrastructure or within your application landscape to respond to that. For example, with a function or with a micro surface and then API management. Obviously, if you want to open up your environments to the outside world, especially if you want to open up your API eyes to the outside world, you need a defence barrier there. You need to define policies and throttling. And what have you to make sure that that happens in an enterprise gateway. So we're rich set of two links that you can use to build and run your applications in that space. Now, if you look at the actual devil's cycle, as I mentioned, I hope I'll have time to give you a quick demo of Visual Build a studio, which is our CIC, the environment that allows you to have, for example, get repository and set up automated pipelines to deploy software, to build docker images and to deploy them on Cuba needed, for example. But there's much more. There's a compatibility with the promise. Prometheus Farner notifications, logging and then resource manager, which is basically, again, an open source platform, an open source project terraform that we offer as a managed service on the platform itself. And I will go later in a little bit more detail on that topic to. Now, obviously, the database is pretty important at Oracle. We are much more than the database. But obviously when you develop cloud native applications, you need to store that data in some way. And Oracle is offering very rich set of ways to set up those databases. You can do that in the cloud in a way that is customer managed, whereby you have full control over their database. You install a database basically that is an exact copy of the database that you would have had on premise. So there is no change to your application whatsoever. Or you can leverage our autonomous offering, which is basically a database that is most of the part managed by Oracle. You just have to worry about your data, inserting it, extracting, etc, etc. The whole patching, updating or grading of that database itself is managed by Oracle. So that's at the other end of the spectrum, whereby Oracle takes a big chunk of running a database. A you as a developer just worry about creating a table, putting data in it and using that environment in your development lifecycle without having to worry about the low level database aspects of that. Obviously, security, again, is very important. Security is big theme to the Oracle cloud infrastructure itself. And on top of that, you can leverage all the security mechanisms that are building over have been building over all these years in the Oracle database to secure data on a number of levels, albeit with data masking, with advanced security on the level of who can see what, et cetera. So a very rich set of offerings that you can use to store your data. On the development lifecycle, as I mentioned, we are basically running on cubic meters, mainly deploying any application as a dock or container. So that means that this is a true polyglot platform. You can use any language. And on top of that language, any framework, obviously, we are. Historically, we have been focusing a lot on Java. So we have a very strong Java offering, but we are definitely reaching that right now. I will talk about a few examples where we have nodes as a base language to develop. For example, visual builder. The rapid development environment is not based on Java is based on JavaScript. So we are definitely extending that. We are supporting all these languages with the case and what have you. And we are bringing opensource elements to that mix like headed home. I have a slide on that. More in detail about how to go on is basically a Java Microcircuits framework that allows you to have low weight applications that spin up real fast. And then we have grow grow. VM is basically a replacement of the Java VM. But in this one, Polygonal compiles Java, but also scripting languages, languages. Most of the languages that are on the slide, by the way. And it's fast. It's really fast. It's allowing you to have spectacular startup plans and also to have runtime improvements. So the compiler optimizations make that it is like 10 to 20 percent faster than the standard Java VM that you would use today. So these are all open source projects which are also available in our cloud in a more or less managed way. As for Grall, for example, is a matched version of it. It's like something that you plug underneath your applications. If we look at the developer tools, so there's a bunch of tools that are included in the cloud. The most recent one is our cloud show, which is a key tool to interact, which the cloud environment, really. So a single location to go. Your cloud console, where you have all your services up or running, Podemos that in a while and with the cloud console, you can very easily issue commands. You have a full fledged developer environment with get docker functions, terraform. All these components are preinstalled in the cloud shell and that allows that, that gives you a lot of productivity to interact with that environment at the same time. All the, I would say industry standard, open source ways to develop. Ah ah ah ah. Open to this bathroom. You can deploy and use any of the tools that are here on the left to deploy and interact with the platform as we have API. See Alize Rest API is to interact with it. We support TerraForm, which we support Ansible so you can interact with all the cloud services in a variety of ways that is fully industry compatible. Now, another aspect I mentioned already, the database in terms of management, in terms of the database, as with respect to micro services, there is an added additional benefit is that you can use the autonomous database as a one stop fits all type of database. In a typical micro surfaces architecture, you have specialized databases, but that brings an overhead of different technologies that you have to incorporate the Oracle database. You can actually have all these types of databases in one single instance. And Jason types the key value and have a relational database, of course, but also other types of interactions with the database. That is all in a single management structure. Very easy for you to develop and maintain those applications along the way. So with that, I think I've spoken a lot on slides. Let's take a little bit of time to show you some stuff. I'm going to go out of my presentation mode and I will go into my browser. So if somebody from the crew can confirm that you can see the browser window correctly. Yes. OK. So I'm logging into. I have a short cut straight into my environment. Obviously, I have to log in, but I think I really love in, you know, I IBC. So I have real again. Here we go. So is the console not spectacular, I would say, but a very rich environment. And to be true, some quick actions that you can do, like creating a VM, setting up a network, creating a database and a rich set of manuals and tutorials to get started. An overview of what has happened. What is the billing situation of your account? But most importantly, the little I can hear on the left. This is basically where you manage all the surfaces. So if you fold that out, you see the different chapters here. And I hope it's too small. You can see the core infrastructure services that that's this menu with compute storage and networking. This is space infrastructure stuff. You spin up a VM. You choose your shape. You choose all the parameters. You get in no time. You have an up and running machine. Nothing. Spectacular there. What is nice is that all the services on top of that infrastructures are in that same menu underneath it. So here you have all the database options that you can spin out. And so, for example, the autonomous database that I mentioned is here, and it's just a simple wizard. If you go into that menu to spin up a database. So I'm here in my compartment. I have two databases that are available. I want to create a new database. Well, I have a very simple wizards' that allows me to specify a few parameters, specify how much compute power I actually want to add to that machine. Specify username password and off you go. That's it. My data will be created in a few minutes. I'm not going to do that in the interest of time, but the same is true for the other services. So that's the second one that I want to highlight is the developer services. And if we go to developer services, this is where we can spin up very easily a company to sponsor. So this is my environment here. You'll see there's a bunch of them up and running again, a very simple wizzard create positive as the quick create very simple way. It's a new carbonemys cluster. I go into my workflow. I have to choose a name. I could choose a version. Private, public. I can choose the shape of the compute notes that are underneath that environment. And then that's about it for the simple ways. There's a more complex vision of where you can do much more configuration and fine-tuning, of which network interfaces to use, which acuity level, et cetera. But this is the quick start wizard you hit next and off you go. You're finished again in the user. In the interest of time, I won't do it. But that is a very simple way to see what is up and running. Here you are. For example, I can go into an existing cluster. I can see some metrics that are there and I can go to my tools and I can see what type of infrastructure is underneath that. This is a very simple one that I use for some testing. It's actually a very old one on an old version. I should upgrade it soon. And that is actually just a button away, right? No tools is where the actual applications were deployed will be deployed. And that is in this case, just a single note. But that can be a much more complex. So with that, I think you've seen a first introduction of the services. There's all the other services that I mentioned yet. Resource manager, the application integration, space monitoring with metering and alarms, et cetera. We will go through a few more of them in the PPD and then I will do a second set of demos. So with that, let me get back into my PowerPoint. Am I doing with time? OK, let's get into presentation mode again. So I'll highlight a few of the surfaces. One of them we already looked at, which is the Cuban exclusive, the matched Cuban discuss. So basically it's an enterprise, great environment to run your container workload's. It's fully managed by Oracle, as you will see in the next slide. It's fully open source based. It's not a Oracle flavor of this of the of the Cuban leaders or anything. It does integrate a private registry, which is just on the side of it. I should have shown you that the demo. I can do that in my second part of the demo. And basically, it allows you to very quickly spin up this this environment. It's available in all our regions. And the number of regions that we have, the number of data centers around the world that we have is increasing quite spectacularly over these last months. And with a very, I would say, ambitious road map ahead of us of new data centers opening a little bit all over the place. So check your nearest data center and you will see that I don't have a slide on that right now. Let's say at the Cuban leaders level. So basically what we're doing is for you running the control plane of that Cuban leader's engine. We run the management node and you do not have to pay for that. This is all managed by Oracle. The same is true for the registry as long as you don't store excessive volumes of data. This is completely free from a usage perspective. And you do not need to worry at all about the underlying infrastructure. You just have a Docker V2 compliant registry. You deploy your story or containers there and you can use it to deploy to your work or nodes. And that is actually what you will be paying for. Is the workload of C.P.U that you are running in your work or notes? And that is where you will have access to. You can access these notes and you can deploy applications on them in the usual way. You have a rich set of choice in terms of underlying types of hardware can be bare metal with as many as one hundred and twenty eight course or a single core virtual machine. And everything in between. So full flexibility there. What I didn't mention yet is that we have three availability domains in most datacenter regions, which means that when you set up a cluster with three nodes, that tosser will actually be distributed across those three availability domains, which are three separate data centers in that same area. So they center right. Most often use this Frankfurt Street, separate data centers. And when you deploy a new company, this cluster between nodes, it will deploy one on each of those data centers in a very automated way. It's completely transparent for you. Basically. So a typical flow is what you have all your CIC details. I will present a few of them that we can offer later. But it can be anything that you're using today. Can we get the lapper, Jenkins? What have you? You push. You build your container. You push it to the registry. You then push your your deployment to your you define your deployment on your next cluster, which will pull the image from the registry. And then your application is basically up and running and you can expose those services potentially using all those other services like low dancer and gateways and what have you, to make sure that this application is accessible in the appropriate way to your external or potentially external audience. So far, so far for the containers. The other aspect that I want to highlight today is the Oracle functions. So this is a serverless infrastructure. It's functions as a service. Well, this is actually an open source project. You can go to Ethen Project DOT you. Anybody can contribute. It's an open source project. You can download it. Run it. But obviously, when you want to set up a serverless environment, actually there are servers somewhere and somebody has to run them. So if you did download the open source, you are in charge of running that platform that your developers will deploy their functions to. What Oracle is offering with Oracle functions is a matched service of that open opensource service. It's all based on containers. So you basically deploy container. And the platform will spin of that container when a call for the function comes in. If no second call comes in after a certain time, there's a timeout. That container will be announced and nothing will run again on that server. So basically, you will pay for use recall to that platform, which is a very, very small fee actually protocol. And then you do not have to worry about that underlying platform at all. And as it is an open source, there is no locking at all. If tomorrow you decide you want to run the same environment on premise or with another cloud vendor, you can perfectly well do that. It is in all aspects open source. So somebody how does it work? You push your function image to the registry as a image, you configure your function on the level of the interface of the matched the functions platform. And then that's where it ends. If nobody calls the function right. So when somebody calls in the function, the function platform will make sure to split up the container. Execute the function response with the answer and then potentially go down again. And at the end, you're built by the call to that platform. So, as I said, it's all based on containers. It's all based on open source library, you can package any open source library. We have a number of is the case that you can leverage that, making it more easy to develop your applications. But basically, you could run anything that is the Bible as a book or container on top of this platform. When would you use this? Well, typically for, for example, event driven things. If if something happens, somebody puts an order in. Somebody does something on a specific system. You can trigger an activity that will spin up a function. Do what it needs to do and then go away again. Can be used both through Web interfaces. True, mobile can be used as a kind of a backend service that can also be used to do Real-Time processing of files. And there are potential to use, for example, with machine learning and in the dead of cycle itself. You can build in these types of elements. Now, talking about the whole cycle. Let me also introduce resource manager. So resource manager allows you to manage your infrastructure ascots. Resources manager is a an implementation of TerraForm. TerraForm is a opensource framework developed by Heshy Corp that allows you to basically configure your cloud infrastructure for a specific project in a very structured way, in a very easy way. That doesn't force you to take into account all the dependencies between the different infrastructure elements. You just defined them and the platform, the framework itself will figure out what is the correct order to spin up that environment. And if you change configuration file, the platform will actually try to get to that new state based on the existing state. And that is where the fact that you package that form as a managed service comes in very good, because in a traditional situation, what you do is when you run terraform just in Europe, you seek to spin up an environment. You get those state files on your P.C., which is not very good in a corporate environment where you have teams that needs need to be able to manage that type of deployment. You want to store those configuration files. Sorry, those state files this specific way. And so, again, using a cloud service that basically offers terraform is a very easy way to share that across your team to a bi governance on it. And again, it's basically a free service you pay when you spin up infrastructure. Obviously, you spin up a database or compute instance or a company express that you pay for the paying resources of that service itself is offered on top of the platform. So I have a slide that because this a little bit so you can do and apply and destroy it like you would on the command line of your reference script. And then you have jobs that you spin up. You can visualize a stack, you can edit the stack that you defines and you can even introspect an existing configuration that is out there and create a terraform script out of that. Do you see that as a starting point? So you don't have to start from scratch after you've done some testing and some building up of an environment. You can simply introspect that environment and use that to replicate it in a second environment, for example, from test to death, props, etc.. And as such. Use that as a piece of code and submit that in your version is. So that basically sums up resource manager, a third service that I would like to go a little bit deeper on is a visual builder studio. This is our Demps environment that allows you basically to manage the whole cycle of developing codes. Packaging the code and deploying it to an environment. It contains a good repository. It contains little pipelines. But it also does the management of your team. It has issue management. It has agile boards and release management, et cetera, all in one single, too. Now, I can talk about this, but I think it's it's much nicer if I showed this to you life. So I'll do that after a few more slides on a few references that I wanted to highlight some of the customers that have been running on this platform. The first one is a snapback. This is a company that delivers visual services. Basically, will the ability to take images and use them in a context of marketing. So they moved into a cloud. Native services using, for example, our graphic jeep. You shape's to accelerate tremendously the speed and the power of their solution. So some some impressive numbers on this case. Deployment times much faster, decrease in management overhead, specifically with respect to the data storage. And then, yeah, in general, a reduction of the administrative tasks surrounding that solution. That combined with a real good uptime, basically 100 percent uptime. So far for this. Another customer is across country. They are using drones to do crop inspection. And they also migrated to this pack from these used Google needles and in this case, not the Oracle database, but the ESKIL database. On top of the cloud platform, you might have noticed that we have multiple flavors of the database. Obviously, the Oracle database is available in different management levels, but is also escudo mice, you know, squirrel, et cetera. So there's a bunch of databases, database flavors that you can run as a managed service on top of the platform, independent of the fact that obviously you can deploy any open source database on top of the structure. Right. So there is no, I would say, obligation to to run the Oracle database, although we strongly suggest that if you want to have some enterprise, great performance, this customer, again, implementing a full solution on top of this. Looking at a serious performance improvement and increase of the developer philosophy as compared with their old solution. Now, another element that I mentioned in the beginning is the fact that a lot of organizations have. Existing applications are not all developing applications from scratch. There's a lot of existing what I would call monolith services, so big old star layer services out there and they're not going to go away anytime soon. Most organizations are not ready to refactor of these applications from A to Z into a cloud native infrastructure. So what can we offer to those customers? Well, basically, as I mentioned, we offer the ability to lift this shift. Those applications has this into a cloud native environment, taking them, taking those applications running of our project and offering the logic environment as a container on top of our platform. So we developed an environment that allows you to very easily lift and shift those applications, as is using the exact same technology as you would in the past. On premise. But then in that cloud native environment and on the level of the project management team that is managing this environment, we now cover not only the logic and coherence. Coherence is in memory grids. That has been around a long time alongside with project. So you can lift what project and coherence through the cloud. But I would call them more existing on prem technologies. Alongside that, we are also introducing haling on a on is a Java library framework for micro services. And I do have a slide with more detail on Helicon just after this. On top of this, we have the Rosano and is a.. Is a application management, too, which actually is not yet out. So this is why I had to include a safe harbor statement. It will be released in the near future. I can't be more specific, unfortunately, but the Rosano will offer the ability to deploy both monolithic applications running on the project as well as micro servers, applications running Heldon or Docker environment. On top of Google need this. So combining this monolithic old style world with the new cloud native micro services style in one deployment mechanism is already good. What's even better is that very Zano also covers multiple environments. So it can cover both on premise as well as clouds. Clouds as in plural. Obviously Oracle Cloud, but also any other cloud where Kubilius resources are available where you could deploy these applications. So really a way to bridge the gap between the old worlds and that new cloud native world. Quickly going over the features that have been added to a logic to to enable this basically make it ready to run in the clouds. Make it open for defense leverage beneath. Need us to offer new models of high availability and make sure that the manageability of the environment is fully compatible with existing open source. Or I would say club native type of environments like using Farner, et cetera, for locking and tracing, using those same mechanisms, making the output of the project compatible with that type of effort. And then the ability to run both on premise and in the cloud on top of Supernus. I have one more slide on this. So basically the details of running our project on Google Nita's is done through the operators. An operator is a normal mechanism in cubic meters to deploy non-standard environments on top of that. So it's the operator will actually be in charge of spinning up the container that contains the project using your traditional deployment files as you would for any other application. In the interest of flying, because I do want to do a quick demo still, I'll speed up a little bit. There is more here. We can go into more detail. If you are interested contractors, we do have a imaging tool that allows you to design yourself the building of the docker image that contains the Web logic. There is an migration. Tooling allows you to very easily transpose a existing on prem environment to the cloud, etc. But I won't go any further with that. One last line before the demo actually to help them. So Heldon is our Java open source framework for Microsoft services. It is an open source so you can just download it and run it. We do offer support for the project paying customers and it's available in two flavors. So there is the S.T. Flavors, which is a declarative style of programming. Ussery a functional style of programming and the and there is the NPT, which is a micro profile compatible, which is an industry standard. And you can position it basically as opposed to the other micro surface frameworks in this or it's held on SD is really, really very light. It's actually a micro framework. An MP is a fully compatible framework with micro profiles, so it offers Java EE type of programming. And then, well, if you compare it to Springwood Springle, this is actually quite a lot heavier and I think that's the main differentiator headed on. Empey is much more agile and lightweight with respect to that. I did mentioned Grobin already. So maybe I don't have to spend too much time on this. This is really an alternative way of running your applications. It makes Java faster, a lot faster. It started time and in execution time. So, yes, you can. It is compatible with existing software like logic and coherence. And it allows you to basically also run other languages, JavaScript by Ruby, etc.. There's enterable interoperability between these languages on the level of the execution. Now, let's do a quick demo. What I have set up, and I'll point you to the left, to the location where you can see that lap, I think it's if you want to get a first. Feel of what it means to develop in this environment. You can follow that lab, I've set up a developer cloud environment, which we actually renamed my slide is outdated. This is now called Visual Build a Studio. Apologies for that. It's a drawing. So I need to redo my drawing. I use Visual Studio to deploy escudo to the database. I use Terraformed to actually spin up the infrastructure components, the database itself and the disgust. And I use the boot pipelines to. Package a note application into a container and then deploy that container. The cupboard needs better. So that's a lot. Let me show you how you get there. I'm going to go out of presentation mode now back to my browser. You go to my other window. So this is the protocol gets hot location. So get up. Come, Oracle. And then the key to remember is how to strike. So this is public information. And the lab that I'm going to very quickly describe you is actually this link here below. Micro services using autonomous ATP and manage containers. If you go to that lab, you can see there is a full explanation. Step by step of how to execute those steps that I just detailed. So, first of all, we're going to prepare your Tennessee. But actually, first you need to get a tenancy right, to get. You need to get a hold of a Tennessee so that you can just go to our free time. You will get access to that and you will get credit for one month to run that. Once you have that, you can prepare your tenancy and you can start executing the last steps. So. Let me very quickly show that there. Can I still have five minutes before the Q&A, can you please advise on the best way? Yes, I think it's relevant to show the demo part. OK. There are a couple of questions that I selected for you. And you have been chucked. I sent to you. OK. So I showed you the cloud platform. Now I'm gonna go straight into the developer part of that platform. I have a stake in that. That's why I'm opening a new window. And this is my development environment. What I can do is spin up a new project, define who will work on that project. And what that does is give me and I will open this project actually to show you that this is just a project that I used to show the environment. This gives me a great repository where I basically, in this case for a lot, what I do is I just upload a get repository into this GitHub repository, into this one particular repository. And then we start working on it, creating the ammo files for the for the deployment's, creating everything that is necessary. So here you have a stomached get you can do all the things. You can manage your requests, immerge requests. Push-Pull, you have your issue management so you can look what has happened with the issues that users bring back. You can manage your come on board. You can define sprints and stuff like that. But bottom line, the important stuff is that you can build stuff from here. And so basically what I did here, for example, the database creation build is populating development objects into the database. Straight out of your gate repository. So if I go into the configuration mode, I can see that I have set up my steps, built steps. I set up an escrow connection. And here I specify the database connection credentials. And I specify that I want to do the create schema script that is part of my get repository. So that will actually be triggers when I change this script. This I will be triggered. And another version of that environment will be made available in my database. So that's a first step in the lab. We will actually, in a manual way, use terraform to. And go to get your standard forum to spin up communities environment. Because from the practical purpose, I think it's better to do it that way. So if we go to the terraform, you will see there's a bunch of terraformed scripts. And the most important one is this. Who would need this one? Well, you see that I specify that I want to have a container of engine cluster. I give it a name. I specify some networks and I want to have a node, too. So these are typically the elements that you need to provide on the level of terraform to spin up a company discussing. So once you've got this and there's examples available, you can very easily with terraform spin up the company's cluster. You don't need to go through the GWI anymore. It will be done then. Ultimately, once your company, this cluster is up and running, you can then use the build pipelines to, for example, build the containers. Let me go in this pipeline. Build containers. Is my whole pipeline. Let me show you the type of steps that are in the pipeline. So basically, here you have you can you can run any unique scripts. I need to do something with some library that I have to download from a machine. I can do a doctor log in. I do. My doctor come out using the standard using this. In this case, the Docker file with this name. And then I do a push to my private registry. And once that step has been executed, the Docker container will be in my repository. On the other side of the of the here on my cloud. So this is my company, this cluster where I will depart. If I go here, I can go into my registry. And this is where I can see all the images that have been deployed. And I can. Who did what at what point in time? I'm just clicking on a few of them. But you can see what happened. My colleague Alarm was playing around with Project Image four days ago, for example. Right. So if you run Descript, this would like this pipeline. This will actually deploy your container into that. Go back, the other one that's interesting to look at is the actual deployment of the Cuban cluster. If I go to my deploy and I think this is my latest version, this basically is the script that allows to deploy my conflagration to my crew. We need this cluster. And again, if I go to my build steps, I can see what I'm doing. Again, I'm doing a Logan and I'm doing some running shell script that will actually run my Google Nita's setup for me. So if I go to my get repository, I can actually visualize what exactly I'm doing there. There's my I think I'm using I think this is my YAML file. Defining my application called ATP Tree. Defining the part that it will listen. No, Spinella could need this configuration. It's all part of my get repository. If I change something here, depending on the setup that I did for my build pipelines, it will deploy to that environment. And so with that, I think I've showed you the highlights in just one hour, I had to go real fast. And now we need to have some time for questions. So let's go there. If you open your chart, you have a couple of questions that I share it next and then we try to do that. My interface on this platform is a little bit. Slow to respond so they can check and nothing is happening. Maybe you can read them. I thought. I think that's gonna be simple if you read the question. Can I bring my own software like Jenkins' for doing continuous integration, INS delivery and deploy apps to Oracle, Cuban inmates and Gene? Absolutely, yes. Absolutely. That's the whole idea. So we do have this developing environment that does potentially a lot of the work for you, but it is at no. In no way a mandatory order or it is just the option to use if you want to use your own pipelines. As I said, we have all the interfaces to interact with that environment. It's a stunning lack of any cluster so you can deploy with it. You can run your scripts on a computer instance. For example, you can run your CIC, the environment on a thus on the on the cloud. You can run it on your premises. The only thing you need to have is connectivity to the right environment where you spin up that could rediscuss there. Obviously, depending on the security settings, you might have to be on your Internet if you have a private network that's only accessible through VPN from your corporate environment, that you can do that from the outside. But that is normal security stuff which you need to take care of. I would say. I don't have any other questions. Another one is, is Oracle Cubitt Aid Services. See NCF compliant? Yes, absolutely. We are a member. I think a platinum member of the SNCF. And we only use vanilla versions from CNS. And we are. I know there's some certification and so on. And yes, we are. Then there is this one. Do you have a blueprint to make great application to Oracle crowd? For example, say, a job application using SBN? J Developer Web Logic, Oracle DBE. We do have yes, we do have, as I mentioned very briefly, we do have a tooling to automate that migration. Now, it all depends on the type of deployment that you will want to do. There's a number of options that you have in terms of how are how far are you going to go? You can run Web logic as a VM on top of our cloud, which is the basic option, which is the closest to what you would have on premise, or you can run it as a or image. And in that case, you have a number of options. For example, you can package your application inside of the container, in which case you have a fancy ICD cycle where you deploy every time you make a change to your application and you deploy, you redeploy your full project and you can take a new replica container with on top that your application. Or you can choose to use persistent volumes whereby you build your application sort of at your word logic container that is then deployed on the cube of its bottom. And then you use the system volumes to do a more traditional way of updating your applications that are deployed on that virtual volume that the project can access from the containers. OK. There is also this. This one, I think is interesting. What if I need to work in a multi cloud environments? Yes. So we have a number of options for that. I think the most talked about is the connection with Microsoft. So we have a direct connection with what's the name, fast connect with Microsoft, which a lot with as your cloud, which allows you to really have a very easy and jointly managed on the level of security and identity management, et cetera, between the two clouds to have hybrid deployments in that way. The other way to look at it is obviously you can run a Google search in your cloud, you can run a company. This does not occur in other clouds with the Verizon or tooling that will come out that will cover exactly that use case whereby you want to deploy different applications on multiple clouds. And specifically for Web logic, for I would say traditional Oracle stock applications with logic is very much search. They're meant to run on any environment. We have some specific things that we will offer on the Oracle Cloud. You will get nowhere else. But from a technical perspective, it can run anywhere. I think the big differentiator is the billing mechanism. Basically, if you run on the Oracle Cloud, you can go for what we call a pay as you go. So only paper what you use. So you don't have to buy a license for a CPA that you're using, like in a traditional environment, that you will consume the web project license and the database license fee for that has a on a CPA for OCB per hour basis. So that means you can spin up a whole environment with hundreds of CPA use for just one hour to do a low test, spin it down again and pay a very small amounts because it's just one hour. Right. We're talking behind the comma number of dollars for these types of pricing. A CPA is zero point zero six a list price, a database. I don't know by heart, but the Web logic is zero point three dollars per hour. So even 100 Web projects for an hour is a thirty dollars. You're correct. Yes. So very flexible way of deploying. But as I said, a lot of this stuff is absolutely industry or open source industry standard and very easy to use across clouds. If that is your and if that is what you want to do. OK. Any other questions? I think that we are on top of the hour and so maybe we will go through the other question directly to the audience and the the people that might be. And so really. Just to close. Thank you so much to everybody. Thank you, Ian. OK, thanks a lot. So I hope this was useful. Let's check it out on our website. Go to the counties drive if you want to play around with this environment. And with that. The rest of the day.