G'day guys, how are you going? If you're new here, I'm Tech and this is my channel Boot Lossophy. I'm on Wajik Country in Western Australia and I recognise the traditional owners of this land. Today I'm looking at the Ellen Edmonds Landon Boot in a stone-coloured new buck. This is the Ellen Edmonds Landon Boot. On their website they call this the Landon Suede Capto Boot in light brown. Firstly, it's not suede, it's definitely new buck. In fact, in the small print of the description they say that the Landon is offered in a full range of materials including an extra sturdy pair made in hefty new buck. They're adjective by the way, not mine. Secondly, would you call this light brown? I'm not sure I would. Maybe it's fawn, khaki or stone, but I wouldn't call it light brown, right? In fact, if you explore the website descriptions a bit, they're clearly written for the model and then remain unchanged as they copy the basic text onto different make-ups and just make some changes to the photos and a few names and words. I might be upsetting a few Ellen Edmonds fans, but I'm really not impressed by their website. So, it is a Capto Service Boot, six inches high with a brick-red day-night outsole. Aesthetically, it's reasonably sleek but has this strange thing going on at the back. There's the usual heel counter backstay, but the central strip is sewn on the outside of the backstay and there's this thing. I mean, I have no idea what it's there for. I guess it's a fashion choice and it is interesting, but I'm not into fashionable form and it seems a little unnecessary. I'll get into it when I get into the construction, but it has this nice natural colored welt which goes well with a stone-colored new buck. They call this a bench welt, but as we'll see, I think it's a standard split-reverse welt. The welt will make it more water-resistant, of course, but on top of that, these boots are themselves weatherproof. I think that means that the new buck is treated and there's a lining inside that's weatherproof. Ellen Edmonds do make them in a variety of leathers and even some wool and leather combinations including two-tone make-ups, but I think the outstanding thing about this aesthetic is the stone color in the matte new buck. I think it's quite eye-catching. From what I've seen and been able to research, they seem to have made an appearance in the Ellen Edmonds catalogs in 2019 or 2020, so they're not an old-time heritage boot, but built on the style of one. I'm not sure what the historical significance of the name Landon is, but Ellen Edmonds do have a range of World War II related names like the pattern after the general, the corn, even though that's a British battle, and the Normandy, which all seem to have appeared at roughly the same period. So maybe it's something to do with that. So based on that aesthetic, it's definitely a casual boot. Perhaps in a smooth brown or black leather, you could get away with more business casual attire, but in these uppers, they're smart casual and downwards in that casual ladder. Where I live, winter is reasonably mild, mild single digits at night, mid-teens during the day, just rain, no snow or ice. So I would wear this in winter as well as in summer, but I can see that if your conditions are a bit more harsh, this would be your summer boot, I think. And as a summer boot, the color and light new butt would be excellent to pair with similar tones like khaki chinos or very pale and even white trousers and polo shirts or smart button downs. The look in these could be quite preppy rather than a rugged jeans and t-shirt type casual. I'd also consider dark wash denim or darker earth and neutral colors like navy, olive or even black pants. I'd certainly be happy to top it with a blazer or a herrington jacket or a light textile bomber. It's soft and light enough to wear it in almost all social casual occasions. Things like friends parties, going to lunch at a cafe or the pub, lounging at the park or going to a game. Let's take a look at Ellen Edmonds before we look at the construction of these boots. Ellen Edmonds is a moderate to higher end shoe manufacturing and retail company. It was started in 1922 by Ebert Allen and Ralph Spiegel in Belgium, Wisconsin, and the company was originally called the Ellen Spiegel Shoe Company. I'm not sure when Ralph Spiegel left or was bought out, but in 1946 new partner William Edmonds joined Ebert Allen's sons who had inherited the company when their father passed away. So the current Ellen Edmonds shoe corporation was born then. According to their website, when Ebert Allen started the company, he specialized in making footwear with cork insoles instead of metal nails and shanks used at the time. I'm not sure what they mean by cork insoles instead of nails and shanks. I mean, I would have thought that there were different parts of the boot anatomy. Doing a little further research, I think what they mean is that most shoes of that period seems to have been made with stiff leather insoles and midsole, including that midsole filler, which is now mainly cork. So with or without a shank, there were probably a lot more uncomfortable than today's shoes with less thickness leather and more cork or other filling inside. Honestly, another example I think of poorly crafted website text. Anyway, presumably making more comfortable shoes than his competitors, Allen grew the company steadily and the company supplied footwear to the US Army and Navy in World War II. It's said that this gained them a huge following and loyalty from returning troops. As they grew, they kept on introducing Oxford dress shoes like Park Avenues and Strands that had become American classics. In 2006, investment firm Goldner Horn bought 90% of the company and then in 2013, they were bought out by private equity hedge fund Brentwood. And finally in 2013, they were acquired for 255 million by Caleres Inc, a public company listed on the New York Stock Exchange. Caleres also owns other footwear brands like Dr. Shawl, Famous, Vince, Lifestride and Blowfish Malibu, selling through websites, department stores, and over a thousand retail stores and malls and shopping centers. Caleres has a market cap today of over $1 billion US with a group turnover of nearly $2.8 billion US in financial 2021. The estimated turnover for Allen Edmonds itself in financial 2021 was about $119 million US and it was estimated to employ about 500 people. It's said that Allen Edmonds resisted the trend to move all production overseas to save costs, mainly due to concerns about quality control, and they still use the tagline Handcrafted in Port Washington, Wisconsin. However, you should note that their hand-sewn collection is hand-sewn in company-owned factories in the Dominican Republic and then shipped to Port Washington to complete their production there. And in this way, they can legally say their products are made in America, which to a large extent I suppose they are. Today, Allen Edmonds also makes shoes in Italy as well as the Dominican Republic and in America. A lot of commentary now is that since they ramped up production numbers in the late 2010s, there have been more and more QC issues. I'm new to Allen Edmonds and I have three models, two pairs of the Higgins mill, one in brown chrome XL, the iconic pair, and the other in loading suede. And of course, I have these. I can't compare QC to earlier models, but all three have, I think, seem to be good. Let's turn to the way these Landon boots are constructed. Starting at the uppers, they are new buck. While it might look and almost feel like suede, new buck is a top grain leather that's been sanded or buffed on the grain side to give it a slight nap or short fibers that produce a velvety feel to the surface. Let's break that down. When a hide comes into the tannery, it's split through a horizontal rolling blade into a top half and a bottom half. The bottom half is taken to be made into suede. The top half or top grain half can be turned into smooth top grain leather. Or in the case of new buck, that top grain side, or where the hair used to be, is sanded lightly to create new buck. New buck being made of tighter fiber structures is tougher than suede and with fibers looser than smooth leather, also more durable than smooth full grain, which scratches easily. This new buck is very soft and just nappy enough so that you can stroke it and cause the light to change the color and shade. The cap toe is very lightly structured. You can easily depress it and it's not a real cap toe. It isn't two pieces leather, one on top of each other, but a cap toe sewn onto a cut off vent piece. The heel counter is also extremely softly stiffened. Again, you can easily depress it. The counter backstay is a single piece with this, whatever you call it, backstrap thingy running outside the heel backstay and up the shaft. And then it's crossed by this horizontal strap thingy. The strap thingy doesn't fulfill any function that I can see, it's just there for a fashion distinction I think. The stitching is neat and clean, but more like a dress shoe than of a rugged boot and that's what I mean by pretty good QC. It's mainly double stitching only and there's some loose threads here and there and it doesn't feel particularly sturdy but it's well sewn. This is not intended as a work or idea say outdoorsy hiking boot by any means. There are five brass eyelets and three brass speed hooks. They're backed with washers and they feel pretty sturdy.  The boot is fully lined with a soft and I'm guessing goat leather. Newbuck is usually thinner weight than full grain uncorrected leather but because of the lining I can't measure the thickness of the newbuck itself. The thickness including the lining is three and a half to four mils thick so that's pretty good overall. The newbuck and lining together gives it a comfortable and quite luxurious feel to the uppers. This is quite a strange last and has the effect of creating a wide gap between the lace facings on my feet. When I lace them up tight there's almost a two inch gap at the widest part. That's not because they don't fit, these boots fit me perfectly which I'll get to later but they're lasted very wide. Apparently Ellen Edmonds lasts are developed in-house as supposed to be bought from last designers. Some boot makers will buy a last from designers like Jones and Vinning but Ellen Edmonds make their own. The Landon is built on their 2622 last that's described as broad through the four part with a round toe and a low profile and gives a relaxed fit. It definitely has less volume than the Higgins Mill. The low profile is what tends to widen that lacing up I think not that the boot is too small and the design of the quarters is cut so that they are wide apart. Inside the boot is a leather insole and pushing into that I reckon there's a foam or poron type insole in there as well. It isn't listed on the website under materials but they do talk about cork and other innovative materials in the insole so I guess that's it. However under that they say there is a cork filling that fills in the cavity caused by the Goodyear welt going around the edge of the boot. So yes this boot is a Goodyear welted boot. That's the form of construction that sews the uppers to the welt and then separately sews the outsoles to the welt. In this way making the welt a barrier between inside and outside and increasing water resistance. It's also a form of construction that makes it easy to re-sole or re-craft the boot by undoing the stitching and replacing the worn out sole. This is despite their website saying the landon is bench welter. I don't know if there is a technical definition for bench welting but as far as I've been able to research it's another term for a flat welt where the welt is a flat piece of leather. If that's right then I don't know why their website describes this as a bench or flat welt because this is clearly a split reverse welt. A split reverse welt is a welt that's partly split in the inside edge. The lower part of the split is sewn to the uppers like normal. The upper part of the split is flanged upwards and then pushed against the side of the boot to create a further barrier against moisture and water getting in. These boots have a two plus mil leather welt and it's sewn to a two mil thick leather midsole and then to the rubber day night outsole. Day night is an English company that started producing these day night studded outsoles in 1910. The company used to run its mil day and night and hence coined this name day night. This is a truly ubiquitous outsole seen on the styles of almost every boot maker and if a boot maker doesn't use day night they almost certainly have made a proprietary version of day night because of the successful combination of grip afforded by these sunken studs and the thin dressiness of the sole from the profile. They go on rugged Pacific Northwest boots as well as on dressy English oxfords replacing traditional thin leather soles. In this case Ellen Edmonds uses the brick red or ochre version. A lot of people don't like it but I think it's an attractive point of difference unlike that funny strappy thing at the back of the boot. Day night is grippy enough in most urban situations. Remember I've not worn it on ice or snow. With the cork filler on top and the foam backing in the insole you don't get any feeling of the studs coming through inside so I find them good if not perfect for my use case scenarios in the office or in social occasions especially as they look flat and dressy from the side. Now how do you take care of this new buck especially with this light colour? To start with it's slightly absorbent which means that if you splash it with dirt or even with moisture it will absorb some of that into it so before first wear I'd treat it with a waterproofer spray like Tarago's Nano spray. It does wear off so I respray it every three or four months or more if this is your everyday boot that you wear in weather. If it does get marked you can treat it like suede. Don't wash it with water don't saddle soap new buck. For most everyday cleaning it's enough to just remove gritty dirt with a suede brush. You can get a suede brush with firm bristles or some have a copper core of bristles surrounded by an edging of rubber bristles to help smooth out the net just simply with the brushing action. You can also brush away any shiny spots I haven't got any developed here but if they do develop with constant rubbing like say from your trouser leg just rub them off. If there is a stain or dirty spot you can rub at it with a suede eraser. I find that Timberlands dry cleaning kits with a suede brush and eraser are useful for this care. I'll leave a link in the description box below. If you have liquid stains like red wine or ink you may have to resort to more scarier methods. I mean obviously if you spot the stain quickly immediately wipe it off and damp at the spot with a damp cloth being careful not to spread the stain. However if you've not been careful and it has dried before you recognize it you may have to resort to a very fine sandpaper I mean really fine. That sounds incredibly frightening but as long as you're gentle and don't treat it like a block of wood it should be fine. The newbuck was created by fine sanding of the surface of the leather so you should be able to replicate that and remove the tiniest of tiniest of surface layer to remove the stain. As for conditioning I don't think you need to stress about that as much it's a it's a pretty dry leather but if it really does dry out as it gets older you can use a roll-on type of suede and newbuck conditioner like the Echo product or use Tarago suede and newbuck conditioning spray. Taking a look at how these size I'll start with my true size as measured on a brannock device which is an eight and a half in D or average width. For UK and Australian viewers our sizes are one number down from US. For most of my American heritage boots I size down by a half to an eight D. I did the same here and it's a great fit. As I said earlier the 2622 last is a wide last. The heels are pretty snug just the way I like them because it gives me that locked in feeling and then the last widens into the ball of the feet so that my widest part of my feet don't feel squeezed. The toes are rounded and they round gently so no quick taper in. Sometimes especially in European lasts they taper into a very pointed toe very quickly sometimes pushing your outside toes in a bit too much. The length at eight D is great for me plenty of room at the tip of my toes without being oversized. The overall comfort is good. The last is suited to my feet. The supple newbuck and soft uppers wrap my feet without constraining them and the slight foam feeling under the leather insole gives me a light touch under my feet. The only thing is that the arch support is not great. If you've seen my other videos you know that when I'm talking about the construction I usually mention the presence or absence of a shank. That's the thin strip of hard material steel plastic fiberglass that gets inserted into the midsole between the heel and the ball of the foot. It gives the the boot arch support by stopping your weight collapsing this gap here and also gives a little stability longitudinally so as your feet wobble over uneven ground it's stabilized. I didn't mention it because I have no idea if they have one. I can't find any information about it and in many forums and discussion groups it seems to be generally accepted that Ellen Edmonds tend not to have a shank. These do not feel like there is a shank. It is pretty light so it's not a steel shank. It flexes quite a bit when you press down or when you stand. You can flex the boot through the middle part quite easily. But mostly when I stand in it I do feel my archers sink down a bit. I haven't worn these long enough in a day when my feet could feel tired but I feel that they would. So potentially comfy because of the materials but probably not great for a long day on your feet. I bought this pair from eBay for 179 US dollars. They sell on the Ellen Edmonds website for about 480 US so I felt it was a good buy especially as they were hardly used just didn't fit the guy. The heel was unmarked, the sole was untouched. There was a little creasing at the vamp but nothing too alarming and there were absolutely no impressions on the insole. I think at best these were worn no more than a week or so and most of it I think indoors. At that price I think they're a great buy. At the listed price in the mid 400s they stand 100 dollars above Grant Stone and Parkhurst and maybe 150 above some sturdy red ring models. There are a few dollars more than Wolverine 1000 miles. They're at a comparable price with Oak Street bootmakers trench boots as well as some Truman boots. Looking at those comparisons they're about the same quality as Wolverines. Parkhurst boots are I think sturdier and more rugged if you're that way inclined. Grant Stone quality is well above these in my opinion. The Oak Street items seem to be more carefully handmade and Truman boots are just tanks so I'm not sure I can say that at mid 400s or at the 480 dollars on the website that they are worth that price. Having said that they seem to be on sale quite often and on Amazon they're usually listed around US 300 or even less sometimes you just have to catch it at the right time. At 300 dollars US I think that's more like it. I'd say they'd be at the right value then. I'll leave a link to Amazon below if you're interested in chasing them there. You do have to keep looking out for them to get the right price and there you have it. My review of the Ellen Edmonds Landon boots in light brown or stone. New buck not suede. I hope you like my review. If you did please click on the like button so that I can grow my channel to bring you more boot reviews and if you want to catch my boot reviews as I upload them don't forget to click on subscribe as well. That'll get YouTube to notify you when something new from me comes up. Take care guys and I'll see you soon.


Live from San Francisco, it's theCUBE. Covering Red Hat Summit 2018, brought to you by Red Hat. Okay, welcome back everyone. We are here live, the CUBE in San Francisco, Moscone West for the Red Hat Summit 2018. Exclusive coverage, I'm John Furrier, the co-host of theCUBE. I'm here with my co-host, John Troyer, who's the co-founder of Tech Reckoning, an advisory and community development firm. Our next guest is Jonathan Donaldson, technical director, office of the CTO, Google Cloud, former CUBE alumni, formerly with Intel, been on before, now at Google Cloud for almost two years. Welcome back, good to see you. Good to see you too, it's great to be back. So, had a great time last week with the Google Cloud folks at KubeCon in Denmark, Kubernetes, rock on the world. Really, when I hear the word de facto standard and abstraction layers, I start to get my bells going, hmm, let me look at that. Some interesting stuff, you guys have been part of that from the beginning with the CNCF, Google, Intel, among others, really created a movement, congratulations. Thank you, yeah, I mean, it really comes down to the fact that we've been running containers for almost a dozen years, right? Four billion a week, we launch and collapse, and we know that at some point as Docker and containers really started to take over the new way of developing things, that everyone's going to run into that scalability wall that we had run into years and years and years ago, and so Craig and the team at Google, again, I wasn't at Google at the time, but they had a really, like, hey, let's take what we know from internally here, and let's take those patterns and let's put them out there for the world to use, and that became Kubernetes, and so I think that's really kind of the massive growth there, is that people are like, wow, you've solved a problem, but not from a science project, it's actually from something that's been running for a decade. And that's called Bore, that's the tools that Google used to, that their SRE site reliable engineers used to massively provision management, and they're all software engineers, it's not like they're operators, they're all like Google engineers, but I want to take a minute if you can to explain because you're new to your Google Cloud, you're in the industry, you've been around, you've helped form the CNCF, which is the Cloud Native Foundation, you know Cloud, you know tech, Google's changed a lot, and Google Cloud specifically has a narrative of, well, you know, they're one big cloud, and they have an application called Google Stuff, and the enterprises are different, you've been there now for almost a year or more. A little over a year, yeah. What's Google Cloud like right now? Break the myths down around Google Cloud, what's the current state? I know personally, a lot of cloud DNA is coming in from the industry they've been hiring, making some great progress, take a minute to explain the Google Cloud. Yeah, so it's really interesting. So again, it comes to back from where you started from, and so Google itself started from a scale, consumer, you know, SaaS type of business, and so that they understood really well, and we still understand obviously, you know, uptime and scalability really, really well, and I would say, you know, if you backtrack several years ago, as the enterprise started to really look at public clouds and Google Cloud itself started to spin up, that was probably not, they probably didn't understand exactly all of the things that an enterprise would need, as really at that point in time, really no one cloud understood any of the enterprise specifically, and so what they did is they started hiring in people like myself and others that are in the group that I'm in, they're, you know, former CIOs of large enterprise companies or former VPs of engineering, and really kind of our job in the Office of CTO for Google Cloud is to help with the product teams, to help them build the products that enterprises need to be able to use the public cloud, and then also work with, you know, some of those top enterprise customers to help them adopt those technologies, and so I think now that if you look at Google Cloud, right, they understand enterprise really, really well, certainly from the product and the technology perspective, and I think it's just going to get better. I interviewed Jennifer Lin at a one-on-one with her, I didn't publish it, it was more of a briefing, she's runs product management on the security side. It's fantastic. So, you know, we, she's checking the boxes, so the table stakes are kind of like set for Google, I know you got to do some basic things to catch up to get in the cloud, but also you have partnerships, Google Next is coming up, theCUBE will be there, Red Hat's a partner, talk about that relationship with Red Hat and partners, so you're very partner-centric with Google Cloud, and that's important in the enterprise. Yeah, there tends to be kind of two main areas that we focus on from what we consider, the right way to do cloud. One of them is open source, right? So having the, which again, aligns perfectly with Red Hat is putting the technologies that we want customers to use and that we think customers should use in open source, right? Kubernetes is an example of those, Istio and others that we've put out there, examples of those, you know, a lot of the open source projects that we all take for granted today were started from white papers that we had put out at one point in time, kind of explaining how we do those things. Red Hat, and from a partner perspective, I think that that follows along, right? We think that the way that customers are going to consume these technologies, certainly enterprise customers, are through those partners that they know and trust, and so having a good flourishing ecosystem of partners that surround Google Cloud is absolutely key to what we do. They love multi-cloud too, I mean, can't you? They love multi-cloud, and we do too. I mean, the idea is that we want customers to come to Google Cloud and stay there because they want to stay there, because they like us for who we are and for what we offer them, not because they're locked into a specific service or technology, and, you know, things like Kubernetes, things like containers, being open source, right, allows them to, you know, take their tool chains all the way from their laptop to their own cloud and inside their own data center to any, you know, cloud provider they want, and we think, you know, hopefully they'll naturally gravitate towards us over time. One of the things I like about the cloud is that there's a flywheel, if you will, of expertise, like I look at Amazon, for instance, they're getting a lot of metadata of the kinds of workloads that are on their cloud, so they can learn from that and turn that into an advantage for them or not, or for their customers and how they can do that. That's their business decision. Google has a lot of flywheel action going on. A lot of Android devices connected in the Google system. You have a lot of services that you can bring to bear in the cloud. How are you guys looking at, say, from a security standpoint alone? That would be a very valuable service to have. I can tap into all the security gutting goodness of Google around what spearfishing is out there or things of that nature. So are you guys thinking like that in terms of services for customers? How was that laid out? So we're very consistent on what we consider is privacy is number one for our customers, right? Whether they're consumer customers or whether they're enterprise customers, right? The where we would use data, like you mentioned a lot of things, but where we would use some data across customer bases are typically for security things, right? So where we would see some sort of security impact or an attack or something like that. This started to impact many customers and we would then kind of aggregate that information. It's not really customer information, it's just like, like you said, metadata or themes or trends, right? And yeah, we're not monetizing it, but we're actually using it to protect customers. But when a customer actually uses Google Cloud, that instance, that is their hermetically sealed environment. In fact, I think we just came out recently with even the transparency aspects of it where it's almost like the two key type of access for if our engineers have to help the customer with a troubleshooting ticket, that ticket actually has to be open. That kind of unlocks one door, the customer has to say yes, that unlocks the other door, and then they can go in there and help the customer do things to solve whatever the problem is. And each one of those is transparently and permanently logged, and then the customer can at any point in time go in and see those things. So we are taking customer privacy from an enterprise perspective. And you guys are also in a whole building from Google proper. Like it's a completely different campus. So that's important to note. It is. And a lot of this just chains on from Google proper itself.  Well, you got to amplify that, I understand. But also I see a good side of that, which is there's a lot of resources you're bringing to bear, or learnings. Absolutely. The SRE concept, for instance, is to me really powerful, because Google had to build that out themselves, right? This is now a paradigm we're seeing a cloud scale here with the cloud native market bringing in all new capabilities at scale. Horizontally scalable, fully asynchronous, microservices architecture. This future is a complete game changer on functionality at the different scale points. So there's no longer the operators running provisioning storage here. And this is what we've been doing for years and years and years. That's how all of Google itself has all search and ads and Gmail and everything runs in containers, all orchestrated by Borg, which is our version of Kubernetes and stuff. We're really just bringing those learnings into Google Cloud and to those customers. Jonathan, machine learning and AI has been a big topic this week on OpenShift. Obviously that's a big strength of Google Cloud as well. Can you drill down in that story and talk about what Google Cloud is bringing and machine learning on OpenShift in general? Give us a little picture of what's running. So I think they showed some of the service broker stuff and I think they showed some of the Kubeflow stuff, which is kind of taking some machine learning and Kubernetes underneath OpenShift. Like I think those are like very, very interesting for people that want to start getting into using auto ML, which is kind of roll your own machine learning or even the voice or vision APIs to enhance their products. And I think that those are going to be keys. Easing the adoption of those, making them really, really easy to consume is what's going to drive the significant ramp on using those types of technologies. One of the key touch points here has been the fact that this stuff is real world and production ready. The fact that the enterprise architects are now rolling out apps within days or weeks. One of those things that's now real is ML and even in the opening keynote, they talked about using a little bit of it to optimize the scheduling and what sessions were in which rooms. As you talk to enterprises, it does seem like this stuff is being baked into real enterprise apps today. Can you talk a little bit about that? So it certainly can't give any specific examples because I think what you're seeing is that a lot of enterprises or a lot of companies are kind of like, they're looking at that like, oh, this is our new secret sauce. It always used to be like they had some interesting feature before that a competitor would have to keep up with or catch up with, but I think they're looking at machine learning as a way to enhance that customer experience, right? So that it's a much more intimate experience. It feels much more tailored to whomever is using their product. And I think that you're seeing a lot of those types of things that people are starting to bake into their products. We've, again, this is one of these things where we've been using machine learning for almost 10 years inside Google things, like for Gmail, even in early days like spam filtering. I mean, something just kind of mundane like that or we even used it, turned it on in our data centers to drop our, because it does a really good job of lowering the PUE, which is the power efficiency in data centers. And those are very mundane things, but we have a lot of experience with that and we're exposing that through these products and we're starting to see people, customers gravitate to grab onto those to go. Instead of having to hard code something that is a one to many kind of thing, right? I may get it right or I may have to tweak it over time, but I'm still kind of generalizing what the use cases are that my customers want to see. Once they turn on machine learning inside their applications, it feels much more tailored to the customer's use cases. Machine learning as a service seems to be a big hot button that's coming out. How are you guys looking at the technical direction from the cloud? We're going there first, because you have three classes of enterprises. You have the early adopters, the power, front cutting edge, then you have the fast followers and you have kind of everybody else. The everybody else and fast followers, they know about Kubernetes, some might even, what is Kubernetes? So you have kind of the level of progress where people are. How are you guys looking at addressing those three areas? Because you could blow them away with, TensorFlow is a server. Whoa, I'm just trying to get my storage lungs moving to a cloud operation. So there's different parts of the journey. Is there a technical direction that addresses these? What are you guys doing? So typically we'll work with those customers to help them kind of chart the path for all those things and making it easy for them to use and consume. Machine learning is still, unless you are a stats major or you're a math major, a lot of the algorithms and understanding kind of linear algebra and things like that are still very complex topics. But then again, so is networking and BGP and things like OSPF back a few years ago. So technology always evolves and the thing that you can do is you can just help pull people along to continue on there by making it easy for them to use and to provide a lot of education. So we work with customers on all ends of the spectrum. If it's just like, how do I modernize my applications or how do I even just put them into the cloud? We have teams that can help do that or can educate on that. If there are customers who are like, I really want to go do something special with maybe refactoring my applications. I really want to get the cloud native experience. We help with that. And those customers that say, I really want to find out this machine learning thing. How can I actually make that an impactful portion of my company's portfolio? We can certainly help with that. And it's just a, there's no one, and typically you'll find in any large enterprise because there'll be some people on each one of those camps. Yeah, and they'll also want to, they'll put their toe in the water here and there. The question I have for you guys is you've got a lot of goodness going on. You're not trying to match Amazon speed for speed, feature for feature. You guys are picking your shots that is core to Google, that's clear. Is there a use case or set of building blocks that are highly adopted with you guys now? And as Google gets out there and gets some penetration in the enterprise, what's the use, what are the key things that you see with successes for you guys out of the gate? I mean, is there a basic building that Amazon's got EC2 and S3? What are you guys seeing as the kind of the core building blocks of Google Cloud from a product standpoint that's getting the most traction today? So I think we're seeing the same types of building blocks that the other cloud providers are. I think some of the differences is we look at security differently because of where, again, where we grew up, we do things like live migration of virtual machines if you're using virtual machines because we've had to do that internally. So I think there are some differences on just even some of the basic block and tackling type of things. But I do think that if you look at, just moving to the cloud in and of itself is not enough. I mean, that's just kind of, that's a stepping stone. We truly believe that artificial intelligence, the machine learning, cloud native style of applications, containers, things like service meshes, those things that kind of reduce the operational burdens and improve the rate of new feature introduction as well as the machine learning things. I think that that's what people tend to come to Google for. And we think that that's kind of the, a lot of what people are going to stay with us for. I overheard a quote I want to get your reaction to. I wrote it down. It says, I need to get away from VPNs and firewalls. I need user and application layer security with un-fishable access, otherwise I'm never safe. So this is kind of a user perspective or customer perspective. Obviously with cloud there's no perimeter. So you've got phishing problems, right? You know, speed phishing is one big problem. Security, you mentioned that. And then another quote I had was, Kubernetes is about running frameworks and it's about changing the way applications are going to be built over time. That's where I think SRE and Istio is very interesting in Kubeflow. This is a modern architecture for- We're doing a Kubevert out there where you can run a VM inside a container, which is actually what we do internally too. So that's, there's a lot of different ways to slice and dice. How relevant is that, those concepts? Because are you hearing that as well on the customers? Because that's pain point. But also the new modern software development is a future way to do things. So there's pain point, I need some aspirin for that, and then I need some growth with the new applications being built and hiring talent. Is that consistent with how you guys see it? So which one should I tackle? So you talked about VPNs first, that's my favorite one. So one of the most, can I give you the backstory? So one of the most interesting things when I came to Google, having come from other large enterprise vendors, before this was there's no VPNs. We don't even have it on our laptop. They have this thing called BeyondCorp, which is essentially now productized as the identity where proxy, which is it actually takes, we trust no one or nothing with anything. It's not the walled garden style of approach of firewall type VPN security. What we do is based upon the resource you're going to request access for, and are you on a trusted machine? So are you one that corporate has given you? And do you have two factor authentication that corporate, not only it's what you have and what you know, right? And so they take all of those things into awareness. Like is this the laptop that's registered to you, right? Is this, do you have your two factor authentication? Have you authenticated to it? That's a trusted platform. Boom, then I can gain access to the resources, but they will also look for things like, if all of a sudden, you were sitting here and I'm in San Francisco, but something from some country in Asia pops up with my credentials on it, they're going to slam the door shut going, there's no way that you can be in two places at one time. And so that's what the identity where proxy or beyond corp does, kind of in a nutshell. And so we use that everywhere, internally, externally. And so that's the way that we, one of the ways that we do security differently is without VPNs. And that's actually in front of, you know, a lot of the GCP technologies today that you can actually leverage that. So I would say, we take- Just rethinking security. Rethinking security, again, based upon a long history and not only that, but what we use internally from our corporate perspective. And now to get to the second question. Istio, Kubeflow is more of the way software gets run. I mean, with one quote from one of the ex-Googler who left Google and went out to another company, she goes, she was blown away, but this is the way people ship software. She was like, she was a fish out of water. She's like, oh my God, where's board? You know, like we do waterfall. So there's a new approach that opens source communities and people expect. Right. That's the notion of Kubeflow and orchestration. So that's kind of a modern, that requires training and commitment. Right. That's the upside, right? Fixed to aspirin, so identity proxy cool, future of software development architecture. Yeah, I think one of the strong things that you're going to see in software development is, I think the days of people running differently in development and then in sandbox and then in testing QA and then in prod are over, right? They want to basically have that same experience no matter where they are. They want to not have to do that, crossing your fingers. Remember, it used to get, now it gets red-edited or it got slash dotted way back in the past and things would collapse. Those days of people being able to put up with those types of issues are over. And so I think that you're going to continue to see the development and the style of microservices containers orchestrated by something that can do auto scaling and healing like Kubernetes, you're going to see them then start to use kind of that base layer to add new capabilities on top, which is where we see Qubeflow, which is like, hey, how can I go put, you know, scalable machine learning on top of containers and on top of Kubernetes? And you even see, like I said, you see people saying, well, I don't really want to run two different data planes and do kind of the inception model. Like, if I can lay down a base layer of Kubernetes and containers, then I can run bare metal workloads against the bare metal. If I need to run, launch a virtual machine, I'll just launch that inside the container. And that's what Qvert's doing. So we're seeing a lot of this very interesting stuff. Creativity. Creativity. Great. Talk about your role in the office of the CTO. I know we've got a couple of minutes left. I want to get it out there. What is the role of the CTO? Obviously, Brian, Steve, formerly a Red Hat executive. Yeah, Brian's our CTO. Used to run a big chunk of the engineering at for Google Cloud, absolutely. And so what is the office charter? You mentioned some CIOs, former CIOs are in there. Is it the think tank? Is it the command and control ivory tower? I mean, what's the role of the office? So I think a couple of years ago, Diane Green and Brian Stevens and other executives decided, if we want to really understand what the enterprise needs from us from a cloud perspective, we really need to have some people that have walked in those shoes. And they can't just be Diane or can't just be Brian, who also had a big breadth of experience there. But two people can't do that for every customer or for every product. And so they instituted this. The office CTO tapped Will Granis, again, had been in Boeing before, been in the military, and so tapped him to kind of build this thing. And they went and they looked for people that had experience. Former VP's of engineering, former CIOs. We have people from GE, oil and gas. We have people from Boeing. We have people from Pixar. Like you name it, across each of the different verticals, health care. We have those in the office CTO, and probably, I think, 25 to 30 of us now. I can't remember exact numbers. And really, what our day-to-day life is like is working significantly with the product managers and the engineering teams to help facilitate more and more enterprise-focused engineering into the products. And then working with enterprise customers, kind of the big enterprise customers that we want to see successful and helping drive their success as they consume Google Cloud. So being kind of that conduit directly into the engineering. So in market with customer, big-nut customers, getting requirements, helping facilitate product management function as well. And it's from an engineering perspective. So we actually sit in the engineering organization. Make sure you're making the good bets. Yes, exactly. Great, well, thanks for coming on theCUBE. Thanks for sharing the insight. Great to have you on. Great insight, again, Google. Always great technology. Great enterprise mojo going on right now. Of course, theCUBE will be at Google Next this July. So we'll have live coverage from Google Next here in San Francisco at that time. Thanks for coming on, Jonathan. Really appreciate it. Looking forward to more coverage. Stay with us for more day three as we start to wrap up our live coverage of Red Hat Summit 2018. We'll be back after this short break.


Hey guys, it's Julia and welcome back to my channel and for today's video, I'm going to be talking to you guys about my December 2017 favorites Have some things to show you guys and I'm really excited about it because I'm working with a company for this video Joy sent me one of their wood watches and I'm so excited to tell you guys about this because It's Beautiful like one when I got this in the mail I was so happy because I look forward to mail so much not the point of this video, but Um Basically, they said you this like wooden case and has their logo on the top and I'll do close-ups, but like oh My god, the watch is so pretty like you get it perfect like you can get it sized and it's just so pretty They have a little drawer and it comes with like a bunch of stuff for the watch Like it's really nice quality and I was just so impressed by like how high quality this is and like when I got them Like wow when the company approached me I was super excited about this and I just love the look of the watch so much and You just tell how high quality it is and like the box is a magnet like look how cute So basically in the description box, I'm gonna have a link for you guys It's to enter a giveaway contest basically. I believe the prize is $180 gift certificate if you went so I'll link that down below all the giveaway details will be in the description But there's some like codes a gift thingy you can enter giveaway It's a lot of fun. I'll also link the site down below So just thank you so much to yoid for working with me And I am just so excited about this watch and if you like comment down below your favorite one on the site because I It's so much fun like looking through the site. So Yes, that's my first favorite. It's honestly a favorite. I wouldn't lie to you guys I hope you know that here. I just have a few like beauty product thingies So I have this Urban Decay lipstick and it's in the color back talk. Oh, I'm wearing it on my lips today I love it so much. It's so pretty. It's just like a mauvee pink just my shade just my kind of color and Yeah, I'm getting a lot of wearer this one and it's like really buttery oddly enough Like it's not drying at all and it's mad so you think it'd be like kind of like mmm, but it's good So next up here. I have the Jeffree Star cosmetics skin for us and nefri So this is like a purpley pinky Skinfrost it's really pretty it's from their family collection and I love it so much I'm wearing it today I think it looks really pretty with like a nice blush because it like kind of blends in with the blush And it's like oh fancy. It's cute. I love it a lot and oh like I love his whole brand But like this skin frost is so nice And I think it would look great on a lot of skin tones But like if you're going like make sure you wear blush with this will kind of like looks good with your blush So you're not just having like pink on your face, but yeah, it's cute here I have this hat which this is just like a gray beanie with a rose on it I wear it so much. I think you guys probably seen it in some of my videos But I wear this so often and it's just a beanie like it's just cute. I Think I got it from blue notes. I Don't know what countries have blue notes I think the states in Canada has it like that's it But I'm not sure but this is just so pretty so soft. I've been wearing it all winter and last but not least I wasn't actually asked to talk about this But I it's sincerely one of my favorites. Oh, I think what I've been looking for is in here Yeah, so another favorite I was gonna talk about is but I couldn't find it is the Jeffree star cosmetics holiday collection Lipstick and the color Christmas cookies. So I wore this in a few of my videos and I just love it It's like a really nice nude color mmm love this color and It was literally in my book pouch like okay um But this is a book pouch I got this a few months ago from Kayla But this month especially I've been really really using it because like I've just been bringing books with me I like I've been going out a lot So I've been bringing book like my pouch with me everywhere and I just love How my books don't get ruined and I love Well, I love Kayla who made it. She's one of my best friends, but I'll link her shop down below I think she has like a Facebook page for it But I'll link it down below because it's actually like really nice quality And they're a really good price because some book pouches can get really pricey especially with shipping and stuff But Kayla's are quite inexpensive and they're really nicely like padded on the inside I love it and she gave me a little one which I haven't used too much just because I don't read many mass markets But I have used that one this month, too. So there you guys have it. Thank you so much for watching this video Um, I hope you guys know by now if you're new here that I would not talk about something that I didn't Sincerely love so in regards to the company Yoid that I was working with I Sincerely think it's a good product and it's high quality and I think a lot of people would love it So that's why I'm talking about it.  See you all very soon with a new video. Bye


that love is not a gift. Love is a baton, no relay baton. Love isn't a gift that I keep and it stays with me. Love is a baton to be passed on.


Welcome to OSB Local, we will be talking about service brokers on your machine. My name is Christian Brinker, I'm a software developer at Ivolá and I talk about a problem I faced a lot of times during developing of software. What is the problem we want to solve with this? I'm a dev and unfortunately sometimes I'm also consulting somewhere and in between I want to develop something in the train maybe on the drive to the customer and to test something and unfortunately I like Cloud Foundry and the Cloud Foundry experience but at some times you don't have internet access, you cannot access your Cloud Foundry maybe, you may be remote or in a hotel room with a bad Wi-Fi and you want to test something and then you don't have a Cloud Foundry. So several people came up with this idea, hey, why don't you have a local Cloud Foundry on your local computer which is CF Local, CF Dev, different types of ideas. By the one you have Docker containers, by the other hand you have a fully fledged VM in the hyperkit running on your local machine and you have all the things stuffed in there. So this is cool, now you have a local Cloud Foundry, okay, CF Dev is not that un-consuming of hardware resources in your laptop so with this old guy here it's a little bit of frustrating sometimes but you have it. You can test things, you can experiment and so on. So you have this idea of a Cloud is more or less equal to this local Cloud thing. But let's face another problem, I'm deaf and I have my local Cloud and now my friend here comes and says, yeah, I have a cool idea. Let's make Mongo great again and use it in our project. Now get sad because why? My local Cloud PCF Dev, CF Dev made only have my SQL in it but no Mongo. So I have the problem to get a local MongoDB stuck in there somehow. So I'm really, okay, where can I get a MongoDB? Maybe I can take a Docker container, spawn it, wire it somehow in the network of the CF Dev and okay or I have to look for some service broker and look how could I ship this thingy and I'm really getting a little bit frustrated. So the cool idea is I want to have local Cloud with my MongoDB service in the marketplace. That would be awesome and that's what makes me happy so I can develop with it. But not only with MongoDB with every service broker around, I want to start with. So what is the idea? I have my local CF Dev with Cloud Foundry, with Bosch Director, with my SQL. I didn't use CF local because most service brokers need a Bosch Director to deploy something which we don't have in CF local. Then I want to have a service broker, some more thing and I want to have a CLI plug in for my Cloud Foundry CLI to start that thing up, to make the service broker available in my CF Dev in an easy way. I don't have to think much about it. I only start working and then I get my marketplace things there. So this is then OSB local as a concept. So what we have to achieve? First of all, you have to have some kind of rendering mechanism for the service brokers. Why that? If you look at service brokers, they are a little bit different. They all have to be a little bit started differently, how they work, how they will be shipped, how they will be deployed. There are tiles, there are no tiles. They are deployed as VMs, as a cloud native application inside Cloud Foundry. It's all a little bit different. If you look at different kinds of service brokers out there. So you have to have a standardized rendering system for the service brokers. Then you have to load them via CLI into CF Dev so you can use them in the marketplace, create service instances, create service keys maybe for local testing outside of the CF Dev. So you can use these service instances with your IDE. So you can directly use them in my IntelliJ, starting some of my stuff there locally and connect to that database also. So because I have it there, it's available. And then I can also push to CF Dev my app. And the best thing with that is, if I want to restart my tests, I delete that service instance, create a new one and start over. So if you look at Docker containers, you have that problem maybe that the Docker container may be stopped and started and maybe lose things. And here you have a proper lifecycle management through the service broker maybe. And we also have the possibility to add amounts of saving to the local disk. So you can restart things and so on. So what we're doing with the CLI, I want to start over with my service broker. So first of all, I have to have a vendor version of my service broker, which has a direct way to interact. So my CLI is needing some container for my service broker. I don't know what it is. It could be something different, but I have a tar file, a tar ball with a deploy and a remove script, which can be run on my machine locally to start up that service broker to deploy it somehow and to remove it. And I have some binaries in there, some push releases maybe, some config files maybe. I don't know because the deploy file, I want to start with my CLI student the job. And what is done, the deploy script is called from the CLI to, with giving me a host them, it wants to register later on the service broker. And the username of the password, it wants to use for that. And the other thing is later on, it wants to remove that service broker. That's it. So for example, with our MongoDB, I have a deploy script, my remove script. I have a JAR file, which is the service broker. I have a push release, which creates MongoDB VM inside of the hyper kit maybe. I have some config files I want to use for the deployment here. And I deployed with my service broker, admin, admin. And later on, I remove it that way. So what are the benefits? What did I achieve against getting Docker? First of all, I have the same deployment methods used alike in production. If I go later on to Cloud Foundry, my test experience on my local machine is the same. So I've completely the same thing, the same way to use the services. I don't have to use cups on my local machine to get that Docker stuff used for my CFDF, I do not have to tackle with my networking or my local machine to the hyper kit, where I have to tackle these different things with my Docker. The service brokers are maybe the same things I use also in the production environment, because they only use a small plan instead of big cluster. But it's more or less could be the same service broker with a different plan, which is used for local tests, which I use for testing also in the test stage in my production environment. I can use the CLI plug-in for scripting in difference to that. I can have Docker files, which I mostly have to get from somewhere. So I get some from Docker Hub, some MongoDB, Docker file, and then I say, cool, and yeah, this doesn't work that way I thought so. Then this, and the MongoDB is completely different configurator than in production. Then maybe, but there is a Docker file for everything on the web. So it's a bit of a things for that. But if I look at the two operations with my databases, with the Docker file, I have to do all that things by hand. I have to delete my Docker file, I have to restart it. I have to look at how it is started up. Do I have to introduce some advanced configuration stuff so it's comparable to the things I do in production, where I have here a database lifecycle management through the CFCLI, because it's a service broker. And I have a service key management which I can also use to make it differently available. So let's see what it does, how it works. Okay, wrong package I see, so, where we are. I have here my service broker repository folder, whereas I have my service broker in there. So I have here the files I talked about, the deploy file, the MongoDB jar, and here I have my packaged table, which I now want to upload to my Cloud for Android. So if I go back and I, CF, CF, OSB, got it wrong, CF, OSB, CF, OSB, add. So what I want to do is, I want to, this is one step, I forgot. Live demos, summit, it should be local. MongoDB service broker, create and serve. Forgot to start my web server, now we can do that here. Starting a web server for providing the tar file for me. Now if we go back, if we go back, CF, OSB, add. Now we retreat from our local web server, the tar file. Adding the things here, creating new space for my service brokers, uploading things, and look in and now marketplace. Nope. What did I do? Did I get it wrong? CDLS, I see it.  And now it go. Now we see it. Why don't you want to talk with me? Yeah, I can do that. Ah, you're right. You can totally right. I knew, I did. What changes to Mongo? What changes here? What is, what? You use Mongo.tgz. Ah, now it, yeah, now it loads Antares, uploads. This is the power of Perry. Yeah, it's perfect. Takes some seconds, I know, because it has to upload that to the hyperkit VM of the Bosch director and spawn a VM in there and installing MongoDB there. So because it's a pre-provisioned MongoDB servers. In the meantime, any questions until now? I know it's a little bit flaky with a demo, hands-on demo. What I created is, I started a service where the files I described beforehand into the tab all, upload, made it available with the HTTP process. Then I said I wanted to edit as a new service to my CFDef and make things available there. In the meantime, we wait. Let's talk about where we want to go with that. In the long run, we want to go to CF local because this is a little bit more less aggressive in the resources of your local machine, but the drawback is you have no Bosch director with that, which most service brokers need. So we have to circumvent that. We actually have seen, I used a web server for that because the initial CLI tool only use web address at the moment. I want to change that you can change between local file system and using the web address. You've seen the debug log is not that optimized. So we need a bit more for there and only at the moment because of CFDef and so on, we only support macOS. With CF local, you have also other distributions like Windows working. And so this would also improve the footprint on the local machine. Our documentation could be better and we want to have a standalone mode without CFDef or CF local so you can also use this for providing your database locally without doing all of the other stuff. So you can only for your IDE spawn up the MongoDB, then remove it and so on, maybe with Eden, CLI and so on. So you can directly interact with that. Let's switch back. Oh, I know. No, let's have a look. What's going on? Ah, no, it's there. What's in between? So if I now want to test something, an app, so I have a script for spawning up a new space, adding some information about that in manifest and then pushing our music spring app to Cloud Foundry using a new service instance I created. I can easily do things like that. So where is it? So if I have this thing here, so he says there's no test instance, so I create, so I go to Marketplace, CF create always be MongoDBXS called test. Ah, you're right. What is my typo day? It's already there. It doesn't do what the wrong one. Clean up, know that I didn't want, test, test. Somewhere there are too much presentations. There's nothing more in my history than test, test, test. It was space service, service plan, service instance app, app path. So it is, test as age, the greatest was test, test and music, service, did I miss something? Space? Ah, yeah. So one more test. XS, did I get it wrong? So you have two tests in a minute. No, I think I know what's the problem. Oh, yeah, location. Looks better. Nobody can accuse you for not being live? No. This is not a fake demo, I guess. Should we take some questions? Yeah, we should do. Do we have some questions to that? And now it looks a little bit freaky at the moment because of the demo. And I tried to script things and then forgot to. So I'll ask, you said you want to add it to CF Dev? Or something like this? No, at the moment it works with CF Dev. So if you have to have CF Dev started at your local machine, I did that beforehand. And here you see the code from the music app. So if you look at browser, I don't think that's the right one. So this is the spring music app using the MongoDB service. And so what we were talking about, what I meant was we were using CF Dev. So I've run CF Dev, started during the keynote, started up my CF Dev, and use this now here. And by the CF Dev has a very big footprint on your machine. If you look at the, it takes about more or less of this old laptop here, the full memory, which is not cool if you want to run an IDE next to it. For that, CF Local, which uses Docker containers, it's a little bit less strong from the footprint. And because it doesn't utilize, it makes about the user experience, but not about creating a complete Cloud Foundry next to it. It would be much better for the user, for the developer. So we want to go there. But CF Local, because it's a Cloud Foundry deployment, doesn't have a Bosch directory, which most of the service brokers need. So what we have to do then is deploy a Bosch directory for the CF Local to work with it. And by that, we have to look when start making the CF OSB ad that he looks, is there a CF Dev or CF Local, and then starting the things for it. So this is work to do. So you can use less footprint. And also, we have to come up with a trick if there's nothing of both. So you can use it in standalone mode. Coming from someone that is running Cloud Foundry on Kubernetes, the missing Bosch directory in CF Local is kind of a feature for us. Because so many things currently in Cloud Foundry rely on Bosch being there. And, well, not even sure how this is going to be solved in the future. The problem is most of the service brokers at the moment do. So if you want to use arbitrary service brokers with that, you have to have a Bosch directory for them prepared so they can utilize that. You're right. If you want to get along without a Bosch directory in the long run, and you want to use Kubernetes for your data services, you don't want to have that. So we may add some information in the configuration of the service broker tab all to show any of the Bosch directory I don't need it. So you can deploy them with less footprint. This could be a possible solution. Maybe one very technical one. You were always using SH, so the born shell when you ran your scripts. Is this explicitly to avoid people running into bash and something like that, or reinstall and deploy? The plurse edge is at the moment it was only, it is a little bit of enforced. But I'm not sure if that is a good thing. It's an early stage of the project. So it was for the easy access, because an SH is easy to write. For the long run, we have to come up with a better trick for that. I feel like a little CLI. Yeah. I didn't work with some of the technologies you showed in quite a while, but the last time I used them, it was very, very flaky on the local machine. The CFDF. The CFDF as well as Bosch Lite and everything. Yeah, you're right. And there are quite a few differences between depth and production once you use them, because you have completely different setup locally than in production. So would you say that this small gain of depth brought parity you gain by the setup is really worth the effort compared to running those services in Docker and just bind them to Docker? The problem with the Docker thing is you have when using Service Broker, you have a distinct configuration of your service. So it's not about the cluster or not a cluster for most services, but also which are the predefined type character sets and so on in the configuration, how it's preparations for the wrapper set configuration and so on for bigger clusters. You have also in the smaller depth versions of the service brokers often. And if you look at the Docker versions you find on Docker Hub, for example, they're completely different. So if you have a Service Broker provider, which has also a Docker file, which would be completely same configured, that would be you could easily use that Docker file. But often you don't have that. So you want to have a service broker configuration like that on your local machine. Very last question. I assume this only works with stateless service brokers, right? Once they need any backing services, this might get a little chicken-ack problem. Actually, this Service Broker has a back end. Which is Mongora. Yeah, which is spanning up on its own virtual machine, which is deployed to his running on a virtual machine deployed by the Bosch director. So if you look here, if you look down there, you have a Service MongoDB VM, which is having the Service Broker. And there he has a local file system. And also there's running a local MongoDB for the back end of that thing. So it doesn't have to have more than one release. Thank you, Christian.


The phenomenon of the death of languages has been known for a long time. Some languages have disappeared without leaving any trace. Others jealously guard their own secrets because no one has succeeded in deciphering them. Finally, there are those languages which have evolved and given birth to new languages. We know that, like any living thing, a language placed in a specific context blossoms or fades away and dies. This e-lecture gives a brief description of the phenomenon of language death and discusses the following aspects. First, we will look at our heritage. That is our duty to preserve and protect languages and cultures. Then we will look at the mechanisms of language death and language endangerment before finally we will look at some aspects that can be implemented to protect languages from dying out by multilingualism. There are about 7000 languages spoken in the world today. Most of them in several dialects. Many of them are no longer spoken and are now extinct. Each language reflects a unique world view and a unique culture complex mirroring the manner in which a speech community has resolved its problems in dealing with the world and has formulated its thinking, its system of philosophy and understanding of the world around it. Each language is the means of expression of the intangible cultural heritage of people and it remains a reflection of this culture for some time even after the culture which underlies its decays and crumbles often under the impact of an intrusive, powerful, usually metropolitan, different culture. However, with the death and disappearance of such a language an irreplaceable unit in our knowledge and understanding of human thought and world view is lost forever. For this reason, the protection of endangered languages is among the most important goals of modern linguistics. But what exactly is language endangerment? A language is said to be endangered or at least potentially endangered if it is no longer learned by the children or at least by a large part of the children of that community say at least 30%. If a large portion of the children switch to another language then more and more children will act likewise until there are no child speakers left and the language will eventually disappear with the death of its last speakers. Languages become endangered resulting in a state of being on the edge of extinction for several reasons. The first of these reasons is the forceful splitting up and transplanting of the speech community that speaks a given language putting small groups or even only individuals of the speech community into communities that use other languages. This will inevitably kill the original language of the transplanted people in a short amount of time. A second situation in which a language becomes endangered and threatened to disappear occurs when a particular speech community comes into face-to-face contact with carriers of a more aggressive culture who speak another, usually metropolitan language. The first culture is overwhelmed and threatened with disintegration because mastery of the intrusive language offers economic advantages to the speakers of the weaker culture. Parents of children in the weaker culture tend to encourage their children to use the language of the stronger culture in preference to their own and will themselves tend to speak to their children in that preferred language. The young generation will soon learn to despise their traditional language and regard it as worthless and inferior and cease to be interested in it. A third group of causes for the endangerment or even disappearance of local and minority languages can be indirectly attributed to the actions of people of a dominant culture that lead to the destruction of the environment, the habitat and the livelihood of the speakers of local languages. For example, through mining, oil drilling, excessive tree-felling, damming of rivers, warfare, etc. These actions lead to the transplanting and scattering of the speakers of the local languages with disastrous results for their languages. Other types of causes of the endangerment or disappearance of very small to moderately small local languages include natural catastrophes such as volcanic eruptions, severe earthquakes, tsunamis, gigantic waves hitting shorelines after a sea quake, floods, wildfires, new devastating diseases and then there might be epidemics resulting from contacts between speakers of local languages and those of a dominant culture where the former have no resistance to diseases such as influenza or tuberculosis and in the past to smallpox and the like. It is important to know that a language which is in danger of disappearing can still be saved, provided that an appropriate language policy is adopted. The case of Hebrew is a good example of the revival of a language that ceased to be a living community language thousands of years ago. To define the degree of language endangerment an important factor is the number of speakers of a given language. Languages spoken by a large group are less vulnerable to the danger of disappearing than others. However, the problem here is that the question of a large or small group of speakers is quite relative and is determined by the number of speakers of surrounding languages which are culturally aggressive. Let us look at two examples. Australia and India. They help us to illustrate this point. In Australia, very few of the many indigenous languages ever had or even have today more than a thousand speakers but they are nonetheless regarded and referred to as large languages because the average number of speakers of viable Australian languages with fewer speakers is a few hundred or even less. In Australia, about one percent of the population is of aboriginal descent of whom 47,000 have some knowledge of an aboriginal language. Here are some examples. There are languages such as Al Yawar and Anindil Yakwa with a thousand or more speakers. And then there are highly endangered languages such as Jirbal, Yidin and Gumach with a few hundred or even less speakers. In 1995, about 200 aboriginal languages were still spoken. Now only a hundred or so remain and most of them highly endangered. Aboriginal languages were traditionally spoken by relatively small groups but each had its territory, its culture and the transmission assured. When the Europeans arrived, they occupied these territories, massacred the people and almost destroyed aboriginal cultures. In India, on the other hand, in areas around India and in India itself where languages such as Hindi, Gujarati or Bengali have millions of speakers, languages like Brahui with two million and Hintco with 600,000 speakers are regarded as small languages and will feel pressure from neighbouring languages with these several dozens or even hundreds of millions of speakers. So the question of large or small numbers of speakers is quite relative and is determined by the number of speakers of other languages surrounding languages which are under pressure. The dying and disappearance of languages has been going on for thousands of years as a natural event in human society. But at a slow rate, with few languages here and there in the world disappearing slowly over the years, this trend sometimes increased locally for a short period of time. For instance, when a powerful, conquering group of warriors attacked and killed certain small groups of people such as the North American Indians speaking a variety of different languages and whose languages died with them. Or when natural disasters such as violent volcanic eruptions or great floods wiped out small tribes of people who spoke a number of local languages. However, such events did not bring about the disappearance of hundreds of languages at the same time and at a steady or increasing rate and did not result in a drastic and catastrophic reduction in the number of languages spoken in the world. The current situation, however, over the past 300 years or so has seen a dramatic increase in the death and disappearance of languages. A few of those such as Latin, Greek or Sanskrit, to name a few, have been kept alive artificially and are still widely known and sometimes even spoken in certain special circumstances by quite a number of persons and maybe in other cases by few persons in the case of ancient Greek and the languages spoken in former Egypt. Today, however, at a steadily increasing rate in many parts of the world we have to face a situation in which 3,000 or more languages that are still spoken are endangered, seriously endangered or even dying out. In Europe, believe it or not, our language index lists several dozens of endangered languages and furthermore, there are still viable languages such as Welch, which we can put over here, that already show signs of being potentially endangered and might soon enter the phase where they will face disappearance. There are many examples of the four main reasons we have already given for language endangerment. A paradoxical way to prevent a language from becoming endangered is to promote bi and multilingualism, which is already the norm in many parts of the world with several thousand especially smallish languages spoken by bi and multilinguals irrespective of whether they are just a few members of a speech community or very many or the entire community. The main advantages of bilingualism can be seen in what you call bilingual speech performance. Now, bi and multilingualism make it possible for speakers of languages under threat from languages spoken by bearers of aggressive culture and civilizations to acquire a good knowledge of the latter for economic and other reasons while maintaining a good knowledge of their original languages. This allows them to preserve their cultural and traditional identity and maintain their own self-respect and self-esteem. Bi and multilinguals tend to be superior to monolinguals in having more flexible, more alert minds and a greater and quicker thinking capacity on the basis of a much greater volume of memory which they have for mastering two or in the case of multilinguals even more than two different language systems with different vocabularies, different grammars, different sound systems and different idiomatic expressions. Bi and multilingualism from very early childhood onwards to be maintained past the age of six years is the most advantageous quality a person can possess. Unfortunately, these aspects are not encouraged in most of the major cultures. The speakers of whose languages are overwhelmingly monolingual and wrongly regard monolingualism as the norm and the preferred state for human language. Let us summarize. In this e-lecture, we have discussed an essential aspect of our heritage the protection of endangered languages from becoming extinct. We discussed the main reasons of language endangerment and language death but also pointed out some measures to overcome the trend language policy and multilingualism. If you want to find out more about endangered languages or languages that are extinct, I recommend consulting our Language Index where you can examine a large corpus of audio-supported language samples and if you wish, contribute with an entry of an endangered language of your own in order to save it for our successors. So consider this e-lecture not only a lecture on the topic itself but as an appeal to all of you to help us here. Thank you very much.