So I'm gradually going to take us back a little bit to protein structure because in particular in this class we want to use bioinformatics to better understand protein structure. One very important measure that you've already used in the lab but that we're going to talk more about today is RMSD root mean square displacement or deviation that I define like this. I'm going to need a large bracket here. So I take the sum of all atoms n in a particular protein and then I need to calculate x i minus x i ref squared plus i y minus i y ref squared needs to be longer plus z i minus z i ref squared and then divide that by the number of residues. I think I got that right. What this tells us if the reference here that would be for is my target the known x-ray structure while x i is my prediction or where I am running in a simulation. The whole idea here is what this is then going to measure is kind of the average error between two structures. If this error is one angstrom that means that the average error of any atom corresponds to roughly the length between a carbon and the hydrogen that's nothing it's an amazing structure. If it's two three angstroms it's a pretty good structure quite usable at three pharmaceutical companies will start complaining at five all bets are not quite off and it's bad and at six seven you don't have any similarity at all. So when we talk about models we're somehow going to relate this to RMSD and say how good they are. There are a few other ways that we can measure scores that I won't define but there's one called GDT. It's called global distas test that goes from zero to a hundred and I would say that zero at zero we don't have any similarity at all 70 80 really good and at 90 that would be an experimental structure. So if two structures have a GDT of 90 that means that they're basically experimental that's as good as it gets. There is a reason for mentioning that now I will come back to it later whenever you can forget about it. The RMSD it turns out is intimately related to the sequence similarity not one on one but on average. So if we plot the expected sequence conservation versus the rms it turns out that if I'm well of course if I'm at 100% per sequence identity the rmsd should be zero right but already when I have say 75% of the residues in the core of the protein identical I should expect this rmsd to be in the order of 0.5. So if only 25% of the residues differ it's exactly the same structure and then this will of course go up if but even if only 25% of my structures match I actually expect on average to be within 1.5 angstrom rmsd. The take-home message of this plot is twofold. First you don't need as much identity as you think. Three out of four residues can be different and they will still have the same structure on average very few exceptions. Second it's a gliding scale if we have 80% identity it's of course better than if you only have 20 but you should be fairly certain about this fairly early. This is probably worth writing down. We occasionally talk about this that some sort of scale and then we can say present identity sequence. Now of course there is a difference here right identity just just counts if things are really identical alanine to alanine there is a difference if you replace an alanine with a tryptophan or an alanine with a glycine but for now this is an average so we don't care. So if we start from zero and go maybe up to so we say 20 then the second zone might go up to say 40 and well then all the way up to 100. Here we are sad this is so-called midnight zone below 20% sequence identity I can't really say anything I wouldn't I wouldn't trust it that doesn't mean that the sequences are not homologous it's just that I can't say for certain. If you are from roughly 40% sequence identity we are very happy this is a so-called safe zone if you have 40% sequence identity in those sequences they will be homologous I would almost say that I'm going to eat my left shoe if that's not true but remember that I showed you in a previous lecture that it might be possible for us to design something up here but again that's an exception if you have 40% identity between two sequences they're going to have the same fold but that leaves this interesting area this is a so-called twilight zone or it used to be the twilight zone I would actually argue that these limits have moved down in the twilight zone we might be able to determine structures of proteins if we're lucky and I would actually argue that this has narrowed a bit so that the twilight zone is probably from 20 to 30 percent from 30 percent I would be considered quite safe and I would probably trust emoji already at 30 percent mostly because we've had better and better algorithms to detect sequence similarity and evolutionary patterns but we'll come back to that. The short story here if somebody shows you two sequences and they have 30 percent sequence identity or better you should believe that they have the same fold once they only have 20 percent you're looking at noise don't trust it this twilight zone is fairly narrow but this is of course where a lot of the fascinating research happens that's how we move down from 40 to 30 here so how similar is similar if a couple of proteins share 30 percent sequence what will they look like I have an example of exactly that for you three sequences here they share just under 30 percent of the residues as you will see they're not they're not exactly identical there are some minor differences here in particular that helix is a bit turned the fold is the same you have the same number of secondary structure elements but there are some minor changes relative to this is quite typical but remember this is 30 percent it might even be a bit of a large change for 30 percent you can if these are so similar at 30 percent you should guess what happens if two things are 80 percent identical you would not be able to tell them apart this will now enable us to use bioinformatics in particular homology and sequence similarity as a way to detect in practice the things we've talked about in physics because remember all these all my discussions about folds similarity evolution it's completely true what I told you in the physics lecture but the only way for us to know it then was if we actually had those entire faults right what bioinformatics now enables me to do is get those directly from sequence if I only have 30 percent identity and I have 207 million really good sequences and the uniprot data bank today


Welcome to lecture number 32. In this particular lecture, we will continue our topic that is saline water intrusion in coastal aquifers and in this particular lecture, we will cover our previous topic that is burden, Gaibin, Herzberg principle. Basically, we will continue from our previous lecture and second topic, we will cover analytical solution of saline water intrusion in coastal aquifer. So, in our last lecture, we have seen that if we have one free attic aquifer, this is basically impermeable bottom, this is the location of ocean with our z axis pointing upward and this is the location of interface that is interface between salt water and fresh water. And we have ground water table located at this position, this is ground water table. So, let us consider any arbitrary section in which this depth below ocean level to the position of interface, we can denote it as xi and head above ocean surface that we can denote it as H f and corresponding head in ocean, we can denote it as H s. We have seen that with our assumption that is Gaibin Herzberg principle, we can express this xi in terms of H f as H f rho f by rho s minus rho f into H f. In this particular derivation, we have assumed that our salt water wedge that is basically stationary or stagnant. With this assumption, we will continue our derivation for saline water intrusion in different coastal aquifer formations that is first one will be confined then unconfined and for oceanic islands.  So, with this assumption, we can continue our derivation. So, first of all let us see that how to use this Borden-Gaibin Herzberg principle in the field to identify the salt water intrusion in coastal aquifers. So, with this with Gaibin Herzberg principle, it is possible to the salt water fresh water interface. So, what are the steps for identification of this salt water fresh water interface? So, first point is that network of shallow wells are developed observation water table height. So, first of all we need to install some good number of piezometers in the field to identify the location of groundwater table locally. Next thing is that we can use contour plotting for this groundwater table height distribution. So, contour lines showing the fresh water head HF are drawn using some interpolation method. What are the interpolation methods we can use? One interpolation method may be creaking or inverse distance wetting method we can utilize. So, for example, we can use creaking or IDW or any recent techniques for plotting our contour lines for the fresh water head HF. Then the interface depth the interface depth xi which is a function of x and y is represented by the same set of contour lines this is drawn within the plotting. And fourth one the location of aquifer bottom aquifer bottom which is again function B x y is found from geological maps. And final one the intersection of this two surfaces that is the intersection of the two surfaces xi x y and B x y is sought which represents the saltwater tow location. So, with this method let us say we have our coastline like this which is coastline. And this is our ocean and with dotted lines I am representing the fresh water equipotential lines these are basically fresh water zone these lines are fresh water fresh water lines. And the location of tow that is that is the intersection of two surfaces may be located as this. So, this is basically location of tow. So, for this particular location saltwater has entered into coastal aquifer. So, saltwater invaded zone. So, we have saltwater invaded zone then we have fresh water zone and these are our fresh water equipotential lines. So, using Geiben-Hurtsberg principle we can easily identify the tow location in the field. However, for complex geological formation and non-stationary interface condition this is not valid. Geiben-Hurtsberg principle considers stationary saltwater wage assumption for its derivation. However, in complex geological conditions we cannot directly use that assumption for practical modeling or practical use. So, next thing we will try to find out the analytical solutions for our coastal aquifers. So, for analytical solutions for stationary interface. So, basically for these solutions we will utilize our Geiben-Hurtsberg principle and we will try to see the simplified analytical solutions for simple geological conditions. So, first thing with this analytical solution what we can do we can identify the shape of the sharp interface shape of the sharp interface. Next we can find out the relationship between the extent of sea water intrusion and flow of fresh water to the sea and why this relationship is necessary. This relationship is necessary for taking aquifer management decisions and sustainable yield identification for coastal aquifers. So, this relationship is necessary aquifer management decisions or for identification of sustainable yield of a coastal aquifer. So, we will use certain assumptions for our derivation. So, what are these assumptions? First of all we will consider that aquifers bottom is horizontal. So, aquifer bottom is horizontal the flow is assumed to be everywhere perpendicular to coastline with a stationary interface. That means our fresh water is moving sea water is stationary and we will consider that sea water wedge length L. One important assumption is that Dupitz assumption of essentially horizontal flow is valid assumption essentially horizontal flow is valid. So, let us consider a case of confined aquifer and for this condition we will try to find out the nature of interface. So, interface in a confined coastal aquifer. So, interface in a confined coastal aquifer. So, let us draw the conceptual thing we have horizontal bottom which ensures the horizontal flow in the aquifer towards sea. So, thickness of this confined aquifer is B. Again we have the interface this point T or capital T is called as tow location. Then length of this wedge that we have already assumed to be L. Then location of sea surface or ocean surface we have this and location of this ground water table is this green thing. So, for a particular location we have three different distances first one we will denote it with xi. Next one this is constant depth between ocean surface and the aquifer top that is B and this H f is the fresh water head above ocean surface up to ground water table. So, we can consider this zone as fresh water zone and this one is basically salt water zone. So, with this configuration we can consider that there is horizontal flow which is occurring from aquifer towards the sea and our x axis starts from this tow location towards sea. So, with this fundamental assumptions and configuration we can start our derivation. What is this Q f naught denoted in this position? This is the difference between the total inflow to the aquifer its right side boundary the pumping from the aquifer in the aquifer strip to the right of the point T or location of tow. So, next thing in this particular case another assumption is there that is B is much much lesser than our wedge length and B is the thickness of aquifer. So, using our Geiben-Hurtsberg approximation we have we have this H f is the fresh water head above ocean surface up to this ground water table. So, we can express our this xi plus B that is the distance below ocean level up to interface that we can denote as denote it as xi plus B equals to rho f by rho s minus rho f into H f or in simplified form xi plus B equals to delta H f or H f we can directly use it as B plus xi plus B by delta. So, for the small configuration we can say that our fresh water zone we have flow which is K f or we can write it as basic equation of fresh water flow and this is 1 D and only horizontal flow condition we have K f xi by x D h x by D x equals to constant what is this constant this is Q or flow at location x equals to 0 which is equals to Q f naught. So, what is this this is basically e or flow or Darcy and flow is equals to the flow which is coming from right and side boundary and basically we have seen this is the difference between total inflow to the aquifer from the right hand side boundary and pumping from the aquifer. So, using this thing we can write again we will just write K f xi x D h f x D x equals to Q f naught for this particular situation now we can use our Kaibman Hertzberg principle. So, we can replace this H f with xi plus B by delta or K f xi plus D by D x B by delta equals to f or this is K f by 2 2 xi D xi by D x equals to Q f naught or this thing we can directly write it as i square D x and the right hand side will have delta Q f naught by K f with this we can use integration. So, from integration we have i square equals to 2 delta Q f naught by K f to x plus c the c is the integration constant. Now, if we have x equals to l then this psi value is 0 which implies that c is equals to 2 delta Q f by K f into l.  So, important thing is that we have considered our coordinate system from tau location towards left. So, if we have x equals to 0 that is at the location of tau we have xi equals to B which is again B is the depth of the confined aquifer. So, this implies that we can write it as B square 2 delta Q f naught by K f into l because x equals to 0. So, basically this particular relation relates with our depth of the confined aquifer. This is del is the density ratio which is used for Gauguin-Hurtsberg principle K f is the freshwater hydraulic conductivity Q f as we have defined in our assumptions and l is the sea water wedge length. So, this is somewhat parabolic in nature. So, we can say that saltwater interface in confined aquifer is parabolic in nature. So, next thing we will start our interface for interface interface in a free attic aquifer. So, in this free attic aquifer this is also our unconfined aquifer, unconfined coastal aquifer. Again we can draw our basic configuration for the problem we have horizontal impermeable bottom. This is the location of ocean and location of interface can be denoted with this red line and this is T or 2 location with saltwater and freshwater thing and this is width B which is depth below this ocean surface level up to impermeable bottom. Again we have this ground water table which is free attic surface and we can assume some constant recharge rate n. So, with this height of ground water fresh ground water table above ocean level is h f and below this ocean surface level till the interface we have distance xi and saltwater wedge length this is again l and our coordinate system we are assuming from the tow location towards left and we have again this q f naught which is the difference between the flow which is coming from right side boundary and this is the difference between flow and pumping. So, with this situation this is h s and this precipitation rate or recharge rate this precipitation rate we can consider it as n. So, within this interface if we consider one small elemental portion then we will see that for this elemental portion we have this is n which is recharge from the top and q f is a flow coming to this strip and q f plus d q f by d x into del x this is the distance the flow which is coming from left boundary and which is going out from the right boundary and going out from the left boundary. So, if we do mass balance for this particular configuration then we will see that q f minus q f plus d q f by d x into delta x plus we have n into delta x equals to 0 or we have situation where d q f by d x this is n or 0.  So, this q f at the right hand side boundary we have this value q f is equals to q f naught.   Again from our fundamental relationship that is we have derived that is k q f d x n equals to 0 and in this one if we substitute q f then we will get d by d x which is minus k f h f xi d h f d x plus n equals to 0 this is our relation number 1 or 32.1 let us denote it and from this one if we substitute our Guyburn Hertzberg principle relationship. So, k f again this is 1 plus delta divided by delta square d x plus n equals to 0 or we can have a relationship where this d by d x xi square d x equals to minus n 2 n delta square divided by k f 1 plus delta. So, from this one we can derive this square x equals to minus 2 n delta square k f 1 plus delta x plus c 1. So, from our relationship from 32.1 we have seen that d of xi square d x at x 0 or x equals to 0 x equals to 0 this value is equals to 2 q f delta square by k f 1 plus delta. So, if we utilize this thing for our case then we have c 1 is equals to minus 2 q f naught delta square by k f 1 plus delta.  So, again integrating this one we will get phi square equals to minus 2. So, 2 2 will cancel this is x square.  So, if we have x equals to 0 we will get xi equals to b. So, with this one we can get that c 2 equals to b square. So, finally, we can write our equation as xi square equals to minus 2 n delta square by k f 1 plus delta into x square by 2.  If we have recharge is equal to 0 then n equals to 0 and we can get simplified relationship with n equals to 0 and if we have xi equals to 0 at x equals to l we can get this is b square equals to delta square f 2 q f naught plus n l into l. So, again we have found out one relationship between depth of this free attic aquifer from ocean surface to impermeable bottom delta is the our Gaiman Herzberg density relationship k f is freshwater hydraulic conductivity q f as we have defined in our assumptions and n is the recharge rate l is the length of the wedge. So, with this relationship we can easily find out the shape of the wedge and this is the final relationship between different parameters in confined aquifer. So, we can utilize this thing for our calculations. So, we can conclude our lecture with this particular confined aquifer, unconfined aquifer condition, unconfined aquifer condition that we have derived here and in the next lecture we will start with case where we will try to find out the ocean island case in which we will try to utilize the condition for symmetric flow symmetric radial flow conditions. Thank you.


From around the globe, it's theCUBE with digital coverage of DockerCon Live 2020. Brought to you by Docker and its ecosystem partners. Everyone welcome back to DockerCon 2020, hashtag Docker 20. This is theCUBE and Docker's coverage of DockerCon 20. I'm John Furrier in the Palo Alto studios with our quarantine crew. We've got a great interview segment here and big news around developer workflow code to cloud. We've got Amanda Silver, corporate vice president, product for developer tools at Microsoft and Scott Johnson, the CEO of Docker. Scott, you had a great keynote. Talking about this relationship, news has hit about the extension of the Microsoft partnership. So congratulations, Amanda. Welcome to theCUBE. Thanks for having me. Amanda, tell us a little bit about what your role is at Microsoft. You guys are well known in the developer community. You had a developer ecosystem when, even when I was in college going way back. Very modern now cloud is the key code to cloud. That's the theme. Tell us about your role at Microsoft. Yeah, so I basically run the product, product design and use a research team that works on our developer tools at Microsoft. And so that includes the Visual Studio product as well as Visual Studio code that's become pretty popular in the last few years. But it also includes things like the .NET runtime and the TypeScript programming language as well as all of our Azure tooling. So what's your thoughts on the relationship with Docker? I'll see the news extension of an existing relationship. Microsoft's got a lot of tools. You've got a lot of things you guys are doing bringing the cloud to every business. Tell us about your thoughts on this relationship with Docker. Yeah, well, we're very excited about the partnership for sure. You know, our goal is really to make sure that Azure is a fantastic place where all developers can kind of bring their code and they feel welcome. They feel natural. We really see a unique opportunity to make the experience really great for the Docker community by creating more integrated and seamless experience across Docker desktop, Windows and Visual Studio. And we really appreciate how Docker has kind of, you know, supported our Windows ecosystem to run in Docker as well. Scott, this relationship and extension with Microsoft is really, I think impressive and also notable because Microsoft's got so many tools out there and they've so successful with Azure. You guys have been so successful with your developer community but this also is reflective of the new Docker. Could you share your thoughts on how this partnership with Microsoft extending the way it is with the growth of the cloud is a reflection of the new Docker? Yeah, absolutely, John. It's a great question. One of the things that we've really been focused on since November is fully embracing the ecosystem and all the partnerships and all the possibilities of that ecosystem. And part of that is just reality that we're a smaller company now and we can't do it all, nor should we do it all. Part of it's the reality that developers love voice and no one's going to change their minds on choice. And third is just acknowledging that there's so much creativity and so much energy outside the four walls of Docker that we'd be filly not to take advantage of that and welcome it and embrace it and provide that as a phenomenal experience for our developers. So this is a great example of that. The sneak partnership we announced last week is a great example of that and you're going to see many more of partnerships like this going forward that are reflective of exactly this point. You've been a visionary on the product side of the interview before. Also deploying is more important than ever. That whole workflow simplifying it's not getting complex. People want choice, building code, managing code, deploying code. This has been a big focus of yours. Can you just share your thoughts on where Microsoft comes in because they got stuff too.  What's your thoughts? Right, so it needs to work together, right? Because developers want to focus on their app. They don't want to focus on duct taping and stringing together different siloed pools, right? And so you can see in the demo and you'll see in demonstrations later throughout the conference just the seamless experience that a developer gets in the doc command line, interoperating with Visual Studio Code with the doc command line and then deploying to Azure. And what's wonderful about the partnership is that both parties put real engineering effort and design effort into making it a great experience. So a lot of the complexities around configuration, around default settings, around security, user management, all of that is abstracted out and taken away from the developers so they can focus on applications and getting those applications deployed to the cloud as quickly as possible. Getting their app from code to cloud is the walkward or the call to action for this partnership. And we think we've really hit it out of the park with the integration that you saw. Great validation and a critical part of the workflow you guys have been part of. Amanda, we're living in a time we're doing these remote interviews. The COVID crisis has shown the productivity gains of working at home and working and sheltering in place but it also has highlighted the focus of developers mainly who have also worked at home. They kind of used to this. You see the rigs I saw at Microsoft Build, some amazing rigs from the studios of these guys streaming their code demos. This is a Cambrian explosion of new kinds of productivity. You get the world's getting more complex at scale. This is what cloud does. What shared thoughts on this? Cause the tooling is more tools than ever, right? So I still got to deploy code. It's got to be more agile. It's got to be faster. It's got to be at scale. This is what you guys believe in. What's your thinking on all these tooling and abstraction layers? And at the end of the day, developers still got to do their job. Yeah, well, absolutely. And now even more than ever, I mean, I think we've certainly seen over the past few months a more rapid acceleration of digital transformation than has really happened in the past few years. Paper processes are now becoming digital processes. All of a sudden, everybody needs to work and learn from home. And so there's just this rapid acceleration to kind of move everything to support our new remote first lifestyle. But even more so, we now have remote development teams actually working from home as well in a variety of different kinds of environments, whether they're using their own personal machine to connect to their infrastructure or they're using a work-issued machine. It's more important than ever that developers are productive, but they are productive as a team, right? Software is a team sport. We all need to be able to work together and to be able to collaborate. And one of the most important aspects of agility for developers is consistency. And what Docker really enables is with containerization is to make the infrastructure consistent and repeatable so that as developers are moving through the lifecycle from their local desktop and developing on their local desktop to a test environment and to staging and to production, it's really, it's infrastructure for developers as well as operations. And so it's that infrastructure that's completely customizable for what the developer's operating system of choice is, what their app stack is, all of those dependencies kind of running together. And so that's what really enables developers to be really agile and have a really, really fast iteration cycle, but also to have that consistency across all of their development team. And we now need to think about things like how are we actually going to bring on interns for the summer and make sure that they can actually set up their developer boxes in a consistent way that we can actually support them and things like Docker really help with that. As your container instances and visual studio cloud that you guys have has had great success, there's a mix and match formula here. And at the end of the day, developers want to ship the code. What's the message that you guys are sending here with this? Because I think productivity is one, simplification is the other, but as developers on the front lines and they're shipping in real time, this is a big part of the value proposition that you guys are bringing to the table. Yeah, I mean, the core message is that any developer and their code is welcome. And that we really want to support them and power them and increase their velocity and the impact that they can have. And so, you know, having things like the fact that the Docker CLI is natively integrated into the Azure experience is a really important aspect of making sure that developers are feeling welcome and feeling comfortable. And now that the Docker CLI tools that are part of Docker desktop have access to native commands that work well with Azure container instances, Azure container instances, if anybody's unfamiliar with that is the simplest and fastest way to kind of set up containers in Azure. And so we believe that developers have really been looking for a really simple way to kind of get containers on Azure. And now we have that really consistent experience across our services and our tools. And Visual Studio code and Visual Studio extensions make full use of Docker desktop and the Docker CLI so that they can get that combination of the productivity and the power that they're looking for. And in fact, we've integrated these as a design point since very early on in our partnership when we've been partnering with Docker for quite a while. Amanda, I want to ask you about the tool chain. We've heard about workflows, making it simpler. Bottom line from a developer standpoint, what's the bottom line for me? What does this mean to me, everyday developer out there?  And so, you know, Microsoft has been a developer company since the very, very beginning with, you know, Bill Gates and GWBasic. And it's actually similar for Docker, right? They really have a developer first point of view which certainly speaks to my heart. And so one of the things that we're really trying to do with Docker is to make sure that we can create a workflow that's super productive at every stage of the developer experience no matter which stack they're actually targeting. Whether there's targeting node or Python or .NET and C sharp or Java, we really want to make sure that we have a super simple experience that you can actually initiate all of these commands, create, you know, Docker container images and use the Docker compose files. And then, you know, just kind of do that consistently as you're deploying it all the way up into your infrastructure in Azure. And the other thing that we really want to make sure that even post deployment, you can actually inspect and diagnose these containers and images without having to leave the tool. So we also think about the process of writing the code, but also the process of kind of managing the code and remediating issues that might come up in production. And so, you know, we really want you to be able to look at containers up in the Azure, up that are deployed into Azure and make sure that they're running and healthy and that if something's wrong that you can actually open up a shell and be in an interactive mode and be able to look at the logs from those containers and even inspect one to see environment variables or other details. Yeah, that's awesome. You know, writing code, managing code and then you got to deploy, right? So what I've been loving about the past generation of agile is deployment has been faster to deploy often and all the time. Scott, this brings up the ease of use, but you want to actually leverage automation. This is the trend that you want to get into. You want to make it easy to write code, manage code, but during the deployment phase, that's a big innovation. That's the last point, making that better and stronger. What's your thoughts on simplifying that? But that was a big part of this partnership, John, that the Docker and Microsoft embarked on. And as you saw from the demo in the keynote, all within the Docker command line, the developers able to do in two simple commands, deploy an app, defining compose from their desktop to Azure. And there's a whole slew of automation and preconfigured smart defaults and our same defaults that have gone on behind the scenes. And that took a lot of hardcore engineering work on part of Docker and Microsoft together to simplify that and make that easy. And that goes exactly to your point. We just like the simpler you can make it, the more you can abstract away to kind of the underlying plumbing and infrastructure, the faster devs can get their application from code to cloud. Scott, you've been a product CEO. You've been a product person, CEO, but you have a product background. You've been involved with the relationship with Microsoft for a long time. What's the state of the market right now? I mean, obviously Microsoft has evolved. Look at just the performance, corporate performance. The shift to the cloud has been phenomenal. Now developers getting more empowered. There's more demand for the pressure to put on developers to do more and more creativity. So you've seen this evolve, this relationship. What does it mean? Yeah, it's honestly a wonderful question, John. And I want to thank Amanda and the entire Microsoft team for being longstanding partners with us on this journey. So it might not be known to everyone on today's event but Microsoft came to the very first DockerCon event way back in June, 2014. And I had the privilege of greeting them and welcoming them and they were full on ready to see what all the excitement about Docker was about and really embrace it. And you mentioned kind of openness and Microsoft's growth over time in that dimension. And we think Docker together with Microsoft have really shown what an open developer community can do. That started back in 2014 and then we embarked on an open source collaboration around the Docker command line of the Docker engine bringing that Docker engine from Linux and now moving it to Windows applications. And so all of a sudden the promise of write once and use the same primitives, the same formats, the same command lines as you can with Linux onto Windows applications. We brought that promise to the market and it's been an ongoing journey together with Microsoft of open standards base, developer facing, friendliness, ease of use, fast time to deploy. And this partnership that we announced yesterday and we highlighted at the keynote is just another example of that ongoing relationship. Laser like focused on developer productivity and helping teams build great apps. Why do you like Azure in the cloud for Docker? Can you share why? Well, it's as Amanda has been sharing like it's super focused on what are the needs of developers to help them continue to stay focused on their apps and not have their cognitive load burdened by other aspects of getting their apps to the cloud. And Azure does a phenomenal job of simplifying providing same defaults out of the box. And as we've been talking about, it's also very open to partner integrations like the one we've announced yesterday and highlighted that, you know, that make it just easy for development teams to choose their tools and build their apps and deploy them on to Azure as quickly as possible. So it's a phenomenal platform for developers and we're very excited and proud to partner with Microsoft on this. Amanda, on your side, I see Docker's got millions of developers. You guys got millions of developers even more. How do you see the developers in Microsoft side engaging with Docker desktop and Docker hub? What does it all fit? I mentioned earlier how I see Docker context really improving the way that individuals and teams work with their environments and making sure that they're consistent. But I think this really comes together as we work with Docker desktop and Docker hub. When developers sign into Docker hub from Docker desktop, everything kind of lights up. And so they can see all of the images in their repositories and they can also see the cloud environments that they're running them in. And so, you know, once you sign into the hub, you can see all the contexts that map to the logical environments that they have access to, like dev and QA and maybe staging. And another use case that's really important is that we can access the same integration environment. So I could have microservices that I've been working on, but I can also see microservices that my teammates and their logs from the services that they've been working on, which I think is really great and certainly helps with team productivity. I love that. The other thing too is that this also really helps with hybrid cloud deployments, right? Where you might have some on-premises hosted containers and you might have some that's hosted in a public cloud. And so you can see all of those things for your Docker hub. Well, I got to say, I love the code to cloud tagline. I think that's very relevant and catchy. And I think I guess to me, what I'm seeing and I'd love to get your thoughts Amanda on this as you oversee a key part of Microsoft's business that's important for developers, just the vibe and people are amped up right now. I know people are tense to anxiety with the COVID-19 crisis. But I think people are generally agreeing that this is going to be a massive inflection point for just more headroom needed for developers to accelerate their value on the front lines. What's your personal take on this? And you've seen these ways before, but now in this time, what are you most excited about? What are you optimistic about? What's your view on the opportunities? Can you share your thoughts because people are going to get back to work or they're working now remotely, but even when we go back to hybrid world, they're going to be jamming on projects. Yeah, for sure. But I mean, people are jamming on projects right now. And I think that in a lot of ways, developers are first responders in that they are, developers are always trying to support somebody else, right? We're trying to support somebody else's workflow. And so we have examples of people who are creating new remote systems to be able to schedule meetings in hospitals for the doctors who are actually the first responders taking care of patients. But at the end of the day, it's the developer who's actually creating that solution, right? And so we're being called to duty right now. And so we need to make sure that we're actually there to support the needs of our users and that we're basically cranking on code as fast as we can. And to be able to do that, we have to make sure that every developer is empowered and they can move quickly, but also that they can collaborate really quickly. And so I think that, you know, Docker Hub, Docker kind of helps you ensure that you have that consistency, but you also have that connection to the infrastructure that's hosted by your organization. I think you nailed that amazing insight. I think that's, you know, the current situation and the community matters because there's a lot of frontline work being done to your point, but then we got to rebuild and the modernization is happening as well, coming out of this. So there's going to be that. And there's a lot of camaraderie going on and massive community involvement I'm seeing more of, you know, the empathy, but also now there's going to be the building, the creation, the new creation. So Scott, this is going to call for more simplicity and to abstract away the complexities. This is the core issue. Well, that's exactly right. And it is time to build, right? And we're going to build our way out of this. And it is the community that's responding. And so in some sense, Microsoft and Docker are there to support that that community energy and give them the tools to go and identify and have an impact as quickly as possible. May I reference in the keynote, completely bottoms up organic adoption of Docker desktop and Docker hub in racing to provide solutions against the COVID-19 virus, right? It's a war against this pandemic that is heavily dependent on applications and data. And there's over 200 projects, community project on Docker hub today, where you've got tools and containers and data analysis all in service to the COVID-19 battle that's being fought. And then as you said, John, as we get through this the other side, there's entire industries that are completely rethinking their approach that were largely offline before that now see the imperative and the importance of going online. And that tectonic shift nearly overnight of offline to online behavior and commerce and social and go on down the list, that requires new application development. And I'm very pleased about this partnership is that together we're giving developers the tools to really take advantage of that opportunity and go and build our way out of it. Well, Scott, congratulations on a great extended partnership with Microsoft and the Docker brand. You know, I'm a big fan of from day one. I know you guys have pivoted on a new trajectory which is phenomenal, very community oriented, very open source, very open. So congratulations on that. Amanda, thanks for spending the time to come on. I'll give you the final word. Take a minute to talk about what's new at Microsoft with the folks that know Microsoft, know they have a developer mindset from day one, cloud is exploding, code to cloud. What's the update? What's the new narrative? What should people know about Microsoft with developer community? Can you share some data for the folks that aren't in the community or might want to join or the folks in the community who want to get an update? Yeah, it's a great, great kind of question. I mean, right now I think we are all really focused on making sure that we can empower developers throughout the world. And that includes both those who are building solutions for their organizations today. But also I think we're going to end up with a ton of new developers over this next period who are really entering the workforce and learning to create digital solutions. Overall, there's a massive developer shortage across the world. There's so much opportunity for developers to kind of address a lot of the needs that we're seeing out of organizations again across the world. And so I think it's just a really exciting time to be a developer. And my only hope is that basically we're building tools that actually enable them to solve problems. Awesome insight and thank you so much for your time. Code to cloud developers are cranking away that the first responders going to take care of business and then continue to build out the modern applications. And when you have a crisis like this, people cut right through the noise and get right to the tools that matter. So thanks for for share and the Microsoft Docker partnership and the things that you guys are working on together. Thanks for your time. Thank you. Okay, this is the cubes coverage. We are DockerCon 2020 digital is the cube virtual. I'm John Furrier bringing all the action more coverage. Stay with us for more DockerCon virtual after this short break.


మోతాడునిర్ల్ల్ల్మాల్వరియా partially మోతాటకికిద్ంసిమికారాండి. మోతి కోతికికదికికికంసిద్పరంాటి. మరడ్జాకికిలాట. నంవాకకికికి. but we are excited and happy that after COVID-19, we are able to bounce back. Today, this year's race will be running on the golden platform. We are now gold labeled. And that means we are getting closer to our target. And by the time we get there, obviously, Upper Paris will be among one of the best in the world as far as road races is concerned.


Thank you very much. Ladies and gentlemen, my remarks here will be brief because the issue this bill deals with is so clear that it requires little elaboration. Please sit down. You can see how much of an hurry I am to finish the remarks and get to the task. I'm about to sign the Child Protection Act of 1984, a bill which will toughen the federal laws dealing with the production and distribution of pornographic materials involving children. It strengthens prosecuting authority against the producers and distributors, and it creates stiffer penalties for them. And I feel very strongly about these measures. There's no one lower or more vicious than a person who would profit from the abuse of children, whether by using them in pornographic material or by encouraging their sexual abuse by distributing this material. For years, some people have argued that this kind of pornography is a matter of artistic creativity and freedom of expression, and so on and so on, and they go on with that. Well, it's not.  If we do not move against it and protect our children, then we as a society just aren't worth much. In the last few months, we've seen news reports of cases involving child pornography and child abuse on a large scale. We've seen reports suggesting a link between child molesting and pornography, and academic studies have suggested a link between pornography and sexual violence toward women. Back in 1970, you may recall, a presidential commissioner studied this whole issue, and its famous conclusion was that pornography has no significant effect on behavior. I think the evidence that has come out since that time, plus the tendency of pornography to become increasingly more extreme shows that it is time to take a new look at this conclusion, and it's time to stop pretending that extreme pornography is a victimless crime. And so I want to announce that the attorney general is setting up a new national commission to study the effects of pornography on our society. The commission will study the dimensions of the problem and what we can do about it. We've taken some other initiatives in the anti-pornography effort. Last year, the Custom Service increased its seizures of obscene materials coming in across our borders by over 200%. 60% of the material was child pornography. And just last week, the Justice Department held a seminar for nearly 200 federal and state prosecutors and investigators to train them on how to better deal with pornography cases, including child pornography. So I want to make our interests and our intentions known. We consider pornography to be a public problem and we feel it is an issue that demands a second look. And I am particularly happy to sign this bill in the presence of Congressman Harold Sawyer, Republican of Michigan. This bill is largely his work. He plans to retire at the end of the current term. And Hal, I want you to know that your great efforts will be dearly missed in our nation's Congress and by this administration. And by the way, may I also note that under your leadership, this bill passed the House by a vote of 400 to one and that enjoyed similar strong support in the Senate. So there are issues on which bipartisan agreement can be overwhelming. And I'm heartened by this and I feel it bodes well for our dealings with this issue in the future. And now I will sign House Resolution 3635, the Child Protection Act of 1984 with great satisfaction and great appreciation for the good work of the Congress on this and a declaration that this administration shares your commitment and will continue to work closely with you on this issue in the future.