They're three times a week by our exercise physiologist to supervise their exercise training and that runs from about 14 weeks of pregnancy through to 28 weeks of pregnancy and that's about the time when women have their tests to see if they have pregnancy diabetes or not. Okay. Is there any connection? Do they have, have they had diabetes beforehand or has this just become with pregnancy? Yeah. So it's a diabetes specific to pregnancy. So basically up into that point of history. Yeah. And why is this research so important? I know you've given us the reasons and it sounds like it can be pretty serious. Yeah, certainly. You know, given those potential health implications for both mother and baby, if we can find a way of preventing the condition from happening, yeah, it can have such, such great, great benefits and it's, I guess, potentially could impact future generations as well because if those children are potentially at increased risk of obesity and diabetes later in life, then then themselves will have increased risk of, you know, having pregnancy, diabetes and so on. So it's sort of like a recurrent cycle of life. Yeah. With the like that goes data into their homes, what's the reaction like? Are they, are they fine? They're enjoying it? Is it? Yeah. Look, I mean, most women volunteer for the study because they're kind of hoping that they get the exercise program, but at the same time I have to admit there are some women that are a bit horrified at the thought of this fight being delivered and they have to exercise three times a week, but look on the whole, the women, the women really enjoy it because they have had pregnancy, diabetes and a previous pregnancy, they all have at least one child already and any mum will tell you finding time for exercise is really difficult. So this program aims to sort of take away all those barriers so it's in the comfort of your own home. You don't have to go anywhere. You don't have to worry about, yeah, transportation, childcare because kids can be, you know, at home around you and the fact that the trainer comes to the home as well. You've got the supervision aspect for any woman that's concerned about safety. How long are they on the bike for each session? It's individual, so some women come into the study with a reasonable level of fitness. Some don't have any exercise experience, so it's all tailored to each woman's individual levels. Okay, sure. So the study is ongoing. Are there any results from previous research that you've been able to sort of see the direct implications of? Yeah, so you're right, the cycle study is ongoing, so we don't yet know the answer to the question of whether our program will prevent pregnancy, diabetes, but last year we completed a study focusing on women that already had pregnancy, diabetes. So one of my PhD students ran and hold, she led this particular study and she was looking at women diagnosed with GDM, could implementing a regular home-based exercise program at that time help manage the condition. So rather than prevention, we're looking at management and she found some really positive results. So women that completed her exercise program had lower daily sugar levels, better glucose control and it's high sugar levels, that's the whole problem with the pregnancy diabetes and she also found her program only ran for six weeks but within that six weeks she was able to change women's sort of intentions and attitudes towards exercise as well as increase fitness. So that's pretty important to know that within six weeks only you can improve women's fitness during probably the phase of pregnancy where things are starting to get a bit harder, they're getting bitter and so on. So what's been one of the highlights of your career? I don't think I necessarily could name a specific highlight. I think some of the things I've been really appreciative, some of the amazing people that I've been able to work with and that includes both people that I would consider I suppose mentors that have helped me along the way as well as some of my PhD students are just really great and that's probably one of the aspects of my job that I enjoy quite a bit. Other than the people probably the opportunities that I've had to travel have been really lucky in being able to attend conferences. Most recently I was lucky enough to travel to Beijing China to talk about our cycle study over in China exercise isn't the done thing during pregnancy so we were sort of myself and Professor John Newnham who's leading the cycle study. We went over to talk about our research and hopefully spread the word of some of the potential benefits of exercise. So if it's a place where it's not really the norm how did they react to it? We think very positively actually. We were surprised. We thought that we'd sort of presented our work and that it wasn't necessarily filtered through anywhere but we were really impressed to learn through different sources and avenues that things actually were filtering through and things were starting to take effect. They now have in one of the rooms in their hospital a little room set up with a couple of bikes and women actually come into the hospital and do exercise during pregnancy which is really encouraging. Yeah great. If a student is interested in this field of work what major would they start with from the Bachelor of Science? Yeah so in the Bachelor of Science you'd be looking at two majors. You'd be looking at a major in sports science and a major in exercise and health. The major structure is important because those two majors are required in order to get accreditation from our governing body which is called Exercise and Sports Science Australia so there are two majors that you'd be looking at. Okay. You're also in a teaching role. What's the learning environment like for UWA students? I can only comment on the School of Sports Science, Exercise and Health and it's a really great environment. I think because in our particular school we have the lecture setting, we have laboratory classes, tutorials and so on but we also have a lot of practical classes where students are actually interacting in the physical sense whether it's through a sporting game or whatever and I think that really helps to build the experience and so on in addition to just learning the material you make friends and that sort of thing which I think makes a really big difference. Yeah absolutely. Okay. Does the School of Sports Science, Exercise and Health offer students any other experiences outside of the classroom? Yeah we actually have an award winning I have to say practical program. It's been running for many years now essentially in the third year of the Bachelor of Science if you're doing the sports science and exercise and health majors. You complete 140 hours of practical experience or work experience if you like and there's a number of different potential routes that you can go for that experience but students find that great to actually be out in the workforce seeing what it's like doing what it is they think they might want to do in the future. Yeah absolutely. You've mentioned your PhD students so are there any are you looking after supervising a couple or was it just that one? Yeah well Rihanna that I mentioned previously she's now finished her PhD which is great she she graduated earlier this year but I have a number of other PhD students some also working on exercise and pregnancy and then I have others that are working on sort of another research focus which is the effects of exercise on appetite so in terms of you know maintaining a healthy weight it's all about what you take in through food and drink and how you balance that with the energy you expend through exercise but what people often don't think about is how exercise itself might affect what you eat your preferences or cravings for different foods so that's that's another sort of research interest and I have a three PhD students sort of focus in that area at the moment. Sounds like there's some really good opportunities available for students through UWA and thank you so much for taking the time to come and speak to us and tell us a bit more about what's happening at schools for exercise and health. Thanks Kim. Thanks Eliza.


Hi, I'm Sean Bonner and I am a collector. This is something that I've only recently come to terms with, although the evidence has been piling up my whole life. I have these huge boxes of things around my house that through different cycles and different times in my life I've been obsessed with and done research on and piled them up and then gotten bored with them and stuck them someplace else or sold them off to buy the next things that I was interested in and I have a very complicated relationship with stuff, it turns out. I'd really hate having it around, I feel cluttered, but then as soon as I clear a space I'm like oh I need something to go there and so then I start researching and finding new stuff to stick in that spot. But it turns out that when I look at this what's exciting is not really the stuff, it's the thrill of hunting for it and so the thrill of the hunt is what I've realized just this year mostly is what really gets me excited and helps me find stuff and there's a few things that make that possible. So whatever this object is I have to be able to know everything about it. It can't be something infinite like wine that's continuing to grow or whatever. It has to be a finite amount of information that I can learn the entire thing from start to finish. The stuff that was made I have to be able to get it. So it can't be stuff that maybe they made two or three of, it's out in the world, I have no chance of ever getting it. I ask mass produce enough that I can actually track it down and I can complete this collection and then also it can't be something like Ferraris because there's no way I have that kind of expendable income. So the absolute top tier of whatever this thing is has to sort of be in my reach plausibly even if I don't actually go for it and then if I'm really honest if all my friends are into it and I go to their house and everybody has the same stuff around then it's boring and I don't get excited about it anymore. So all those things come together and then I end up finding stuff that I have to research. This is my kid and he's in all of the exciting world around him and so in my efforts to constantly blow his mind I pulled out my record collection and started playing him records mostly because I wanted him to hear different songs and music and stuff but you know it also the physical aspect of playing records turned out to be pretty cool but I let him loose on and I said you just pick stuff go through it and find stuff and he starts picking stuff not by context or by genre but just by record covers and he ended up picking out a lot of jazz records that I had around just by covers which isn't really surprising because that's actually how I got these records myself too. I would go to a record store and I was struck by these amazing covers and I would say hey I want to grab these and so he's playing them I'm looking at him again and then you know I started I started doing research and it turns out that Blue Note jazz records are an incredibly huge black hole for collector nerds and I fell into it earlier this year forget what my next slide is yeah can we just leave that one on forever okay so for any for any record that Blue Note released there there's probably 30 different versions of it and they sort of took the let's just copy of VHS tape a hundred times approach to it so every version that they released is worse than the one before it so people want to get the early versions not because they want oh I got the first but because it actually sounds way better than the stuff they made later sometimes they would just took a cast of a record and then use that to make masters of them but any any Blue Note record that you pick up there's like 20 different things that can all vary at any different point to tell you exactly what year that record was made and then you can sort of look up to figure out like what what the sound quality on it's going to be and so the early stuff very desirable but even the holy grails of this stuff the very first pressings from early 60s of some of this stuff you can still track it down and it's still sort of within reach so it's not like you need to you know sell your car or mortgage or house or anything if if that's what you're going to do not that I'm going to do that but if you are but I also found this weird little black hole or this little loophole in this and that Blue Note licensed out their stuff to other countries to make and in Japan they were incredibly anal about it and they wouldn't take any of the existing masters and they made their own masters off of original tapes and so the Japanese pressings actually sound way better than any of the US pressings past a certain date of course there's also a bunch of versions for the Japanese pressings and similar things happen but that ends up making things like this incredibly exciting for me and I can lose a whole afternoon stumbling across one of these places now hoping to find one of these little gems and then that made me try to figure out why is this so exciting to me in this this little bit of research why am I all obsessed about it now and that's how I came up with these four things and and it seemed this seems to hit on them and so if anybody has any old jazz records around you should give them to me thanks


I've been using Sync thing for, well, I did a video about it three years ago, but I know I was using it maybe a year or two before I did a video. The project's been around a while. I've been using it for a while. It is a great project and it's still my go-to system for how I sync all my data between my desktops, my laptops, or even my servers. Now, you're probably saying, well, Tom, didn't you do a video on NextCloud and why don't you use NextCloud? It's an amazing project and you're not wrong. NextCloud is outstanding as a project. I don't know of any flaws in security related, but we're going to talk about why I use Sync thing versus NextCloud. And it comes down to, I know NextCloud is convenient, but Sync thing has a smaller threat surface. And that is a big factor in the data that we're synchronization is how much exposure do you want to have. If you're not familiar with the term threat surface, it's going around a lot in security because threat surface refers to just how big your risk is, what are all the attack factors that could be attacked with Sync thing. It's much, much narrower and much easier to manage the threat surface versus NextCloud. Before we dive into that topic a little deeper with Sync thing, let's thank a sponsor of the channel. So, this is IT training you'll want to watch with IT Pro TV. These people are great. They have some excellent plans and we reached out to them. We weren't pursued by them as a sponsor. We pursued them to sponsor us. And one of the reasons why is we just kind of figured with me doing all the IT training, people always go, how can I learn more? How can I get certified? How can I dive deeper into a topic that you don't have time to cover? You just don't know, Tom. And that's true. I don't know. We use IT Pro TV for a bunch of our training. My staff uses it here. They all have accounts. As part of the business plan, as part of the offerings, we encourage everyone to keep going and furthering their knowledge. And they have an entire class related, slightly to what we're talking about today when we talk about reducing threat surface, intro to incident response, part three. They have an entire series for the EH counselor certified incident handler. And there's a lot that goes into the state offer, computer hacking and forensics investigation incident handler, certified encryption specialist. These are things that are really handy to know and understanding how the knowledge of how security works and some of the functional, especially when it comes to the legal side of it, is really important. And of course, as we're talking about reducing our threat surface here, they're going to have a lot of discussion about, you know, all the different methods of attack. And after you're done watching something like that, you frequently go, how can I reduce my threat surface? The more time he's been in security, the more time he's been thinking about it. So check out IT Pro TV. We have links to them and many other sponsors of this channel down in the description below. All right. Let's jump over and talk about these topics. Protecting your data, the self-hosted productivity platform that keeps you in control. Now, I really do like NextCloud as a project. They do have a ton of features. They have a lot of big companies. It's a well-mature, updated project. It means it does get a lot of attention if there were a security flaw in it. So you, despite having a lot of exposure, you're running an entire web server that you're allowing internet access to, to synchronize not just files, but be able to collaborate in documents, that is a wonderful feature of NextCloud. I really like it from that standpoint. I mean, you've got calendar sharing, everything else. I really do like the project. What do I use SyncThing for instead though? Well, the only real crossover between NextCloud, I mean, NextCloud supports file synchronization, but of course, that's the only thing SyncThing does.  And for my use case, it works really well. So the SyncThing project's been around for a long time. I've been using it for a long time. It's one port with TLS security synchronizing files. Now it doesn't get into the side of encrypting any of those files. It doesn't get into the side of encrypting data at rest. It's a transport method to synchronize files. All the transport layer it uses is very well secured and it will go over the security principles real quickly how it works, which their documentation, by the way, is quite in depth and well written. So security is one of the primary goal, project goals. This means that it should not be possible for an attacker to join a cluster uninvited and it should not be possible to extract private information from the intercepted traffic. Currently this is implemented as follows. And what they're saying here is they have a key that is not easy to crack with TLS. So if you wanted to join my group of SyncThing vial synchronization, you would need to have that encryption key. Not only would you have to have it. Even after you have the encryption key that you use to get to one SyncThing joined to another SyncThing, there is still a series of prompts in SyncThing that someone has your encryption key and they would like to join and then it takes manual action on your part to get the system to join and then another manual action to share those files. This can be more automated. You can force levels of automation into it once you've shared the key to auto join certain things. But that would obviously reduce the security. So I have it set to the normal stock method, which default is, it's not going to just allow someone. So even if I were to show you or let you have access to my keys and the IP addresses that connect this, it still wouldn't join without me manually intervening. So right there, it's obviously a lot more challenging to get in. Other things I do on my SyncThings, I know the IP addresses of the machines. Well, I have static machines. I have a free NAS here and I have another SyncThing set up at an offsite location that has a static address. My laptop is all over the place, so it has a dynamic address, but via a VPN into the office, I can always get back to my SyncThings servers and SyncThings. That being said, I turn off global discovery, natural reversal, local discovery, and relaying. I just don't need those features. This specifically is our local free NAS that we have here and it keeps everything up to date as I create files. I have it running on my laptop, I have it running on my desktop and this allows me to immediately, as soon as I make a change to a file, it senses that change and a change propagates across all the locations and that change has revisioning and I've got a few videos where I dive deeper into some of the strategies for using it. Right now even, you notice that it says Studio Videos, updated 2019, 10, 6, 11, 4. I even have our studio computer, which is actually right behind the camera there. Well, technically it's off to the side, but details. It, as the files are created when I create this video, we're using the OBS Stream Deck. I've got a whole detailed of how my studio works. As those videos get created, they also get synced to a folder on the free NAS where my videos reside. So they are getting copied off the local workstation immediately over to the free NAS. That way, when I go on my office and edit, all the files are there immediately. So it works for synchronizing those for my server backups. It is constantly as the servers create files, not the whole VM. They create an encrypted file on the server. Once the file server has got this file, it's encrypted, password protected. It then drops it over on the free NAS and the encryption key only lives on the server. So then SyncThing finds a new file and it synchronizes this encrypted file. Even, I use Unify a lot, so even the Unify, every hour creates these data files. So SyncThing takes care of that. And the data files are actually really small, despite how big our deployments are. It's not that much to sync, so keeping them synced hourly. And then, of course, replicated offsite. That way, if anything catastrophic happens to the building, all of this is replicated offsite. And then from offsite again, it's replicated to get out of my house. So it now lives in multiple locations in real time. Plus, if you were to delete all of them here, it would propagate to delete at the other locations. But there's a 30-day hold at all the locations where you can do revisioning, referred to as trash can revisioning. So anything gets into trash, it just holds onto that trash for 30 days. I usually notice if something's missing for 30 days. Even my business documents here, there's really not that many business documents it takes to run a company, some spreadsheets and things like that. As I edit my financials here on my laptop, they get synced. Other things that are synced, it says updated top five command history. And if you follow a tweet I did, I'll even show you what this is. Someone tweeted out a really simple script, and I was like, this is clever. So this is the top five command history. And I was sitting on my laptop, I seen it. I went and copied, pasted the script and ran it in here. I'm like, I like this. I might use this once while to see what my top five commands are, maybe top 10, maybe I'll tweak it later. But then it's just, I created it real quick while I was sitting on my laptop. And now it's at all the locations, and it's back at my desktop if I wanted to do something else on it. And this actually goes for all the bash scripts that get created in here. Anytime I have something quick that I need created, I'll create a script down there. And because I can set this up and you can set syncing up to sync specific folders, if I have just these bash scripts that I need because of another project I'm working on for another video, I just put the scripts I need in there. And then I can also just load syncing really quickly on that particular project VM. And all of my bash scripts are immediately synced to it, making it once again very simple. So syncing is really very much just file syncing. And because it's file syncing and I have easy to find static addresses, when you could build your server in the cloud and encrypt it, you could have a free NAS box that runs it at home or even a free NAS box at work. And some of it's the way I have it and just have those two talking to each other. You're only exposing one single port, the software auto updates. The software is really well documented. The encryption is standard TLS, so they're using normal. They didn't try to reinvent the wheel with encryption. They're using solid encryption libraries. And it's very, very lightweight. So it takes almost nothing to have it running on your system. And once you turn off things like local discovery, you've also removed some more options for people to find you, because it's not just broadcasting out there. But maybe you need those features. And even if you need them, other than them knowing as in them being people that can join your network or see your network traffic that you're using syncing, you're really not that insecure. So it's a solid product. I really like it. Maybe I'll do an updated video as I realized it was three years ago, since I did how to get started with syncing video. But they haven't really changed much over the years. The same methodologies work. The project has matured. It has gotten better, faster, more efficient. Matter of fact, that's one thing I probably should do an update video on. And when you look at the feature set now versus the feature set three years ago, definitely they've improved. The way they do file watching has become more accurate and faster. And by the way, this is completely across platforms. So even if I have a Windows project where I need to synchronize some of the files, I can spin up a Windows VM, load sync thing on there, and it will synchronize between the Windows computers. We've actually set this up for clients. We've set this up for people who want to have kind of a cloud agnostic, I should say. So they're like, I don't really want it in the cloud. I'm not sure I want to be dependent on someone else's protocols or their terms and conditions. And by the way, we've worked with a handful of companies that have engineering secrets. So they don't even like any type of remote access. They want their two facilities to synchronize specific documents like engineering things and so-to-speak secrets that they work on without having to have a third party that can see that data. There's ways to do that by encrypting it before you send it to Google Drive, before you send it to Dropbox or whichever company. But with sync thing, all my data is encrypted at rest on my laptop when I close the lid. And sync thing's just a transport layer between the two. So it's not involved in that. And no third party has to be involved at all. They do have some global discovery servers. If you need natural versus on things like that, it does support. So you don't have to open any ports. That is a feature that you can do with sync thing with your global discovery and relay servers that they offer for free. So you have options if you're out in the field. They even have a phone app, at least for the Android. So you don't have on anything to my knowledge for iPhone anymore. But it's a great project. Check it out. I'll leave links below where to get this. And thanks for watching. And thank you for making it to the end of the video. If you like this video, please give it a thumbs up. If you'd like to see more content from the channel, hit the Subscribe button and hit the bell icon if you'd like YouTube to notify you when new videos come out. If you'd like to hire us, head over to laurancesystems.com, fill out our contact page, and let us know what we can help you with and what projects you'd like us to work together on. If you want to carry on the discussion, head over to forums.laurancesystems.com where we can carry on the discussion about this video, other videos, or other tech topics in general. Even suggestions for new videos, they're accepted right there on our forums, which are free. Also, if you'd like to help the channel in other ways, head over to our affiliate page. We have a lot of great tech offers for you. And once again, thanks for watching and see you next time.


Welcome, everyone. Good morning, good afternoon, good evening, wherever you are. Thanks for joining this webinar by Alchudo and Acquia, unlocking the potential of Adeless Drupal. Let me start with the agenda. Today, we will have a short intro on Alchudo and Acquia, and then we will talk about the market trends. We go deep drive on what is Adeless CMS and how Drupal can function as an Adeless CMS, and how Drupal and XJS can bring two powers, like from the DXP leader, Drupal, plus the front-end technology in XJS, like how they can work together. We do have a short demo of how XJS and Drupal can align and how you can still manage all the Drupal back-end experience and also vis-a-vis editor, everything, along with taking the advantage of all the Adeless CMS features. And also, we have a few Adeless success stories with Drupal and Acquia was able to accomplish. But I will start with the speaker intro. Tammy, you want to start? Absolutely. Hi, I'm Tammy Perlstein. I'm a Principal Product Marketing Manager at Acquia. I've been at Acquia for a little over a year, but joined with a wealth of experience across the digital experience as an industry. So excited to have this conversation with Alchudo today and we have a good one for you guys. Thanks, Tammy. I will go next. I'm Satish, currently working as a Senior Vice President Delivery Technology and Delivery in Alchudo. I have 25 plus years of experience in delivering scalable IT solutions. Been in this content and commerce area for almost 15 years now, currently supporting my customers with achieving the digital and cloud transformation. I'm based in Phoenix, Arizona. I can be reached at the email id given satish.balakrishnan at alchudo.co. The next speaker is Karthik. Karthik, you want to go next? Hi, this is Karthik. So I have about 14 plus years of experience working with Drupal and other CMS. I have a lot of domain experience with marketing, e-commerce, education, health, sports, and telecom domain. So really a good experience with customizing Drupal Drupal as a solution and also implementing third party services in Drupal, CMS, and developing the API. And also I contributed patches and modules to the Drupal community. So you can reach out to me at Karthik.com or at alchudo.co. A brief intro about Alchudo. Alchudo, we are a global digital marketing and technology agency. We focused on one thing and one thing alone that is create a personalized customer experience to our customers. And the way we do that one is like with an integrated tech stack that is focused on delivering omnichannel, cross-channel personalized experience using the single view of customer. The key mark tech that we assemble is CMS, marketing automation, CDP, analytics, CRM. These are the three tools come together so we will be able to achieve the single view of customer. And also we do have a very unique innovative way to bring the customer insights to the process. So our DXP experience, like we've been in this DXP world for over 20 years now. Implemented like 2000 plus projects, worked with 500 plus customers. We are like 400 plus trained certified DXP team members across like various platforms. We are very well known in the market for our IPs and accelerators that we created over this years. From service-wise, we do end-to-end solutioning starting from advisory services, implementation, managed services, migrations and updates. We build like custom solutions for the version upgrade like particularly for Drupal and other major CMS. Like we do have a like upgrade accelerators which helps to migrate this version upgrades much faster and seamless. We do have like something called one-way framework which we primarily used for multi-site implementation, single reusable code base used to build like multi-site, multi-tenant, multi-language websites. And also like we have a lot of experience on the marketing cloud, including campaign management, personalized CDP and dam implementations. About our experience on the Drupal and Acquia, like we've been working with Drupal for more than 10 years now. Three plus years partnership with Acquia have like 10 plus awards across worldwide awards we have received in this DXP. And also like we have like 20 plus integrated solutions which we build, which accelerate the development, IPs and accelerators. And also like we have like 80 plus Drupal SMEs in the team. With that I will give it to Tami to talk about like Acquia. Thank you. A little background on Acquia. So Acquia was born out of the Drupal open-source movement. We were founded back in 2007 by Dries Baitard, the founder of the Drupal project. And the goal was really to support the growing Drupal project and movement and community and help increase the adoption of the composable solution. And Acquia bet that the open-source and cloud movement would win in the long run in the long-term and in the digital experience space specifically. And from the very beginning, our platform has been cloud-based. Now today we're a proven leader in the digital experience space as assessed by Gartner, Forester and more. We have over 4,000 customers across a variety of verticals. You can see just a few here on the right of your screen. And those organizations bet their business and the experiences they provide to their customers on Acquia and on Drupal. And Acquia is the open and composable DXP built with the foundation of Drupal. So built with the open-source CMS to provide you ultimate flexibility and an API-first perspective. We're looking to integrate across your existing systems and services as well as expand you across the Acquia DXP solutions. And our solutions are also composable. So as you grow, as your challenges and your goals adapt, you can swap out different services or expand your services as you really change your organization. Your teams can also assemble and reassemble the different components to craft your digital experiences at scale, making it really modular, really composable and really flexible. And we're built for resilience with that in mind to meet the ever-changing digital landscape with security and performance at the forefront. So Acquia and Altudo, like we both, both the agency have a common goal to help the businesses succeed in the digital world. Acquia being a open-source leader in the DXP platform and Altudo being focusing heavily on the creating a personalized solution, combining both Acquia and Altudo campaign like will result in a better ROI for all your digital investments. We talked about it like why it's time to think and act on edless, right? Like these are all some of the recent studies for example, the worldwide website software forecast, like recently mentioned that the CMS solutions like a headless CMS solutions were like in 2021, it was like 5% but we are seeing a compounded growth of 27.5% across the year after year. And in 2026, like over like $1.6 billion solutions will be built using the headless content management solutions. Same thing like we hear from the faster predicts by 2024 the next year actually like the 75% of enterprise will have adapted a headless CMS, CMS solutions. And one of the recent studies says like a 83% of e-commerce companies will start using the headless CMS for their digital commerce strategy. And from markets and markets predicts that AI in the headless CMS market will grow from like 130 million in 2022, 1.32 billion in 2025 which is like a 58.2% growth year on year. So this is the primary reason, right? Like the various studies, various market trend shows like a headless CMS is being widely adopted. It's not something new, it's been already adopted and it's gonna grow, explode in the upcoming year. So this is the best time for all the marketers and the IT team members like to start thinking about headless and migrate the solution to the headless. So before we go deeper on the headless on the group side, let's talk about like what is like headless CMS and what are all the different variations is today? When we talk about the traditional CMS, CMS, a user create and edit their content through their vis-a-vis editors or an HTML editor. The CMS then displays the content according to the front end layer, front end delivery layer built within the CMS. So the front end delivery layer is coupled within the CMS. That's the only major difference between the headless and traditional CMS. The front end layer is coupled within the CMS itself. So if we remove the headless CMS pretty much like the headless or decoupled CMS will form, in a headless CMS, there is no default front end templates. So the CMS exposes all the content in an API layer and as the developers will create like a front end agnostic solutions, they can utilize this raw data and build the solution which fits for whatever the channel they wanna present the content like whether it's a web or it is in the mobile or in the digital watches or any devices they should be able to use the API content and they can create their own front end templates in their any technologies which they wanna build. Decoupled CMS is very similar to headless but it also provides an additional feature of retaining the front end template but it's decoupled like it's not directly pulled from the database rather it uses the same API layer. So it provides both headless and also features of headless and also the coupled CMS experience also like it provides both in the decoupled CMS. So we can talk a little more on the headless Drupal. Drupal has built like it started as a coupled solution like where the front end sits inside the CMS but in the recent versions like the application layer like API layer has been created. So Drupal supports both decoupled and headless CMS. So what is the, what are all the uses, right? Like headless Drupal is a way to build the website and web application not just the website, like we can use this data content and then build, utilize them in your e-commerce solution, web portal, wherever you want you should be able to build. This provides like the decoupled option. It's no longer like it's not required for us to do the, create the front end using PHP rather we can use any of the recent frameworks like Next.js, React or any of the tools by utilizing the APIs provided by the Drupal. So yeah, like so Drupal, headless Drupal is the ideal for creating a custom front end, building mobile apps and integrating with your any third party services. Why do we need like a headless Drupal, right? Like deciding like the foremost advantage of using an headless Drupal will be the website performance. When we talk about performance like a performance it's not just like it's primarily very important for the customer experience perspective but also right like right now with the recent Google algorithm changes, websites with the better performance gets better page rank. So it became a must for to get the better performance headless Drupal, a decoupled architecture will provide a much better performance than a coupled CMS. So that's the primary importance of moving into a headless Drupal. And also right now it's not just website like to provide a, like create content once and use it across multiple channels it's became a common norm. So headless Drupal will provide that facility as well that feature as well. And as a developer like you get like more control now like all the modern technologies like you don't need to be stuck with PHP or any backend solution. The developers have the wide options right now it's not just the front end technology they can utilize any modern technologies to build that modern technology which they already know they can utilize them and build the solutions. So the availability of developers and et cetera will be much easier now. And also like building this since when you build on your own solution like there is no restriction platform level restrictions are not there. So it will be provides us to build a more engaging responsive and seamless user experience on our website or web application. So the scale, scalability like since the feature of like moving the content delivery away from the backend system will provide us opportunity to scale the website like we can utilize any of the edge computing or wherever we should be able to deploy and scale as our business grows like we have the option to scale. And also the from the security perspective and also maintenance and everything easier right now with the headless proposal. There are like a lot of common misconception about using headless traditionally we get like headless headless is only for developers. So as I mentioned like a headless definitely provides a wide variety of options for the developers but also like with the performance and all other advantages we discussed before it provides like for marketers, non-technical content creators and for everyone headless will provide like improving your page performance and experience and everything like so. So headless provides it's not just for the developers but it's for marketers, non-technical users content authors, everybody take benefits from this headless headless. And also be like a headless is best suited for a single page application. Yes, like a headless definitely can be used in the single page application but with the we can take advantage of all the modern technologies and solutions like we should be able to build a traditional website mobile apps or any other front end applications by consuming this APIs. And there is another misconception like a headless means sacrificing Drupal features. So that's not true as well. In the upcoming we will be showing a demo where even like we will not lose any backend features that Drupal provide but also like a page level editing features also can be enabled when we deploy a headless Drupal. And Drupal is not SEO friendly. This is exactly opposite of what in from the reality. The websites built using the front end technology decoupled websites are always have better SEOs and also like because of as I mentioned before like because of the recent Google algorithm changes. This provides like the SEO has been drastically increased. We have seen customer migrating to the headless CMS have achieved like 90 plus light of score and which improved overall like increase their organic traffic and everything. And Drupal is less secure. This one also is not the right thing. Like Drupal can be more secure than traditional CMS by going with the headless like because we are separating the backend and front end. So which will help us to reduce the security like attack and improve security. And there is another misconception saying like a Drupal is only for the large organization. Definitely like large organizations can take advantage like because of the enterprise wide solution like a large organization can take advantages. But also we have seen like a lot of small businesses nonprofits and the individual bloggers also taking advantage of headless Drupal and building a solutions like which can really omnichannel cross channel solutions they were able to build. Headless Drupal is difficult to set up. It could be a case like several years ago but with the launch of like a starter kit and also like the API layers like very customized API layers which has evolved in the recent version of Drupal. It provides like a easy to set up and easy to manage. Headless Drupal is expensive. That's another misconception like because you can utilize like since we're gonna use the front end development frameworks it'll be easy to deploy even we can deploy them in the Edge Cloud and there's no need for a web server also like with the recent improvement in the Edge Cloud. Drupal requires like extensive coding knowledge. Again, like this one also a big misconception like the headless Drupal will allow us like anyone who knows like how to consume and use an API will be able to start developing their front end using any of the languages they know whether it's a Next.js, whether it's a React or it's a C sharp, whatever language they know if they know how to consume an API and how to display it's like we don't need any additional knowledge or anything like we can the team developers can use their existing knowledge and they should be able to build a headless Drupal solution. And the last one is like a headless Drupal is not user friendly. Again, like it's like the front end experience now with the performance and also like using the latest React.js and type of front end framework. We can improve the customer experience drastically. We can showcase like in our demo we will show like how we easy to filter filter a huge volume of search results and everything. Yaakartik you wanna talk about Drupal architecture? Thank you Satish. So I want to touch base on the different architectures available for us to solution or implement the Drupal application in a way like we want to have this data exposed to multiple channels and multiple organizations. So this can be easily achieved by following any of the architectures which best fits your requirements. So basically we have a traditional or monolithic architecture where we are using Drupal as a CMS. So it holds all the content and we have the front end templates available to render the data. The unified architecture where you have powerful tools and features of content management and user management will be using in the traditional Drupal templating. And next is like we have decoupled architecture. So Drupal is used solely as a content management system and the front end is built completely separately using a technology or a platform design whichever platform you are comfortable or best suit for your needs. So you can approach that solution. So this way it provides a greatest degree of flexibility but requires more development effort as I mentioned like since we are separating the layers like front end and back end we might need some expertise developing the front end frameworks using view or next year or react. And we need the coordination between the both teams to make it a better outcome. And next is the hybrid architecture or progressively decoupling. So this is the best shoot for organizations where they wanted to have or utilize the Drupal front end templates as well as exposing the data through the API. So some parts of the website or application are built using traditional Drupal templating and rendering techniques while other parts are built using some front end frameworks like I mentioned makeshares or view whichever we can. So this approach provides a balance between the flexibility and Drupal's out-of-work features. So we are not losing any kind of editing experience or any kind of user management or content management experience. So that is what it is about like the Drupal architectures which we can take up. And coming to the next, it is the key components of Headless Drupal when we are implementing any headless application. So we have, and coming to Drupal like we have these components like Drupal CMS we have the API or the web services we have different end frameworks. So authentication part is also the major component here and the content delivery and also the decoupled architectures of going over like Drupal CMS as we are well versed with Drupal and other CMS. So it has a powerful content creation and management capabilities including content types, fields, taxonomies and views. So and the API coming to the API component the Drupal provides an API that allows other systems to access and manipulate Drupal content. It is both like consuming the data and also we can update the data from the front end framework. And the next component is the front end framework. So which separates the Drupal front end component and we can use any framework like React, Angular or View is used to build the user interface for the Drupal headless application. So it communicates with the Drupal API to retrieve and display the content. So that's the main role of this component and authentication and user management basically handled by Drupal which provides user accounts, roles, permissions so we can still use the capabilities of Drupal authentication and users can log into the headless Drupal application using the same Drupal credentials which we have which we provide from the back end. And going over the content delivery Drupal provides a variety of options for delivering content to the front end including the RESTful web services, JS and GraphQL. The front end framework can choose best delivery method based on its requirements. So whatever is best choice for you like we can pick up the content delivery method. And also as I mentioned this all comes under the decoupled architecture where we are separating the front end layer and back end and we are using these services in between to transfer the data, talk between the front end and back end components. So the key considerations to move to headless Drupal so everyone has a question like why we should move to headless Drupal and what are the reasons behind moving to headless and what benefits we'll be getting out of it. So I'm going to just walk over the key considerations which you have to make while making the decision. So the content strategy is the main component here which you have to consider. So headless Drupal separates back end content management from the presentation layer. This means that you will not have a solid content strategy in place to ensure that your content is structured organized and optimized for delivery to different channels and devices. So you should have more focus on how you are structuring your content. And coming to the next consideration is that development expertise. So headless Drupal requires quite different skills like as I mentioned, like we need to have a Drupal back end development experience, side building experience. And also you'll need developers to develop different end frameworks which can be next year, so a few years and this should be well versed with implementing the API and also follow the microservices architecture and best possible standards to create the API. And next comes the integration requirements with headless Drupal, we need a lot. We need to integrate in the third party systems to deliver content to different channels and devices. As I mentioned, if you want to create a system for only channel experience like we need to deliver to different channels and the responses may vary depending upon what channel we are targeting. So this means you'll need to carefully evaluate your integration requirements, select tools, which will help you seamlessly connect between Drupal and other systems. And security considerations with headless Drupal, you are exposing your Drupal API to the internet which can create a security risk. You'll need to ensure that you have robust security measures in place to protect against the potential vulnerabilities. So we have, yeah, we have the secure communication and we have to follow the best coding practices. So we have to make sure like access and security protection are in place and we are also making regular updates to the Drupal core and contributed modules so that we are not giving any chance of leaking our vulnerabilities. So I'm going to talk about Drupal solution which we developed at all today. So like we developed an application using Drupal and we selected Next.js as a framework because it is getting more popular and it has a lot of capabilities and our front-end team also created a component library which we can reuse and kind of a framework which we can enhance the time to market for anyone who is going to opt for it. Yeah, we have implemented the solution using RESTful web services and JSON API modules which comes out of works with Drupal we configured the REST resources for content, file uploads, the web forms. So yeah, we structured them in a fashion like we want to expose the data to the different channels. So we are using JSON, like there are a lot of authentication methods available out of works with Drupal. We implemented this using JSON web token authentication and the RESTful APIs are authenticated with disability tokens. And also we have few customization implemented in our Drupal application to make sure like the responses API responses are to facilitate the required formatting and the structure based on the channel which is trying to utilize it. So we also implemented that as part of this solution. And yeah, we have a next year component library which is the most and which fits the best with the Drupal to consume the data and also like update the data. So it's kind of two-way handshake between the Drupal used as a content repository and the next year's framework. Yeah, thanks, you can take over, thank you so much. Thank you, Karate. So AQUIA also pulled together two starter kits that enable organizations in building headless Drupal applications. The first is AQUIA's headless starter kit and what you achieve with the starter kit is being able to accelerate your new headless Drupal application builds by up to 50%. So I will say this is meant for new headless Drupal projects but it really comes with a boatload of capabilities and features that enable your teams to work faster when building with headless Drupal. I'll touch on a few today. The first is a minimalist configuration for easy setup with access configuration for purely headless development in Drupal. The second is a specific headless developer role for front-end developers to have a dedicated role inside the CMS to access API docs, managing access for front-end applications, connecting right into the CMS. An API dashboard for front-end developers to get access to dedicated dashboards that manage all headless integration aspects within the CMS. Data modeling in headless mode, providing revamped admin navigation, bringing all the data modeling controls under a single menu. So making that navigation really seamless, really easy. Content preview and experience to create preview within the CMS to see the content through the front-end context right from within the headless CMS. So being able to see what that content is going to look like in the headless context but making it very easily previewed. And lastly, headless and hybrid UI modes so the ability to operate in a purely headless mode or in a hybrid mode where Drupal is still used to render a front-end. So that is covering off on the Acquia headless starter kit. But like I said, we do offer another which is the NextJS Starter Kit. So the NextJS Starter Kit gives you pre-built configuration and react components to speed up the creation of your new react-based front-end application. And why we chose NextJS? Well, it's really proven as popularity, maturity and flexibility to support decoupled headless and static architectures. So with the NextJS Starter Kit, you'll be able to achieve accelerated administrative setup with roles, users, consumers, API keys, NextJS site instances and more within a single step. So that single step setup makes it really easy. A starter kit for connecting NextJS with Drupal and the Acquia content model. So that makes that very seamless. And then the third is JSON API wrapper to handle all JSON API queries. And the last is starter react components for rendering the content available in the Headless Starter Kit and a default routing system mapping Drupal content types to react components. So again, making the seamless process of building out your Headless Drupal projects with the Headless Starter Kit for Drupal from Acquia and then also providing that front-end accelerator as well with our NextJS Starter Kit. So this is our application which we developed. So this, we have a carousel, we have two cards of content and we have a contact us block here at the end. So this is the homepage which we developed and all this content is coming from the Drupal GMS which we'll be showing you in the next few minutes. So going over to our professionals, so this is the page where we have lots of tons of data about the professionals which are available in different locations. So we can filter the ad filters and then fine-tune the results based on the applied filter. We can also see like we have few more filters from other locations. We can just select them and see how the results are getting fine-tuned. So this is again like selecting a new location. So you just see like the professionals available in those locations. We have another filter here, area of focus. So this bio professional has some area of focus tag. So we can filter these professionals by choosing the data of tags. We can also search by a keyword either by the name of the professional or let's say I'm going to search for com and we got this professional matching with the name. So snora and on clicking like we are going to the details page for that professional and these are the different sections which we implemented which are there in Drupal, all this content is getting pulled from Drupal using the RESTful API. I can show you the editing experience. So I can click on edit and this gets updated into the text field where we can do the inline editing. For this professional and here I can just scroll down and show you how we are editing the bio of this professional. We need some edits. Yeah, and yeah, this data is updated in real time and I just wanted to show the other section where interest of the particular professional we can just update this by making some changes and then click on save and this gets updated in real time. So as this content is updated I'm just going to go back to our professionals page to show you the changes are now reflecting in the listing as well with this data being pulled from the listing API and all this data which we modify is now available in Drupal. So I'm now going to show you the backend that Drupal CMS implementation. So we configured the RESTful API which comes out of works in Drupal like we configured them. We configured serialization. Yeah, we have token and JSON authentication token modules for providing the JWT authentication and I'm going to show you how we configured the RESTful APIs like we have these resources available, content, web form, our file upload and I can just edit our content and show you we have all these methods and then JWT authentication is what we are using as authentication method and yeah, so we configured everything and I'm just going to showcase one particular content type which is bio, which we just had a look at and here we have different fields added and then we are referencing these fields with paragraphs where we added paragraph types. I'm just going to edit one paragraph type and show you how we structure the fields to hold the content which we are showcasing in the UI. So let's make it on education and we have a lot of fields which are available for that particular paragraph and filtering by a content type we can see the list of bios available and Nora Peters, we just updated from Nora and to something Nora Peters so it is now reflecting back in Drupal. So just trying to edit and show you how we populated the content in the backend which is available in the front end in different sections as I showcased you. Yeah, so this is how we structure the all the categories applicable for this professional. Yeah, so this is a quick demo showcasing the capabilities of headless implementation using next year. So we'll finish off our conversation today with a couple of customer stories of how they were able to achieve success in leveraging headless Drupal. A couple of different industries but some really great stories. So we'll start off with PAC-12 which is the collegiate athletic conference and they would really wanted to provide connected applications to provide the best digital fan experience. I know some I'm a big sports fan March Madness is going on but really they wanted to provide the number one spot for their fans to go to for information. PAC-12 has connected apps on an array of platforms such as iOS, Apple TV, Android, Fire TV and they rebuilt their entire website PAC-12.com. So their applications present content such as team schedules, video info from social platforms so pretty dynamic content to their fans and connecting all of these applications with the most accurate content which as I said is dynamic it changes frequently proved to be pretty challenging for their team. So PAC-12 went out and leveraged headless Drupal to connect to and power their array of fan-facing applications via APIs and Drupal acts as the central nervous system. So really the piece that holds everything together orchestrating various microservices and the flow of key data across all of these apps. Leveraging headless Drupal and Acquia together PAC-12 was able to deliver 3,000 plus landing pages for all annual PAC-12 conference events then they were able to create all these in just five months and they also migrated all their existing video and can now host all pre-game, live game and post-game video on their new site. And in the first year on Acquia's platform PAC-12 networks doubled the number of hours people viewed content on their site. So a really great example of a real life way to leverage headless Drupal to increase customer digital experiences and connect those experiences across an array of applications. Our second example is a company called Livewire. They're an electric motorcycle brand and what they really wanted to do was deliver a rich multimedia digital experience that portrayed what it was like to ride one of their motorcycles. They also wanted to establish a single source of truth for their digital assets. And their previous site was designed completely from custom code which made their content updates very, very challenging with a heavy reliance on their developer team. And by shifting to a headless implementation with Drupal it lets Livewire integrate Drupal, their CMS and all the content that lives in Drupal into two different versions on their website. So overall they're able to improve their site performance but they're also able to boost their customer experience and satisfaction. And their team leveraged Drupal's rich API support to take a content as a service approach. So they were seamlessly integrating Drupal, their powerful CMS into their existing front-end application. And the new site effectively captures their brand, the experience of their brand and allows their communication specialists to seamlessly update media and all of the related content. So removing all of those barriers that they initially had by building with custom code. The results, they were able to implement in just one month. They launched five global sites in one month as well and they launched a pre-order page for one of their bikes, which sold out in minutes. So again, another great example of leveraging headless Drupal, accessing those rich APIs and delivering rich content that connects with customers and really drives incredible customer experiences. And our last customer success story is KCTS9, which is the Netflix of PBS and they're powered by Drupal of course, but they chose to build their experience with headless Drupal. Their site was really tightly integrated with a variety of PBS's APIs with station level curation, personalization and original content. And they built the site to serve APIs for future projects such as Roku and Apple TV and a number of apps. So again, another example of leveraging headless Drupal to use those rich APIs to serve content not just on current channels but looking towards those free to channels, what are you looking to expand into and how are you planning on serving all of your content to those new channels? And what KCTS9 was able to deliver by leveraging headless Drupal. So by taking that decoupled approach, they were able to create a streaming application that is three times stickier than their default PBS app based on videos played per visit. So they were able to increase their customer engagement threefold just by leveraging headless in a Drupal context. So great, another example, another great example of how a customer of ours leveraging headless Drupal was able to again impact that customer experience, really drive impactful engagement, gain revenue, gain loyalty, leveraging headless Drupal and really seeing some strong success. Thank you everyone. Have a good rest of your day or night.


Welcome to The Anxious Morning. Every weekday morning, we'll take a few minutes to go over some important lessons that you can use in your anxiety recovery journey. Away from the endless noisy scroll of social media, The Anxious Morning brings you support, education, inspiration, encouragement, and empowerment. For more, visit us at TheAnxiousMorning.com I know that many members of this community deal with all-day anxiety. I often hear descriptions of continuous anxiety that just sits in the background all the time, making one very uncomfortable. Often, there are no panic attacks or they may be few and far between, leaving the all-day anxious person confused and clinging to that three-letter label, G-A-D. It's important to understand that being anxious all day does not automatically mean you have GAD. People with panic disorder, agoraphobia, and health anxiety are also often anxious all day too. So be mindful of that. You may get a diagnosis of GAD from a qualified clinician, or you may not. Either way, the label is not all that important because it does not indicate that you are in a special situation that is impossible to deal with. GAD is not a life sentence. Even if you do have GAD, you do not have to be doomed forever to be anxious and unsettled during every waking moment. One of the hallmarks of GAD is persistent worry, focus, or rumination about a number of things that may change from day-to-day or even hour-to-hour. That worry, focus, and rumination shows up as anxiety, and it is very unpleasant. Someone with GAD isn't necessarily anxious about being anxious in the same way that someone with panic disorder might be, but the GAD person often winds up more anxious than they need to be simply because they can't find a way to solve the problem of the anxiety that makes them uncomfortable, though may be not afraid. This is not really news though because people with GAD often get anxious about trying to solve, know, understand, fix, and control everything. In fact, there is a segment of the professional mental health community that will point at traits like perfectionism, people pleasing, overthinking, overplanning, excessive worrying, and excessive focus on problem-solving as common underlying drivers of GAD. Odds are that you are well aware of the allow it and let it be there without engagement advice when it comes to dealing with anxiety. This is really hard for somebody with panic disorder because they fear immediate danger from the anxious state itself, but this is also hard for someone with GAD because leave it alone is not a thing that feels right to do ever under any circumstances. This is especially true in the face of a really uncomfortable anxiety problem that they can neither understand nor solve. An unanswerable question wrapped around a seemingly unsolvable problem? This is damn near nightmare scenario for many people that suffer from all the anxiety or they have gotten a GAD diagnosis. Why? Because problem-solving and knowing. So maybe you have GAD, maybe you don't. Even that statement might make you anxious to some degree because uncertainty. But if this is a thing you are struggling with, take some time to think about your propensity to problem-solve, know, fix, predict, control, or perfect. Are you the hyper-responsible person that feels like the health and happiness of the world is on your shoulders? Are you driven to please everyone to avoid being judged or plunged into conflict? If you're wondering why you're anxious all day and wondering, what about GAD? Considering some of this may start to shed some light on your situation. The mystery of all day anxiety and GAD sometimes begins to reveal itself when examined from this point of view. Tomorrow we'll examine the difference between managing your anxiety and just hanging on because you're afraid. Hey, if you're enjoying the podcast and you'd like to get a copy of it delivered every morning into your email inbox, including a full text transcription, head on over to theanxiousmorning.email and sign up for the newsletter. And if you're listening on iTunes or Spotify or someplace where you can leave us a rating or a review, take a moment and rate the podcast and maybe write a small review. It really helps us out. Or just tell a friend about us. Thanks a lot.


Hey, good morning, good afternoon, good evening, and welcome to our session Architecting Geodistributed and Hybrid 5G Edge with Kubernetes. My name is Sachin Rathi, I'm responsible for edge technologies at Red Hat, and I have with me Robert Belson from Verizon, Robbie. Thanks Sachin, and hello everyone, thanks so much for joining this session. We're super excited to tell you a little bit more about our experiences working together to build the next generation of hybrid mobile edge compute applications using Kubernetes. And I think it all starts with defining what the edge actually is, and that it's an inherently ambiguous term. I'd argue that the edge is both the device you often have in your back pocket, the various 5G radios you might see as you walk along a city street or on the highway itself, as well as anything in between. Any edge endpoint could be defined as part of an overall cloud continuum. And what gets us so excited about the edge isn't just that it's more performant, it's not just the speed, the latency, the throughput, but it's that you can start to unlock new revenue streams because you can often introduce new features as a result of the edge topologies. The ability to unlock innovation, drive new revenue streams, while also having a more performant end user experience, we think is a really exciting opportunity. And that's why we teamed up with Red Hat to explore this, particularly on the architectural side, in earnest. I want to talk a little bit about the challenges here, because while edge applications unlock all of these fascinating capabilities, they're pretty difficult to build. As you think about edge use cases that necessitate higher performance, perhaps a disaster response-based use case, today you could find yourself in a scenario in the absence of the edge that the actual workload is a thousand miles away from those end devices. That's not going to work in the future. More broadly, can you introduce the edge in such a way that doesn't disrupt the existing ways you deploy applications and the existing ways you orchestrate your containerized workloads? And lastly, as you start to introduce new paradigms, not just for the cloud itself but your device fleet, are you going to know ahead of time whether that device is connected to a public network, a private network? Could we find ourselves in a world where you have a mix of devices and then how does your edge environment care for that? Do you need to decide ahead of time? To all of those challenges, we worked with Red Hat to address each of those by trying to create a Kubernetes-native implementation to solve these challenges. Now, when looking at Kubernetes solutions suitable for edge, we're not just looking at edge deployment option, but we're looking at an end-to-end solution. This is where OpenShift, which is a Kubernetes distribution, comes into play. It's a solution that takes care of development of apps, provide consistency in their deployment, as well as maintains consistent resource consumption no matter where it's deployed. OpenShift also has capability to interface with any infrastructure components, whether it's networking, storage, support various CPU architectures and GPUs, depending on the use cases. From a security perspective, how data is handled at edge is also of paramount importance and for that, OpenShift provides highly secure solution built on rel core OS. With OpenShift, you have a solution that can be deployed seamlessly or any infrastructure using its native capabilities, whether it's full deployment or installing on existing environment. It can also be sized based on the use cases, which could be a single node deployment on a very restrictive environment to possibly a remote managed environment number of nodes deployed in different sites. And as you think about the reference architecture here, at the highest of levels, there are ongoing discussions about how to best deploy Kubernetes at the edge. From our experience, what we think is going to be most successful from a mobile edge perspective is to take that control plane for a given region and actually centralize it in the region itself. And then for each incremental set of edges, each of which could be separated by over a thousand miles apart, the nodes would essentially be the spoke in the hub and spoke architecture. That way, you're reusing the same control plane. It's cost efficient. It's easier to manage. And in a world, particularly in the future of 10, 20, 50, 100 edges, you reduce the complexity of management. Nonetheless, now you'll have challenges around multi-cloud, multi-region. What do I do? And how do I keep the simplicity? That's where OCM comes in. Now, edge is not limited to a particular geography or technology. Edge could be private to an enterprise or public where it can be accessed by anyone. It could be on a cloud platform or multiple disparate cloud platforms. However, the need to manage from a central location still remains. This is where open cluster management project comes into play, which is a CNCF project. Open cluster management, which is supported as advanced cluster management by Red Hat, solves the problem by deploying an ingesting cluster configuration from multiple Kubernetes platforms and use it to manage edge application deployed anywhere. Once clusters are under advanced cluster management, users can get full observability and can manage all Kubernetes cluster from a single dashboard. Orchestration of applications can be done based on various policies, making sure that the deployment is done based on your compliance requirements. Now, when we look at infrastructure automation, it requires use of software to create repeatable instructions and processes that reduce human interaction and makes management less error prone. The right automation platform, install and running in the right location, can improve activities like provisioning, configuration management, security and compliance. Those benefits of automation are more noticeable when the automation software is running as close to the thing it's automating. When automation is rolled out to the edges of the network, it will help speed up the transactions. Now, Ansible Automation Platform, which was used in this case, make use of blueprints of automation tasks called Playbooks. Ansible Playbooks are frameworks that can program edge applications, services, server nodes, infrastructure, Kubernetes clusters, et cetera. Ansible Automation Platform always runs as the control node, the location at which automation tasks execute from. This allows us to automate edge location with the lowest latencies. But now let's talk about one additional challenge. In the world where you fully automated and abstracted away the complexity of the id for itself, you've still introduced a problem around edge discovery. Even in the case of a single cluster, how does a given mobile application understand natively which edge is the closest edge? In fact, if we borrow from the airline industry when they often say the closest exit may be behind you, that very much is true in an edge discovery scenario. It could very well be that you're in Boston, a highly immersive application needs to be delivered, and the closest edge could be in Miami. It all has to do with the topology of the mobile network, and the nature of where your device is in fact anchored within the packet core of our mobile network. With that said, as a developer, you don't have to manage that complexity. You're already managing the complexity of the infrastructure itself. That's why we developed the edge discovery service, an API that any developer can use to solve these challenges. It's a simple API that essentially allows you to take advantage of CRUD operations for a service registry, populating edge endpoints with an FQDN, the IP address for those carrier-facing workloads, and then you just query it passing your IP address as a mobile device or IoT device and out comes the closest edge. It's incredibly powerful, but then we ask the question of what's the right infrastructure platform that allows us to automate the complexity of keeping the service registry up-to-date? First and foremost, that's where OpenShift comes in. We wanted to create a future-proof architecture that in a multi-cloud world, but also a hybrid cloud world where those specific carrier-facing endpoints could in fact be public and private network facing. You just want one single pane of glass. That's exactly what you're seeing here on the left-hand side. These machine sets are spanning a physical data center or rather a physical outpost in Dallas, and then equipment that you've perhaps never even seen before because it's a wavelength zone in Boston in New York City on top of the region itself.  And then by inspecting each of these nodes or each of these workloads, you can see all of that relevant metadata right at your fingertips. But going back to the Edge Discovery service, what we did is we created an admission controller that anytime requests are made to the Kubernetes API server to expose a given workload that thus would necessitate for the Edge Discovery to actually know about this workload, we would then intercept that request, figure out the end node being exposed, take that metadata, populate it to the Edge Discovery service, and then keep that valuable state information in a config map. So this is how we're using Kubernetes native objects to bring together network intelligence and a hybrid multi-cloud mobile edge computing world. We recognize that this is just the start. We invite you to join us on this journey by visiting github.com slash Verizon slash 5GS tutorials to learn more. And we hope that together, Verizon and Red Hat can be your trusted partner for solving your next generation of challenges and opportunities on the hybrid mobile edge. Thanks so much and hope you enjoy the rest of KUKON. Thank you.