What if the admirals chose to become pirates instead of marines? Imagine how different the series would look if instead of forming the world government's greatest military force, these powerful individuals decided to join the race for the One Piece, which one of them has the highest potential to become the pirate king. Well, at least for one former admiral, we already know what would happen. Akainu's mago mago no mi is said to have one of the highest offensive powers among all the devil fruits, and Akainu is already a proven leader, steadfast in his pursuit of absolute justice, and is the only one confirmed to have defeated a fellow admiral. As a pirate, he would undoubtedly be as ruthless as he is now, and as relentless as we witnessed in Marineford in his pursuit of ace and loofy. Akainu or Sakazuki had a rather rough upbringing, a scene when he was drawn as a child with his ragged clothes and the young boy holding a knife, meaning that we can count on the fact that even if he didn't pursue life in the Navy, Sakazuki would be just as ruthless, if not more, without the authoritative restrictions that the Marine institution imposes. In fact, if he was a pirate, Sakazuki would probably have the highest kill count in the series, killing any pirate, marine, or even civilians that gets in his way. His brutality as a pirate could earn him a reputation as the second coming of Rocks the Zabeck, while being involved in legendary rivalries against other big-name pirates. He might even end up being the most infamous pirate of his generation, sandwiched between Roger and Shanks' respective eras. According to one-piece author Echiro Oda, the current fleet admiral Sakazuki is so strong that if he were to become the protagonist of one-piece, the series would end in just one year. I mean, just imagine if you replaced Luffy with Sakazuki, and he took the same path Luffy did in the original timeline, pacing off against Luffy's past opponents, we wouldn't even need a time skip, and Sakazuki would just breeze through all the necessary steps to find the treasure and end the series early, leaving the rest of us very depressed without one piece to watch. Okay, so that's only one of the admirals, but what about the rest of them? Before we get into all the other admirals, make sure to salute and subscribe if you'd like more one-piece videos. Now let's look at Garb, who although was never an official admiral, is powerful enough to have even become fleet admiral if he didn't refuse the promotion to rise above the vice admiral position. As a pirate, Garb would definitely have the most fun and interesting journey, especially being of the same era as legends like Roger, Whitebeard and Rocks. He fought these men as the marine hero, but imagine the chaos of these legends fighting over each other's booty. As a child, Garb is the embodiment of an adventuring kid who would tame monsters along the way in search for treasure. Remind you of anyone? Garb is literally Luffy if he decided to become a pirate. If you look at how Garb was drawn as a child, you could even say he kind of looks like a joyboy, and is someone who also carries the will of deeds. Garb would most likely be Roger's closest competitor when it comes to finding the hidden treasure that would later be known as the one-piece. The two would be involved in a fun but extremely intense rivalry, where Roger and Garb would constantly butt heads and clash one minute and then party till the sun comes up the next, before vowing to beat one another in their race to claim all the world's treasures. In fact, having shared the ocean with the rest of the great pirates in his generation, Garb would have likely developed rivalries with both Roger and Whitebeard, while also being on fairly good terms with each of them. A temporary alliance over a common cause is also not out of the question between these three legends in a similar way to what we've seen of the Luffy kid and Lore alliance at Wano. I can imagine Rox the Zepek would have likely been the one to play the role of an evil that must be toppled down figure that Kaido played at Wano. And I can't think of anything more exciting than seeing these three legends fight side by side. But if Garb was a pirate, it would be a massive blow to the Marines, not only because they would lose arguably the strongest Marine in history, but Garb as a pirate would inspire many other people to follow in his footsteps. In a similar way Roger did in the past and what his grandson Luffy is currently doing. Garb is definitely the most protagonist-like character on this list and the Navy struck gold that Garb chose to become a Marine because had Garb decided to become a pirate, the One Piece world may be completely without Marines at all. And before we get into the rest of the admirals, a big thank you to today's sponsor Filmora.  Filmora is a cross-platform video editing tool available on Windows, Mac and mobile so that you can create videos quickly with ease with a ton of built-in editing features. Filmora is also launching AI features such as speech to text or text to speech meaning that you can create videos without even recording yourself. For example, this is Batjoy Girl saying, Hello, my Nakamotachi, or how about in Japanese? It has AI Portrait meaning that it's even easier for me to transport Luffy into different settings such as marriage or smart recommendation where Filmora will offer you with personalized recommended resources that's specific to your video. And this is just the beginning. There is so much more to love about Filmora. With loads more cool features, you definitely gotta give it a try. So make sure to use the link below to download Filmora now. Making your own video has never been easier. Kuzan or former Admiral Aokiji is another figure we don't just have to imagine what would happen if he became a pirate but it's rather more of a case where we're just gonna have to wait and see through his future actions because Kuzan is currently a member of the Blackbeard Pirates.  First of all, while the admirals are powerful enough to travel by themselves to handle strong and powerful opponents as a pirate, this idea could not be any truer than when applying it to Kuzan due to the power of his devil foot. Kuzan would have the easiest means to navigate the wide ocean even without a crew. But if he is a part of a crew, Kuzan would more than likely become the reluctant captain of a pirate ship just because of how powerful he is. But I think a more fitting role for him is to be another strong pirate's first mate. And since we've already mentioned Garb being the captain of his own ship, imagine Kuzan being Garb's second in command, making Kuzan one of, if not the strongest vice captain in the entire series. Regardless, any pirate crew Kuzan decides to join would instantly have an advantage in navigation over other pirates as well as having a reliable combatant in their ranks. Travel-wise, Kuzan could just freeze the ocean so that his crew could go wherever their destination is. Although ideally this would require the crew making significant alterations to their ship to accommodate them being able to travel on the ice road that Kuzan would create. But if that sounds like too much of a big task, Kuzan could just shield his pirate crew's ship with ice walls to safely travel the seas, which also sounds perfect when escaping from anyone chasing them such as the marines. And as a fighter, we've seen that Kuzan is able to take on an entire crew by himself. So just imagine the damage he could cause as a pirate without the moral ground and code to follow as a marine. The only mercy other pirates would receive is if Kuzan decides not to go all out because his laid-back nature gets the best of him. Kizuru is the only one out of the original group of admirals to still hold his position and his calm and easy-going demeanor is a trait that he shares with some of the most likable pirates in the series. Seriously though, this man is perpetually calm. He's probably the most prominent admiral in terms of how many pirates he's been shown to deal with in the series. He easily defeated multiple supernovas at Saabodi and captured 500 pirates before leaving the island. He even looked good against Whitebeard and managed to give him a serious injury. Based on what Sentomaru calls him in the series, if Kizuru was to become a pirate, he would most likely have a Yakuza-themed pirate crew much like a stronger version of Beja's mafia crew. Similarly to Kuzan, Kizuru would also have an advantage in terms of navigation. Even he's able to travel from one distance to another at super speed. From what we've seen in the use of his devil fruit, he could potentially jump his way from island to island, landing on ships in between to even completely taking over weaker pirate crews or just completely wiping them out depending on if he's feeling murderous that day or ransacking through unlucky marine ships traveling the seas. On top of being impossibly strong, Kizuru is also hinted to have a high level of intelligence. As a child, Kizuru was shown to be a studious little boy who spent his time consuming knowledge as suggested through the stack of books next to him. So don't be surprised if he's later revealed to be adept when it comes to science and technology that is sure to be beneficial should he have decided to take the path of piracy. In fact, as a free sea traveler, Kizuru may have even become a part of a different group such as the now defunct science group Mads making him the unquestionable strongest member of the group which is actually very fitting given he is the exact same age as both Vinsmoke Judge and Queen completing the Yellow Trio. And on top of this, with this brand of unclear justice, even outside of the marines, this code seems to align with the very ambiguous science group being once the laboratory for peace but then also being filled with members who have gone on to do things that are very far from peaceful and if he were to join the chase for the one piece Rosalino the Yellow Monkey would be a problem for anyone who gets in his way although I doubt he would be visibly devastated if he doesn't find the treasure but either way he is a terrifying figure when it comes to both brute end brains Admiral Ryokugu or Aramaki the worst of the bunch take away his great admiration and devotion to the world government and to the world nobles and then Aramaki is perhaps in the traditional sense the most pirate-like out of all the admirals so flipping his ideals to make it more pirate-y Aramaki would more than likely idolize the likes of rocks the Zabek Zabek being the epitome of what a pirate is in a similar way to how Ryokugu admires current fleet Admiral Sakazuki with his code of justice being deadly justice this could translate very well to a life of piracy and with his unique devil fruit powers making him extremely strong on top of his idolization of Zabek Aramaki would likely be leading an evil pirate crew that was fulfilling the will of Zabek long before Blackbeard ever started and Aramaki seems to be a balanced mix of impulsive decision making as well as recognizing when he's out of his depth as seen when he decided to infiltrate Wano against Sakazuki's orders but then backing down when he came across the red-haired pirates alone so this is already one similarity he shares with Zabek's seeming follower Blackbeard and if he surrounds himself with like-minded evil pirates as Blackbeard did maybe even Blackbeard himself then they're sure to spread terror and shake the world of piracy Fujitora is the closest thing to what true justice represents and perhaps the most ideal figure to represent what the Marines should be being one of the straight-up good guys he cares about common citizens showing the highest respect for human rights than we've seen of any of the other admirals and these ideals make it difficult to imagine Fujitora or Isho as a pirate but if he were to be one Isho's human justice translated to piracy would make him one of the good pirates he would have a scary reputation due to how powerful he is his strength only matched by his compassion for others the closest comparison to what his ideal pirate career would turn out to be would be Whitebeard as a pirate who looks out for regular people and offers his protection to many different weaker islands in fact if Isho decided to become a pirate instead of enlisting during the military draft I can imagine him gathering like-minded crew members and feeling the role that Whitebeard played after the Yonkou passed away which would have a lot of implications such as Jinbei never needing to join Big Mom's crew but that's another discussion of its own Isho with his physical strength and swordsmanship alone would be strong enough to deal with a number of pirates on the sea just one attack from his devil fruit ability is enough to sink multiple pirate ships or any marines chasing him down to the bottom of the ocean he may even play the role of ally to the Straw Hats perhaps a scenario where the Straw Hats and Isho started off as enemies but later come to the conclusion that they're both here to protect the island therefore forming a temporary alliance where after their victory Rufi and Isho would argue over whose protection the island would fall under and although he would more than likely be everyone's favorite frontrunner to claim the one piece I bet he would be more than happy just as long as the people are protected Sengoku is probably the hardest X admiral to imagine as a pirate he has shown dedication to being a marine so applying this to a career of piracy would instantly make Sengoku one of the scariest pirates to deal with in the series while he may be a fleet admiral within the marine this leadership position doesn't necessarily have to be the case should he choose to become a pirate upholding honor and logical thinking I can imagine Sengoku to be a very reliable first mate being an individual who could very well be captain of his own crew if he so wanted but instead playing the role of someone who is able to steer the captain straight when the captain loses his way like Zoro does to Rufi or being the disciplinarian of a crew similar to what we've seen of Rayleigh and if we have the ideal scenario where both Garp and Sengoku are pirates I could see their positions reversing with Sengoku now being Garp's right hand man making them an almighty duo that is perfectly poised to finding the one piece and crowning Garp as the pirate king but regardless of who ultimately finds the great treasure there is no doubt that each of the admirals or former admirals or could be admirals would have bounties that range in the astronomical amounts that we've seen of the Yonko throughout the series most likely each of them becoming one of the Yonko in their own right and having great rivalries amongst each other and with the other legends in the story if the marines don't recruit powerful navy soldiers to rival these legendary pirates then the one piece world would be nothing but a lawless ocean filled with monsters but what do you think? what do you think would happen if these admirals became pirates? let me know by leaving a comment below don't forget to like and subscribe thank you to all of our patreon and channel members and thank you to everyone for listening to another one of my rambling this is Joygirl and I'll see you again soon


Hey guys, welcome back to my YouTube channel. This is Daniel Rosil here and I'm doing an experimentary video today. It's going to be called Beer and Backup. Now this is not my idea. This is, I'm robbing the creative idea from the Restore It All Backup podcast, which I'll presently be introducing. It's one of my favorite podcasts. It's the best of my knowledge, the only podcast that really dives deep into the world of backup, which is one of my long-standing tech fascinations. I'll put it up on the screen there, a couple of things. Firstly, I was on this podcast about a year ago, maybe several. It's corona time. What can I say? It's all a blur. But I was on there at some point, episode number 74, talking to Curtis and Prasanna. I think this is actually one of the first podcast interviews I ever did. I had a great time on the show and they described me as a self-described backup anorak, which I remember Curtis got a great laugh at it because he never had come across the term anorak before. I think it's a British term and growing up in Ireland, you borrow a lot of slang from the Brits. So it means it's a kind of tongue-in-cheek word for someone who has a goofy interest in a very niche area, kind of a, I guess, a ham-hack. I'm trying to think of other words for anorak. You get the idea and certainly backup fits that criteria. There's nothing cool or sexier, glamorous. Even within tech, it's probably the dullest field. And yes, folks like me, Curtis and Prasanna, are fascinated by backup. And I'm going to try to touch a little bit on the psychology of my private, up-to-now private theories about the psychology of that in this YouTube, whatever you describe this, ranting process, or me talking to microphone in the late hours of the evening. So yeah, that was my episode. And if you want to hear me on the podcast, check out episode 74. There was, but here's a podcast itself. It's an absolute gem of a podcast. There's very few podcasts I've actually really stuck with over the course of time. Most are kind of, there's a lot of mediocre podcasts out there. This is a great podcast. It's got a lot of fans. They put out 158 episodes. These two guys, W. Curtis Preston, who's like literally has written the book on backup. And that's actually like literal. He's literally written the backup textbook. And he does a podcast with a friend of his called Prasanna, Molly Andy. And they used to work together at Druva. Now Prasanna is going to go on to Zoom. So Curtis and Prasanna ever listened to this YouTube video. They know I'm actually keeping tabs on the podcast. And they've done some really great episodes. They did one where they interviewed a Hollywood guy and he talked Hollywood studios do backup. Backup is really interesting, guys. I'm trying to sell it. It's a great jumping off point for learning about enterprise tech storage and all these admittedly unsexy fields. They talk about LTO. They've got a few episodes on tape for those who know a bit about backup. And it's really entertaining. They do great interviews. And if you're into tech and especially if you're into backup, this is like Nirvana, this podcast. It's like listening to people who actually get backup and care about backup. I went years without ever meeting another backup fiend before I discovered this podcast. So what I want the topic, the actual topic of this video blog is going to be the sorry state of consumer backup. So because I'm going to be uploading this after my beer, I have to get this straight backup and beer won the sorry state of SaaS consumer backup. That's going to be the title. So yeah, I just want to talk about that for a little bit. Like consumer SaaS backup is pitiful. Let's take a step back. And this is the way I want to frame this discussion. So if you get up in the morning, your average person pulls out their phone, they check their email, they check their Facebook, I check Reddit, YouTube, going through the things. And as you begin going about your day, my contention would be that the average person actually creates more data natively and that lives natively in the cloud environment these days than they do locally, right? What do you do on your local computer anymore? Most people, I mean, I'm looking at my desktop open in front of me here. I do my video editing on the local computer, probably like I'd say almost everybody because video editing is one of those things that is quite hardware intensive, RAM intensive. And it's really actually a bandwidth problem because to do like video editing in the cloud, there are a couple of cloud video editors, but they're just not not anywhere near as good as the desktop ones, right? My wife is an architect. CAD is another thing that's really, really heavy in terms of the data that's involved in doing architectural renderings and stuff like that. Or if you're an engineer, whatever. And it's actually a bandwidth issue rather than a cloud issue. I don't think it's the case that these applications couldn't be deployed as cloud native SaaS applications. It's the case, so let's say I shoot five gigs of video and I now need to edit that video. So, okay, if it's going to be a cloud backup application, I need to first upload my five gigs of video to the cloud. And what happens if I have my real lovely two megabit per second internet connection, it's going to take me six hours to get my clips just up to the cloud, then edit them, then publish them. Once I've done the editing, I could publish cloud to cloud. It's beautiful, but there's a constraint in terms of and that's the same for CAD files. So, it's actually an internet problem that the internet needless to say is there, but we don't really have universal, this would be my contention, high-caliber connectivity needed to really take cloud computing to the next level. I'm certain it's going to get there, by the way. Here's my prediction that in five years there's going to be almost nothing that actually lives in software. There's this concept called edge computing that kind of didn't really ever get a lot of traction. This idea that computers would be super lightweight, terminal 3D, almost like a Chromebook, like very, very lightweight operating systems, almost like what I'm using for the last 10 years, actually, which is LXDE Ubuntu. It's a really lightweight Linux version, and I do basically nothing on it. I just use it for video editing and Google Chrome, and that's all I do at my desktop. Everything else is I'm creating data in the cloud. Anyway, where were we? Your average person these days creates data in the cloud from the moment they get up in the morning passively or actively, right? Passively, I mean that you open your Gmail and you start getting in emails from your boss, from your co-workers, whatever, attachments, and let's see some of that data might be really important, so that's data that you'd ideally want to be backing up. Let's go to active data creation. I'm going to just pause momentarily to actually do the back-up and beer element of this. Heineken at the end of a long and sweaty conference day in Tel Aviv, nothing better. Let's talk about data creation now, so you respond to your co-workers' email. If we break that down from a technical standpoint, let's say you're not doing anything fancy, you're just using the stock Gmail app, right? The stock Google Mail app on an Android phone and you're writing an email. Now, what's just happened on a technical level? Well, you've created some data, so where was that data created? It's the best of my understanding, the Gmail client or any really webmail clients. They don't work like if you've desktop clients that still exist, but not so many people use them. Mozilla Thunderbird on Ubuntu and I even forget what the Windows one is called. It's been so long since I used it. If you remember those, you did your send and receive and they pulled stuff down from the cloud onto your local computer and you could actually see the directory where all the email is restored, whatever. In a webmail, that stuff is native to the cloud. It's not actually touching your local machine at all. So when you open your Google Mail and you read an email, let's just keep it simple here, and you hit reply and you write some text, that webmail client, that email client, the Gmail client for Android is just a front end to the web interface for Android. You're creating your data there, so where is that data being created directly in the cloud? It's a cloud native application. You're not creating it locally, then it's bouncing up to the cloud and there's a local copy. You're just creating it straight in the cloud, recipients reading it on their Gmail, they're reading in the cloud.  That's staying on Google's cloud and the recipient's just reading the data live on the cloud. So that's cloud native data. Now, that really simple example of an email which can be taken much, much further. So you send your email, then you go on to Reddit and you comment on a few Reddit posts or you post a couple of posts on Reddit. What's happening when you're going on Reddit? Well, you're accessing Reddit from, let's say, the desktop.  What's just happened there? You've created data that's being stored in wherever Reddit's hosted on. We could go on like this, talk about Facebook, LinkedIn, blah, blah, blah. Now, the problem that occurs is this. You're going about your day, you're reading emails, responding to emails, you're posting a bit on Reddit. What else might your average internet user be doing on a day in terms of data creation? I don't know. You post a YouTube, a YouTube video, you leave a comment on someone's YouTube video.  So we're going through our day as your average consumer and we're actually continuously creating data if you think about it.  Even then, I would argue the pool of data that's in the cloud that you wish to protect might still be growing completely passively. The example I used before was your colleagues emailing you and stuff you'd want to be backed up. Now, where is the problem here with this cloud native thing from a backup perspective? The problem is that the cloud is not backup. That's your primary data source. The cloud is amazing. Cloud computing is fantastic. As a long-term Linux user, that's actually the reason I've been a cloud supporter from day one because back when Linux compatibility wasn't great, the cloud is great. It doesn't matter whether you're your co-workers on Mac or your co-workers on Windows or they're also on Linux, everyone can work in something like Google Workspaces. You don't have to worry about the operating system for each person. So that's the cloud's amazing. This isn't critical of cloud at all to the country. This is just saying that the cloud is not backup and the cloud is not enough. So when we talk about backup and I've talked about this before, the best practice and backup, the long-standing best practice recommendation is 321. The 321 rule means you want three copies of your data. That's the original data and two copies, two different storage media and one of those off-site. Even though I'm sure I've covered it already in a ton of videos, why does the 321 rule exist? Why do you need two different backup copies? Well, you need one on-site copy. So let's just go back to the cloud. You have a ton of data in your Google Drive. Now why is the cloud not backup? Okay, because that's the most common thing, right? If I don't really talk about backup to anyone in real life except my long-suffering wife who has been subjected to probably way too many hours of me mumbling about backup, but if I told my friends, guys, I'm burning M-discs, this crazy storage technology, why? Because I want to back up my Google Drive and they're like, why would you need to back up your Google Drive? Your Google Drive's not going anywhere. And that's what people think and it's a problem because it's not correct. There's a few things that could happen to a Google Drive. Firstly, Google's a SaaS provider, right? They're not a benevolent entity that has your data. I'm trying to say this, I'm saying like a conspiracy theorist because that's not the point at all. The point is that Google is a third-party company. They're holding your data. And if it's a premium thing, a premium product like Google Workspace, they'll hold your data as long as you pay them to hold your data, right? So that's the first thing. It's an external party and you don't know, even though, yeah, a SaaS provider, Google's not going to vanish from the earth tomorrow along with your data, but a smaller SaaS provider, crazier things have happened. There've actually been some pretty big data losses. It has happened. There's a few other things that can happen. You can find a vendor lock.  This happened to me recently and the cloud provider can change, move the goalpost. Well, you're 15,000 that were free data.  I don't have 10,000 bucks. So there you go. Your data was in a cloud. You thought your data was safe. Suddenly, you may not be able to afford having your data in the cloud. What else can happen? Here's another more perhaps credible scenario, ransomware. Increasingly, cloud services are interconnected. Everything's integrating with each other part of the cloud, which is again, very good. But it, from a cyber security standpoint, does pose a risk in that, let's say you integrate your Google workspace with a SaaS app that turns rogue and has read, write permissions. It can wipe. It could wipe your whatever inbox, calendar, YouTube, all of them, right? That's not unprecedented. That is actually a real threat factor. What else can happen? User error. And this is the thing. People assume, well, you can't, if I delete my Gmail data, YouTube has, Google has a backup. No. If you read the fine print of AWS or B2 or Google, any major cloud provider, you will see that security and backup is the user responsibility. And this is literally, I've seen it happen. I worked at a company once where people are into Linux, excuse me, this is probably doing a beer and backup thing when I'm a bit suffering from, suffering from bloating as they happen since my gallbladder surgery. Linux geeks are very familiar with the, you know, joke that says, oh, I just did an RF, whatever it is, RM minus F asterix, and it's the command to delete an entire file system. Like the intern types this into the root of the server, and your server is completely finished, right? That can happen in Google Drive. And I literally seen it happen. I've seen someone who wasn't so tech savvy, let's just say, accidentally delete the company Google Drive, then someone deleted that from the trash, right? And that's, that trash, that is literally the safeguard that there is no other safeguard if you use Google out of the box, let's say Google mail or Google calendar, you can create your own backups 100% restoring them is another issue. But that's what you get. That's your safeguard. It's totally possible that someone will delete all the company Google Drive, go into the trash, and someone says, oh, let me try restore.  Boom. Two seconds later, your entire company's drive is gone. And you'll, you'll contact Google, you'll say, hi, you have a backup right of my Google Drive. And they'll be like, nope, we do not have a backup. They might have a backup, but they, there's a difference between backup and restore. They may have a backup that they will not restore for your average consumer, maybe for an enterprise, they'll have some kind of backup plan. But you say, please backup, they'll tell you to go jump in a lake. So those are the reasons why the cloud isn't backup. Nothing wrong with the cloud. It's just one data source, like having all the cloud is someone else's computer. From a backup standpoint, the cloud is just about as good as having all your data on an NAS in your house, right? The cloud has redundancy, it's professionally managed, beautiful, beautiful, beautiful. But it doesn't equal backup because backup involves risk protection measures of having your data in one place and then having it in two other places. One of them is, one of them is offsite and why is one offsite?  So I always want to have that fail safe of we have a backup here. And just in case there's a tornado strikes or some other disaster and our onsite and our primary are both destroyed, well, we have that backup to fall back on. I just noticed my levels are a little bit high. I saw some clipping from my audio interface. So I'll try to stop shouting here. Where were we? So yeah, that's why the cloud is not backup. Now let's just roll back a bit to the start of this talk, when I was talking about how much data your average consumer creates, not even a business user, but also a business user. From the moment they get up to the moment they go to sleep, they're sending emails, they're posting on their social media, they're tweeting, they're editing, they're YouTubing, blah, blah, blah, the whole thing goes on, right? Now how much of that data can be protected from in a backup three to one backup compliance standpoint? The answer is actually really, really little. I'm just going to pause here for a moment. The answer is very, very little. There are enterprise tools intended for businesses to backup Google Drive. There's actually even consumer tools. If we take the Google workspace, Google is a big ecosystem, right? If you're even your average user and you're not workspace on a free Google, you just have Daniel at gmail.com, whatever, and you start creating data in the Google pool. You start labeling your friend's house in Google Maps. You create a little list on Google Maps. You create a custom Google Map. You start putting stuff in your Google Drive.   It's very far reaching and you may forget that, oh yeah, Google Maps is part of my Google footprint. It's all connected to that gmail account, right? So even the products like Synology's backup platform, Clitesync, which is a nice decent product and there is a different product for Google workspace for paid Google users, it only gets kind of the core of that stuff. The stuff that your average business will care about, Google Drive, email. I don't think email is even there actually. So in a backup, in a normal functional backup strategy, you want a few things. You want three to one. You want automation because no one really wants to be thinking about backup. You'd rather be doing the beer aspect of this and the backup aspect or most normal, rational thinking people would. You want to be automated. You want it to be three to one compliant and you want it to be either differential or incremental. There's three different backup approaches that you can do a full backup, which means every time that you take a backup, you duplicate the whole shebang, right? That would mean like Google takeout. If anyone's familiar with that, it literally just pulls down the whole Google and that is very inefficient because when you're talking about a big data, I'm going to turn down the output level a tiny bit on my interface.  So good backup approaches, you have differential which takes a full backup then looks at the changes, the positive and negative, the creation and the deletion and moving the file structure around since that point in time, registers that and then creates a little file that's your differential backup and then incremental, which is a series of little slices. Each time from the last incremental, it writes the changes to the file structure and then if you need to restore, you go like this. If I can use my hands, you put the chops together versus differential where you have to put that whole, the slices are bigger if you want to think about it like a pizza, right? You want to back up your pizza. A full backup would mean we copy the pizza, the whole thing, but every time you back up, you end up with a whole another pizza.  Incremental backup would be you took a caper and an olive off your pizza and the incremental backup, the first one, we record that the olive was taken off the pizza. The second one, we record that the caper was taken off the pizza and if you screw up your original pizza, we go from the backup pizza. I never thought I'd explain backup by reference to a pizza and capers, but there you go guys. What a day this has been. So anyway, so even Google, even the few backup products are available and by the way, you have to make a confession. I had an idea a few years ago to actually start a startup here in Israel, a actual consumer backup startup that would be the Swiss army knife of consumer backup. It would try to integrate with Twitter, Reddit, blah, blah, blah, blah, everything your average person. Asada, project management Monday.com, Todoist, Wunderlist, it goes on and on.  I would imagine a lot of people come up with like 20, 30 products. I use my as a freelancer, my accounting platform, my receipt generation platform, my billing platform. It's all SaaS, it's all living in the cloud. So yeah, I had an idea and then I realized, consulted with some business coaches on the idea and I realized it was actually not a good business idea. A, running a backup business would probably be pretty boring. Secondly, there just isn't demand because most folks, most consumers are not as paranoid as me or are not as backup. Woke is me. They say something backs up to the cloud. Beautiful. I don't need to worry about it. Most people don't care about backup. Enterprises care about backup. So the consumer backup space has been kind of left untouched. What do we have in consumer backup? So really, so you have the big data pools, Google workspace, Microsoft 365, whatever it's called. I don't use it. So I'm not sure what it's called, but you know, Microsoft's competing cloud offering. Some companies have developed solutions that will do some kind of backup on these. But again, at least just touching by Google, they are not from my standpoint, not sufficient. They do not capture the full typical imprint of a user on Google's cloud. Now let's just talk, let's talk about more, more, more sources instead of repeating names. Medium.com. I used to blog a lot on medium.com, right? So for stuff like that, that people don't really expect people to be backing up their stuff. Or, you know, the SaaS providers, Medium is a SaaS. It's a CMS that lives in the cloud and you just go in and create your blog. So what do you do?  Now, Medium is typical of what I'd call a backup provider, sorry, a SaaS provider with almost no useful backup functionality. And medium.com would say, Hey, what do you mean? We have backup. We have a data export functionality. User is going to export their own data. Sorry, that's not backup. Firstly, if we're talking in backup terms, that's a full backup. That's the least useful backup from a backup standpoint. It's very inefficient. That means every time I want to back up Medium.com, I need to pull everything down, everything down, everything down each time. Secondly, if you go into the, if you actually go into the backup and I talked about this before, on Medium, I posted about, I was chronicling or maybe GitHub, I think I posted on GitHub, talking about more SaaS GitHub, code repositories, stuff like that. I posted about in before, if you actually look what you get out of Medium.com, you unzip, you take a look, most people again would stop here. They'd say, Oh, great. I've got some kind of a backup. I don't need to worry about Medium. You actually go into the HTML files. They don't give you the images. It's HTML files, hyperlinks to the images that you've uploaded to their cloud. You don't get those in the download. So unless you're manually going through each link, one by one by one by one, pulling them out of the cloud, I'm sure there's some way you could do programmatically. That's not in the backup archive. So the picture that I found is that there's basically the only, so these kind of data export functionalities, which are probably not even intended for backup, they're probably intended for people, deep platforming, leaving a SaaS to go to a different offering. These are not, these are not backup functionalities. These actually only really exist for GDPR compliance or compliance with other data protection instruments. The GDPR, and if you look at Reddit's data export approach, you can google, how do I back on my Reddit account? You'll finally get to some knowledge article in Reddit's Zendesk, and you'll see there's a data backup request form. You need to actually manually complete the form, get someone to Reddit. I don't know if it's automated on their site, but let's just say it's not. Someone at Reddit needs to actually pull out your user archive. That's not, that's totally on backup friendly. That's not automatic from the user side. You have to manually complete a form every time. So hence it can be automated. B, it's a full backup, as we've discussed, which is not great. And that's probably it. So basically what we have today in consumer SaaS backup is actually, if you put those two things together and I realize I'm coming up to 30 minutes here, so I probably try to wrap up this beer, wrapping up the beer so that I can wrap up the backup banter. So the system we have today, put these two facts together. We're creating more data in the cloud, or most people are, I would contend. I just got some message in OBS about some encoding being overloaded. Never seen that before. Hopefully the video is coming through okay. We're creating more data in the cloud than we're getting through our local system. And we have very little in the way of actual viable backup for consumer SaaS out there. So most people currently, and I used to for a time, I can actually wrap this video up because I'm now worried that this is going to be completely unusable. Most people now are committing every single day, the majority of their data to the cloud, and there's no way for them to actually back it up in a viable way, unless, and this is what I used to do, you set yourself reminders, hey, on the 30th of every month, I'm going to download my Reddit archive, I'm going to download my Twitter archive, I'm going to download my Facebook archive, download my LinkedIn archive, you go through service by service by service by service, writing, completing forms, using data export tools all manually.  So you could do that. I just gave up on doing that because it was distracting. And you just have to say, at some point it does not exist. There is no right now at the time of writing, no one's come up with a really, really robust consumer SaaS backup tool. And if you compare this to, excuse me, the enterprise backup ecosystem, it just does not compare. Why do I care as much about backup? I'm going to wrap up with this. My wife asked me, why do why do us backup folk? Why can we only open up about our backup love sometimes over beer like Curtis and Prasanna? I think it's because we're deeply ashamed of our love of backup. We realize it's the most pathetic area of text. And yet we know it's super important. For me, I think it's probably, it's probably a combination and I suspect for a lot of backup people of two things, one being into tech, I think that's a given if you care about backup, be probably having a predisposition to anxiety, because people's anxiety are not able. One of the features of anxiety is that we can't tolerate uncertainty. We crave absolute facts. And in backup, there are no absolute facts. It's about risk mitigation. And the cloud from backup standpoint today is actually a pretty risky environment for your consumers.  You hope they're doing backup. You hope if something goes wrong, you can get it out. You don't know. There's no way you can actually create a robust backup plan. So if you actually learn about backup, you'll actually drive yourself crazy thinking about how bad the consumer SaaS footprint is. I want to just finish on a personal note. Why do I care about backup? I don't really finish that thought. For me, it's that I've seen, I've had a data loss disaster before.  And I've seen what happens when you spend a year tinkering an operating system on Linux, only for the hard drives to catastrophically fail. I've actually experienced this. And the last year of your coding goes to waste. And then you say, I better learn about backup. So that's number one. That's on the negative side. On the positive side, my late grandfather, Aloha Shalom was the custodian of the Jewish records of the synagogue in Cork in Ireland. And he, as part of that job or function, you know, held on to data, literally physical books from literally the 19th century, like burial records, wedding records. And we got them digitized and something anyone who's sort of done it for an archive and then sort of some kind of archival process for a museum or for a religious organization or for a government department. There's an amazing feeling when it comes to actually storing historical data. It's a very satisfying feeling, taking a chunk of history and making sure that it's robust because paper in some ways is actually more robust than bits and bytes. Storing digital data can be surprisingly brittle. I didn't talk today about bit rot and cold data storage, but that's the problem I've talked about in my M disc videos. And sometimes when you do manage to do it right, when you learn about backup and storage, and you get a request from someone looking for the burial record or the wedding record of their great great ancestor, and you're able to pull that data because you protected that data, you've digitized those historical records, you've backed them up, they're safe, as safe as safe can be. It's an amazing feeling. So I've both lost data and I've gotten to appreciate through just personal tech experiences the value of data preservation and digital archiving and all that good stuff. And I think it's a really important feel. It's just again, maybe just because I'm anxious, it's a part of the tech world that's always attracted to me, albeit, yeah, it's not glamorous, it's not cool, but it's so important. And arguably, I would say, never more so than the cloudier. The cloudier is amazing. It's made all our lives better, but people far too many people, even I include inside, including this bracket, IT professionals, just haven't thought about this aspect of the cloud. We mistake redundancy with a valid backup approach. We say the data is available, it's great, my Google Drive's always been there, therefore that is backup, and it's not. So that's where I will leave it for my inaugural backup and beer episode. I almost made it through my beer. I might do another one of these, if there's video interest, anybody, because I probably do have more thoughts about backup, just kind of tinker around the back of my mind, but they'll come out in the next beer and backup episode if they are to come out at all. Thank you guys for watching this video blog. I don't know, whatever this was, this bits and bytes that have floated onto the internet. And if you want to get more videos, subscribe, but if you want to do that, subscribe using the not the all, subscribe, the recommended, because my videos cover a boatload of topics. If you want to get the YouTube algorithm to help you out to see content relevant to you, that will work well. Thanks you guys for watching, and until the next video.


Hello. Hello, Oliver. Tom. Hi, gosh. Hi, Tom. Good morning. Good afternoon. Good evening. I think we have all time zones. Right now. Hello. Hello, Taylor. Good morning. Give it another minute, Tom. Yeah, sure. All right, I guess you can go ahead and get started, Tom. Okay, thank you. I've put the link in the chat for people to put their name on the list. So, looking down the event. So, to Wednesday. I'm going to go to the cloud security, Tom. Do we know where I'm going? Is there any toco? Useful toco. Events to look out for, do we know? The. Coordinated top of the CFPs are up and so definitely. What folks to. Get those in. While it's still open. When do they close? When did it. To the 12th. I noticed that. Right. Maybe. Yes. The next time. Yeah. Yes. There's so many events. Hard to keep up with them. It. We did hear that. There are going to be, there will be some toco presence there. From someone this past week, but. I'm not going to make it up to. That event at this late notice. Maybe we'll, maybe there'll be some good talks and stuff that we can see out of it though. Okay. Anyone got any topic ideas for the. DTF. These tend to be about. Topic, you know, the. Projects. So this is a relevant to talk to you. If there's any that we want to. Consider. It's a bit late notice I know. I wasn't checked it before, but I noticed now that. There's a national topics, which are. Great, like these. And even more are going to present something. So. Pretty nice to see. Some topical nephew.  I mean, so what. There's one of these ones. Cool. I can't think of anything off top of my head. We'd want to add. From a CNF working group point of view. I guess we could do a general interest. Topic thing, but. I mean, the, I think the bigger thing for me is that. It's so soon. And the deadline was the 27th. So. We'd have to really have something ready and ask, you know, ask someone, can you get it down at this point? Yeah. Yeah. I think it would be. I mean, there's a few things that we could look at, but I think. It's probably. Something for a future one. Any type of collaboration, which there's some ongoing. Talks that have increased recently. And then. The stuff that we were talking about going up to the end of the year. As far as, and then started this year for. Publishing. That the dev best practices. And, you know, if we can get. Maybe. Have that as a stronger goal with the timeline and then the. Energy. The energy. Focus stuff environment, environmental. Things that we're seeing more of. And there's post into Slack from. The Kubernetes. Some of the Kubernetes projects around this. And. Some of them. Possibilities for a future one. Okay. Make sense. Maybe over. A few weeks, we can. Have some focused talks about how. Direct specific goals and how we can get there. And those would be high and any future. Conferences. Okay. We'll mention the time it's telco day. Anything else anyone wants to call out or something we should. Submit a talk for. This is CFP closes soon. Open source summit in North America. If anyone's planning on attending. Yeah, good point. I'd like to know how. Tom, you and Victor think about the open source side. We talk about the cloud native a lot. The open sources, you know, underlying a lot of the pieces. When I'm in conversations. With different orgs and. Trying to get collaboration. A lot of times. One of the initial things is we. Our products are not open source. Or we're having to work with non open source products. If it's a consumer of those products. So for open source summit. It seems like we should have a slant where it would be more. Have highlighting more about open source and. At least in my brain when I'm thinking of it, but. I don't know what he all. So I agree. I think. I think there's plenty that could be said about the benefits of open source to telcos. I think if you were going to do it, if someone was going to do a talk on that. You'd have to address. The elephant in the room. Which seems to me to be the elephant in the room, but I think it's. The, the, the patent. Problem that telcos are reliant on. Telcos and telco vendors rely on patent revenue. And that kind of goes against the grain of open source licensing. And open source project. That it that's true to an extent. But I don't know what you're thinking about that. One is. A little bit easier, I think, for, to talk with folks about. Not. Not focusing on what you are doing with your product or how your business works specifically. And then more focusing on. What your business is built on and what your products are built on. I'm not throwing something out my own opinion, but I would. I would bet that. Most products out there are using some open source. If not a large amount of open source libraries and everything else, besides. If you're running on Kubernetes, then. Especially if you're doing like something where it also provides a platform type thing. But if you're providing like operators, you may be using some. Operator framework, but you're using specific pieces. And that's without looking at. Containers running on something and. Dbdk, you know, for instance, well, lots of. CNS that are dealing with the. And user plan are using dbdk and. You just keep going down that path. So you talk about. How open source has provided a lot of benefits. And I don't know, you can talk about that. And I think it. For some companies are more engaged with. The whole open source community. So it's not just a technology. And there may be feedback, you know, and user stories and stuff like that. But in my mind, that's kind of an easier path because you're getting more people to talk about. Open source and how they're involved, even if their product is an open source. And then the other side would be talking about. Different models for what does it mean if you have an open source product? How do you deal with that? And there's a lot of examples of those, including. The one that's looked at CNCF. Then a. A lot of the projects. I'm not going to say all of them, but a lot of them. There is a commercial version of that project where. They may call it enterprise or whatever else they call. It could be a hosted type of service. Or a version that has more plugins. That they have, but the core. It's not going to be open source. So, and that's just one path. There's a lot of paths for that. So I think there's an opportunity there. That. Similar to cloud native. A lot of other domains have learned what, what does it mean and how to work within, you know, how, how do you work within the whole. How do you actually adopt open source. Ideals and that are beneficial. Because this goes back to like. BSD and stuff, which would be. Research and science and sharing. Does it benefit us more? I think the telecom world is still can. Benefit from that similar to cloud native. And it's not sure how to approach it. Into for telecom. Because it's a little bit different. Like how do you translate and show like the benefits of the adoption. Yes, tricky. Because there's two. There's more than two sides to it. And then there's the, there's the use of open source. Kind of within your infrastructure. That is being used to deliver products. But there's also the use of open source in the products that you sell directly to consumer or business customers. So what are the degrees of separation between. The thing you're selling on the open source project. And I think the more degrees there are. Certainly I found the more likelihood you're going to end up with the. Patent discussion. Being had. I think, I think it's a good idea. I think there's plenty of discussion to be had plenty of talk material. On the topic of open source and talk. So I'm interested in the topic. I'm wondering how that ties back to. If there's a, we're talking about open source summit and a CFP. So is it something that we want to do as CNF working group. And that's separate from. You and I, Tom go, Hey, this is interesting. Let's go do a talk. Just completely separate. That's, you know, it could be upstairs telecom. Does that, is that good enough. To say that's related to the CNF working group. We're also interested. I'm just seeing how to tie it all together because we all have limited time. So long term, I think it benefits what we're doing. I mean, we're, you know, the CNF working group is definitely engaged in open source projects. So that's like, there's something there. I'm just not thinking of. More direct. I'm not. Making a more direct connection right now in my head. So. Let's see. February 5th. So that's this Sunday. Yes. Yeah. Does anyone else have any thoughts like how would we, because it, you know, if, if we're going to put time into submitting on CFP. If we have an idea and we just want to submit something fine, but. And then we can always decline later, but I don't have something just ready. But otherwise we need to decide on something. And we think, yeah, this has been official and maybe it ties back to what we're doing. Well, in my case, my only experience attending this. Open source event is in Austin. And one of the things that I noticed is. It's mainly to think that most of the sessions are where technical they were trying to explain some complexities of the technology. And the other thing is like. I feel like most of the tendons were looking for places to innovate but some looking for some fresh ideas or things like that. So maybe I don't know if that was my impression. But I don't know if we can provide something like who could meet those criteria like. I don't know, probably explain a little more like a sweet tool like how it works internally or like some of the benefits are. I don't know. That could be a suggestion, but I don't know if that could be also what we were saying before. So a kind of. A slightly less technical talk about the benefits of open source in telcos less likely to go down. Well, a more technical deep dive into an open source project that's relevant to telco might be more successful. So I've understood. Yeah. I just would maybe on that same topic.  I mean, you can take the angle of sort of the benefits of using open source and the test suite being an example of that. Right. In with the purpose of helping to drive cloud date of adoption. You can make me. So depending on which form right, which, you know, I was thinking you asked earlier. And I think there was a comment. Yeah. Yeah.  The DNTF, you know, for example, if you scroll up just a little bit, I think that was. I'm trying to let's see this on the, on the screen there. Yeah. That we had, you know, topics submission. You know, it's too, it's too late. That's why I didn't make a mention of it. But otherwise I would have thought that would have been a possible area. Certainly since there are. There's a lot of things that we've focused on doing collaboration around again, open source tool, using it across, you know, open source organizations. That, that would be another angle as well. So. I guess we were mainly focused on the open source part though, which was, which. That one's maybe we have time for that. That we won't have a time for the LFN. The DNTF this time around, but maybe one of the future ones. I don't know. I'm, I'm, I'm taking that into consideration with. What Victor had said. And. I think it's maybe similar to the higher level. Thing that Tom was talking about. And. If, if we can't find. If we don't think there's going to be a. A good audience for. What we're presenting. Then we can spend our time elsewhere. That's it. We don't have, I'd love to visit Vancouver again. I think that we should. Respect our time. And, and you know, know that we're only going to have so much time. So if. I'm willing to. Have a follow up. I don't want to take the whole call thinking about open source summit. If we don't have anything, but if, if we. Think that there might be something to focus on. Then we could do that. As far as the tests we open source. Maybe. It does. Give the opportunity to talk about. Collaboration with other orgs. So that could be like just one. Part of it. Using certification. And built on open source. And using a lot of open source projects. Different tools. And so there's potential for that sort of thing to be part of it. And I think that's an okay fit for open source summit. Potentially like pitching it. And why are you going to pitch it there? Maybe as a. A testing tool that could be, you know, used by other. Developers and. Ops folks and whatever else. And then just the benefit of collaboration groups. So I see something there. I'm. I'm not tying it back to why we would do it. I'm not tying it back to why we would do it. I'm not tying it back to why we would do it.  And how that relates back to telco. So maybe let's table it. Unless you all have some ideas like more. If you want to continue, that's fine, but give the opportunity to move on. And if we table it, but we're having some ideas in the back of our head. Either on that. What you put forward vector or. You put forward vector. And then we'll get some time for this. I mean, I, I do think that we need to. Set some specific goals and try to push for more involvement with the working group and push more of. Like, how do we get people. Engaged in. Cloud native and open source. Telecom and the benefits of those things. And I think that we need to be driven by the efforts in open source. So a lot of it's just like, what are you missing in methodology? And thank you. Problem solving. Anyways. What do y'all think? Table it and come back. I think so. I don't think it's feasible. Do something by Sunday. Yeah. Well, I will. I'm going to just set some time on my calendar. And if anyone. I think so something. Just message me and I'll make some time this week. And if we're like, nope, we have an idea. Let's go forward and let's do that. Okay. Yeah. All right. Does anyone know about that big five event in Austin? Any. If y'all attending or know anyone attending. I won't be attending. I've not come across it before. Looks like it's specific to North America. Maybe. Focus. Which isn't a positive or negative. It's just a thought. What about the open ran summit? I think that might be telecom TV. Oh, you were there. Go a little bit down. Right there. Open ran summit telecom TV. I think that's what that is. Let's see if the dates match. Yeah. Possibly. Focus is on. Total cost of ownership. As I was. Stable. Preco system. So maybe if there's something we've got. That's relevant to the Rick developer ecosystem. I don't know if that fits into the. The agenda they've got. Certainly my, my experience of watching those things before is that they are not technical. I don't know if anyone else agrees. They get a lot of folks. Joining. I've seen that. Even the in person too. Filling up a room. But it seems like the. Conversations or. Conversations are pretty set. By the time you're seeing anything. Yeah. And it's often, it's often. Either this kind of interview. It's this interview format. Rather than. Someone given a. Decent chat. We can sort of summit Europe. We can. Just poking about. We've got more time to have something for that. Yeah, that would be maybe. More possibilities for as time one goes. For that one. Okay. We move on to the. Review and the PRs and the issues. Yeah. And if we have any topics that come up, we can start looking for a conference. Yeah. That'd be safe. That's a good way of doing it is, you know, people have a. Kind of a blueprint for a talk they want to give them. That's a good way of doing it. Yeah. Yeah. That sounds good. I'm sure. If we start working on the options, then we'll be able to find. Some, somewhere to talk. There's a lot of places. PR review. No. At the moment. There was one closed in the week. It's a nice way of doing it because then it's. It's ready for when a suitable conference comes around. Maybe we should do that anyway. Yeah. Couple of talk options. Yeah. That sounds good. I'm sure if. If we start working on the options, there was one closed in the week, which was. The issue template. Okay. That's cool. So now that means if you are to new issue. You kind of report vulnerability. I didn't know about. You can open a blank issue or you can create the best practice proposal. And so when we put these text boxes to be able to put in the different sections of the best practice proposal. And. Do one of those. One more. So that might help. We'll see. The issues. Let's go from the bottom up. The privilege flag. So it's included in the CNF certification as an essential test. Currently assigned to Taylor and Victor. With a milestone of this quarter. So by the end of March. Yeah. I'm going to work on that proposal. I mean. So. It's just a matter of putting all the. All the things that we have in. A PR. I'm going to. Send you a calendar invite Victor. Okay. I've been. A little unavailable for. At least half of January. So I'm just trying to catch up. I will, I'm going to send out a few and you just let me know which one works. Okay. Any reasons to bring that off hold. No, well, probably relate with the same PR. Well, any issues like. The. Effort that the committee is doing. Some of the latest things that they were discussing about. Naming. So I think that they are going to send out Torby. Based on the number of proposals. So they have narrowed down to two of them. So if you are able to vote, maybe you can choose. Your option. And they try to summarize the intent of like the goal for, for that new. Human resource. So this is 20 just maybe I object. And you're representing the. Connection on the pot. So the naming are. Yeah. Canate. K, K this net. What network. Connectivity provider. The. Service and network instance. And this is a name for an API. net is, is it representing a network to which pod can attach to this object can be referenced by other API objects, e.g. service. The idea being that a pod can have multiple attachments to different networks or different API objects of this type. If I could, but they tried to just get all the idea in one single sentence. One of the criteria to choose this name could be like in the semantics of the, for example, if you use cube cattle, like cube cattle get what network sounds like something is to understand. So yeah, I don't know. I don't know if the pool are going to be open to anyone or they're just going to tend to mainly lead. For what? The name? Yeah, for the name. Yeah. I'm not as worried about the name as if it actually has the functionality that we've been hearing and talking and complaining about for years now. Is it covering, is it covering some of the main stuff? Is network service mesh folks? Are they saying this? Good question. I think so. Yeah, I mean, I haven't been attending those calls for a while, so I'm not, I don't know if it's been a current topic. I haven't seen it when I'm just looking at the network service mesh meeting that. I find that I mentioned this to Ed. He mentioned like, what was during the last chip gun? And he was saying like, he didn't see any point to this effort. Yeah, because I think that this is one, this is not the first intent that they're trying to do. It's like offering multi network. So I'm giving that they have another way to mitigate this problem like that. He didn't see any particular bandits to keep doing all these things. But that was the opinion of that. Interesting. Okay, need to have a read through this. So one of the calls for this, Wednesday, 8am PST. I think that they are recording the meetings. They switch from Google needs to Linux measures on some meeting platform. So I don't know if probably, I don't know if that was recorded, but usually tried to record the session. Okay. Well, thank you. So that's relating to this issue, which will remain on hold for now, quite a link to non route and non route. I just need to get on with that. Some time refactor introduction final paragraph in the first section. And no one assigned to that yet. Anyone wants to work on that? Please go ahead and assign yourself and create PR. Same for these next two. Yeah. Right. So this one, one process type. So there was a bit of dispute from go okay. He hasn't followed up to the follow up. No. And now Watson is going to be talking with or plans to talk with your guy, I think this week. And yeah, I don't know if I'd put it in there, but he's going to be talking with him some, but they've been working on more write up about related items that would tie into this. And I think there's a microservice white paper that is being edited right now. So that'll have a lot more content about this. And we'd probably point to that as a reference and have further discussion. Ideally, though, if, you know, this is going to be something proposed and there's Gurgi actually even open a pull request to just remove it from the test suite as a main essential test or something. I can't remember that's outside of the working but ideally, you know, we can get gargoyle on here to go in and provide you know, here's alternatives and other stuff. I do want to like bring it on the call and this is recorded. So have it like that that we're trying to create guidelines for what we think is the best path to follow for most cases, not all cases. So the idea with any of these like the privilege flag and all these other stuff are most of the time you should try to do these things. But when there's times where you shouldn't, then that's okay. And the way that we've been writing up the best practices communicate that, including caveats that you're going to run into if you don't do this, alternatives, anything like that. So if there's a dissenting view that we think is important to highlight, then that can go right into a best practice. If we think that it's, you know, a best practice that should be followed in most cases. And this particular one is related to how you would be utilizing macro services normally, which would tie it into, I think, a lot of the best practices and cloud native practices that you would be following. That's why it's being put forward. It's tied into a lot of things. So I think we need to have more context given from any other views and then make decisions on does it go into the caveats area, options area? Does it mean that we don't want to put it forward as a best practice? There's a lot of things there. Yeah, okay. Yeah, the other thing Taylor, I don't know if you remember last time we were talking about this. And that also brought the the topic about having using what was the name container, no, process handler in the because the container requires to manage the signalling properly. That brought the concern of like doing in the right way, which was related with the topic, but not directly tied to the one process per container. So we were also talking about like, okay, let's somehow simplify the things. Let's make the best practice quite simple, but also cover a lot of similar ideas around this side of this problem. Do you remember like that particular topic about managing signouts properly? Taylor? Managing the signoffs. Yeah, yeah. Do you remember like when I was answering to the gallery? So one of the topics that I found was related to the most of the cases like, I mean, you can definitely you can manage multiple processes per container. One of the major problems is like if you are not propagating those signals to the container manager, you get a problem. So and they were suggesting some articles were suggesting to use other tools in the Docker entry point to propagate those things. I mean, it was related with the one process per container probably, but also it was another kind of best practice for that Docker container creation. So eventually we follow the similar pattern like digging more things and eventually we will proliferate in a lot of best practices with similar topics. Yeah. Well, I mean, if we probably should just start coming up with a list of those either as they can go in as issues or into the discussion forum for those ideas. One of the things that we're talking to, I think we talked about a little bit was you can have zombie processes and other stuff. And so you can start looking into process managers and there's software out there that does pretty good management. I think I may have already mentioned the like email system. So QML, I think was one of the big examples of separation of concerns implemented in processes that are running and actually isolating them under different users and stuff. So if anything was if any one of them had a problem, including like external security issues and PostFix, which was a rewrite of that by someone from IBM, those are two large mail. I think if you're into email at all as far as the systems, then most people think Sunmail. But QML and PostFix would be the ones that they actually handle a larger quantities. Like if we look at growth and they were both PostFix was designed like QML to run in different processes. And those are internal versus saying using a in it. What is your in it? Process manager and there are those as well. But you can actually build a system that does process handling. And if you look at languages like Erlang, well, it's all about having its building applications that have lots and tens of thousands of processes. It's designed for that and separation of those using some type of process manager where someone actually already knows what they're doing. And you're taking advantage of that is a good path. If you haven't already been building systems like PostFix or software, the ideal with a best practice of one process type, not multiple processes, but one process type in a container is a method of separation similar to what PostFix is doing with multiple concerns broken into processes. They're not containers, they're just processes. Or if you're running something like Erlang and you're having a lot of processes, but each little component may be split off versus saying I'm going to have one container and running using a process monitor and manager that can run everything, but you end up with lots of process types, which moves you towards it's an anti-pattern for following a microservice model. And there would be a lot of different things that you could start pointing out. But this again is more of is this the path that works for you? Like do you want to take all the benefits and do you have caveats or not? And you could definitely have a container, I don't want to say a CNF, I'm going to be more specific. You have a single container that has multiple process types and you have a very strong and valid reason for that. But is that the best practice for everybody? That's all we're saying. Like should most people follow the practice of trying to separate concerns? And that's what each process type is. I would say probably it's a different concern. It's handling something different. You may have one, I don't even want to say process type because I'm reusing that word. You may have one application running in a container that has multiple processes. That's not what this best practice is about. That's fine. It could be a single process or it could be many, many processes. It's when you have a different process type. So they're doing multiple things. And the best practice is saying when you have multiple things being handled, multiple services, multiple functionality, you're doing processing different types of things, then the recommendation is to split those and not have them in the same container. Yeah, the last thing that I was thinking is one thing is a process and that thing is the threat. I mean, definitely having multiple threats on a single application is hopefully fine. Having different process types or like different processes in general would be a kind of a bad practice. I mean, you mentioned a couple exceptions like Erlang, which is totally fine because it's part of the way that Erlang works. Erlang is hard for me to think about in Kubernetes because it's in a lot of ways and people do write Erlang and Erlang derivative applications running on Kubernetes. But what's weird for me is Erlang in a lot of ways is designed to work like Kubernetes. It is essentially Kubernetes. It has its own system for handling restarts and monitoring and a lot of the stuff that Kubernetes does as a framework and core applications in Kubernetes to help other applications that you write to work well and you don't have to think about those things. Erlang plus the standard library in Erlang is how they look at it. That core is designed the same way. But it's also designed to run tens of thousands of processes when you're building an application. And it's designed to split them all up. But Kubernetes is designed to where you would build lots of containers and they work together. I'm running a Kubernetes cluster and I have three big applications that are five gigs apiece with massive datasets. That's an unusual case for Kubernetes. Most of the time you're talking about thousands or tens of thousands of containers running on a cluster. And with Erlang it feels a little weirder to split it out. I mainly brought it up as an example of that particular programming language. If you're building a container it feels a little weird to split an Erlang container out. So if you had an Erlang telecom application and you're trying to run it on Kubernetes, I can see how splitting different process types into different containers doesn't make as much sense because you're actually not taking advantage of Erlang. Like the actual system was designed to have really high-speed connectivity between essentially its own little mini containers, what would be running on the Erlang VM. But I would count Erlang as a very small subset of applications that are targeting Kubernetes. As far as I know I'm not hearing about a lot of telecoms that are going, hey, we're trying or having trouble. I like the language but I think for most languages that's not the case. Including Java, C++, besides messaging language that I can think of right now. That's not an issue. I'm just conscious of time. I've got to jump to my next call I'm afraid. I think that's been quite interesting news for discussion. I know it's hard if we can summarize some of that in the issue. I think it will help whoever comes to write that. I know we're running over time but I just want to, it's a comment I think we can address next time around on that specific. I think we're talking about, Taylor, you're talking about it being in some cases, there may be reasons for not doing this. In other words, you're saying this doesn't necessarily apply to everyone. There are caveats, et cetera. The only thing I think that we need to address somewhere and all that is I think people think about the certifications and things like that. If it's an essential test and you don't do this, then you lower your chances perhaps of being able to certify. I think that needs to just be addressed some way. Ultimately, we don't want to turn people away. If you have a good reason for doing it, go ahead and do that. You may not be awarded a certification if that's something you're trying to do. Anyway, I just put that out there for us to get to. Right now that's not an issue because it's not a you must pass 100%. I know. I know. I know. One that someone doesn't pass, that doesn't mean they don't get certified. If it turns out that we have a large set of things that we're all recommending, these are essential and then we have the majority of people not being able to get certified. We can think about what does that mean? Ideally, folks are getting helped and they're becoming more cloud native. That's the point and the long run. I'm wanting people to do these things because I literally think that it's going to be beneficial. Add any comments or notes. We can continue next time. Yeah. Thank you. Ideas for talks. Just reach out. Thanks, everyone. Thank you. Bye bye.


Hi, everyone. Thanks for joining me. My name is Rick Viskomi. I'm an engineer and developer advocate on web transparency projects at Google, including the Chrome User Experience Report, or CRUX for short. As you may know, CRUX is a powerful data set containing insights about how real users experience the web. And this data set goes all the way back to late 2017 and includes data from over 18 million websites. This will be a somewhat advanced presentation. So if you want to brush up on the basics, you can visit the CRUX docs at bit.ly slash chrome.exe report to learn about things like metrics, dimensions, best practices, and more. What I'll be sharing with you today are a few pro tips for mining the low-level data set on BigQuery for insights about how users are experiencing the web. So by now, I'm sure you've heard of Core Web Vitals. They are the most important UX metrics we think you should be looking at in 2020. The list includes LCP, FID, and CLS. In fact, CRUX supports all three of these metrics and has months of data across millions of websites. So let's head over to BigQuery to see what we can find. Here, I'm querying the metrics summary table, which is a really quick and easy way to get high-level stats about a website's Core Web Vitals. You can see here that we're extracting the percent of user experiences that meet the good thresholds for LCP, FID, and CLS, as well as metrics 75th percentiles. All of these stats are pre-computed for you, so you can spend more time finding insights and less time writing queries. This summary table is also much smaller and more efficient. You can see it processes only about 100 megabytes, so you shouldn't have any concerns about exceeding your 1 terabyte of free monthly quota. The raw data still exists if you need access to specific histogram bins, but almost everything you need is here in the materialized data set. If you've ever queried the raw data, you'll know that there are several useful dimensions that you can drill down on, like month, device type, and country. So let's look at a few examples of doing that efficiently with the summary tables. The first thing we'll do is modify this query to see how the Core Web Vitals have changed in recent months. To do that, we need to change our where clause to include all releases in 2020 by setting the condition to date greater than 2020, 01, 01, or January 2020. Next, we include the year and month of the release and the select clause, so we can see it in the output. The difference between year and month and date is that the tables are partitioned by date, while the year and month correspond to the table names in the raw data set. And finally, we can sort the results chronologically and run the query. You can see from the results that web.dev has had relatively stable and good user experience this year. But what if we want to break this down by desktop and phone experiences? For that, all we need to do is change over to the device summary table. We'll restrict the results to only desktop and phone results. Now, tablet is available, but it's less interesting. Next, we'll add the device name to the select clause and secondary sort by it to keep the ordering of the results consistent. I'm gonna run this query, but there's one thing I wanted to show you in the results. These percentages are out of all user experiences on the origin, not just the percent of desktop experiences or the percent of phone experiences for boring technical reasons. So one last thing we need to do is normalize these distributions, so it doesn't matter that desktop is more popular than phone. To do that, we just divide the metric by the total. Now we have comparable results between devices and we can see that desktop actually trends slightly better than phone. And finally, what if we want to break this down even further by users' countries? For that, we can change over to the country summary table. For demonstration purposes, let's restrict the results to two countries with very different experiences, Korea and Nigeria, and focus only on desktop. Now, we could write the country code to the results, but I wanted to show you one other cool trick. The crux data set includes an experimental function to map country codes to full names. And the last thing we'll do before running the query is to sort by country rather than device. The results tell a really interesting story about the disparity in user experience by country and BigQuery was able to analyze this in only a couple of seconds and using only about a gigabyte of data. So that's it. These are just a few quick examples of the power of the BigQuery data set and it doesn't have to be mysterious or expensive. I hope you start exploring the data set and finding insights about the state of the web. You can find links to all the resources and queries we discussed in the description and comments of this YouTube video. If you have any questions at all, we have a whole support network set up for you. You can find me on Twitter at Rick Viskomi and I also tweet from at Chrome UX report. We have announcement and discussion groups for important product updates and support. We have the crux cookbook on GitHub where you can find example queries for common problems. And finally, we have crux office hours where we can meet virtually and get your questions answered. I hope you found this useful. Please hit the thumbs up if you did. Thanks for watching, everyone.


In this session, we will tie together some of the sharing concepts that we've discussed in previous sessions. We will go over one example where we use the sharing concept to separate analysis based on a user's role within the health system. We will use the following roles to demonstrate this concept. We will start by logging in as a system administrator. This particular user should be able to see all of the different outputs from all of the different health programs when they log in. Next we will log in as a national MCH team member. This individual is responsible for managing the MCH program at the national level. We will then log in as a district MCH team member. This individual is responsible for managing the implementation of the MCH program at the district level and should only see data related to that particular district. Now that we've defined these roles, let's go ahead and get started with this session. We have been discussing the concept of sharing over several of the sessions. Let's go through an example where we use this concept of sharing to define what users see based on their role within the health system. To start, I'm going to log into a user who has access to all of the different outputs available within this particular system. We can see this user has access to a variety of different dashboards for multiple programs. If I go to one of the analysis applications and then check on the favorites that are available to this user, we can see that there is a long list of favorites that is 17 pages long. Let's log out of this user. I'm now going to log in as a user who's part of the national MCH team. We can see this particular user only has access to a subset of the dashboards that are available within this particular system. If I go to the data visualizer application and then check on the available favorites, I can see this user only has access to four pages of favorites. These are specific to this particular thematic area that this user belongs to. In this case, the national MCH team. Let's log out of this user and go down by one more level. We will now log in to a district level user within the MCH program. We can see this user only has access to two dashboards. From the dashboards, we can note that this user belongs to CAT district. If we go to data visualizer and open the favorites, we can see this user only has access to a subset of favorites. And these favorites, when we open them, only display data for CAT district. Through this demonstration, we've shown you that you can in fact use the concept of sharing to determine what users see when they log in to DHIS2. This is quite useful as it allows us to map a user's role within the health system with the outputs and analysis that they are seeing within the health information system. This wraps up this brief demonstration on bringing sharing concepts together. Let us know if you have questions about anything that we've shown in this tutorial.