Hi guys! Welcome back! As I told you in the last episode, we were just about to go live and as of today we've been running the solution for three weeks in Oracle Cloud. And everything is looking really good, user seems happy and we're getting some nice feedback. This is as you know a business intelligence platform that we have lifted and it seems like the loading times and basically all of the reports are running approximately 20 percent faster than it did before and that is without any heavy tuning being done. We still have some documentation and some glitches to take care of but soon we will be able to close the the project on budget and on time as it seems. For today's episode I thought we would elaborate on what happens next, I mean the Cloud manages itself doesn't it? Not really, let's go talk to Alexander Andersson and he will tell us how it works. Alex so great to have you with us, I know you've been through a lot the last six months within this project. Could you maybe tell us a little bit about what's important to think about after go live, I mean the Cloud manages itself doesn't it? Well not really, I mean it depends on which kind of services you're using. Some are more managed by the cloud vendor than others and some you still need to manage in the same way as you do on premise. But I mean, remember the cloud is basically as any data center it's just more scalable and flexible and dynamic. But maintaining your services will require some work yes. Okay, could you be a little bit more specific and talk about just Oracle Cloud and managing Oracle Cloud? Yes, so for example we have the autonomous database service versus the regular database service where the autonomous is basically patched and upgraded automatically by Oracle and whereas the DBCS service or the regular one is maintained by you as a customer but there are some good tools built in in the OCI console which is a web front-end for managing your services where you can do pre-checks you can do the upgrades also restore a backup if the upgrade should fail for example with all that you could do from the console. Okay and in regards to servers and compute nodes and managing those? Yeah, so the compute service which is actually the VM or bare metal servers where you run linux or windows on them yeah they are managed by the customer but also there you have some OS management capabilities built in in the console, where for example you could deploy security patches quite easily. Nice, so the project is basically done and dusted now, any lessons learned that you want to share? Yes I mean so the Cloud is moving in a rapid phase so it's easy to understand. I mean all the technical components that you're using understand what requirements or actually what the restrictions they have because depending on your requirements there might be some restrictions that you need to do some workarounds for, so yeah especially for autonomous database we have seen that. But yeah and all as always have good and easy to understand naming conventions because some services you can rename afterwards but some you cannot. And yeah, I mean for network security rules which are basically firewall rules, it's really good that you set the description because there will be lots of them and you will probably don't remember why you opened a specific port in a month or a year, so yes. So yeah, we forgot to do that in this project so we needed to try to figure out what it was about. Yeah it might have happened yes. Okay thank you for sharing Alex see you later bye bye!