Previous webinars
THE JOURNEY TO ORACLE CLOUD EPISODE 3
84 views
View transcript
Hi guys! Rafael here again. Well, today I thought we would talk about a topic that is often overlooked or forgotten and it's the topic about networking in the cloud so let's go talk to my good friend and colleague Daniel. Okay Daniel, so what is actually networking in the cloud? Network in the cloud is more or less the same as on-prem except that of course everything is virtual based, you start by building your virtual cloud network which is shown here, it's a K8s station for kubernetes. Within that you have your subnet, your routing tables, your internet gateways, your security lists and NAT Gateways so forth. Subnets is basically just a logical sign arrangement where you deposit your resources, your computes, your databases, what have you, then you have your routing samples which is routing in the cloud you have your network security, security lists which is basically a firewall where you define what traffic is allowed in and out of the various subnets and that great internet gateway is for internet connectivity whether or not the product is public or private and so forth there's quite a few things you need to keep in mind when building a network. Yeah okay but basically the same only that in the cloud of course it's service based. So this is actually something you start off with right when you move, when you are entering the journey to the cloud? Yeah, this is the foundation on which everything else builds upon, you need to get it more or less right since it becomes very complicated that isn't you need to have part you know basically how many ip addresses you have available in order to build your subnets in a good way you need to understand the security requirements your company have, in order to build a proper security and you need to know what you're going to connect to azure, on-prem so, yeah this is the very basics one everything else is built. Okay so to summarize, what is the top three things to think about according to you? Like I said you need to understand the requirements of the projects or clients basically, what do they have right now, security wise, scoping wise etc. You need to start early with this, this is the very start of the architecture so that needs to be played before anything else can be built and you need to think a bit forward, because thinking a bit forward making it the right size and that will simplify, you can expand later on, but it might become more complicated so those would be the top three ones I think. Super thank you Daniel!