20 Burst results for "Cooper Netease"

Russia Still Using 'Brute Force' to Break Into Computer Systems

Cyber Security Headlines

02:18 min | 2 months ago

Russia Still Using 'Brute Force' to Break Into Computer Systems

"Russian military cyber unit behind large scale brute force attacks a press release issued by the national security agency on thursday indicates that the russian military cyber unit used a cooper netease cluster to quote conduct widespread distributed an anatomist brute force access attempts against hundreds of government and private sector targets worldwide and quote. The advisory indicates that the threat actors used the brute force capability to access sensitive data and identify account credentials. The actors exploited well known vulnerabilities including microsoft exchange bugs for remote code execution in further access to target networks. The advisory notes that the attacks are ongoing enlists mitigating steps. That network administrators should adapt including use of multi factor authentication implementing timeout in lockout features. Use of strong passwords and deploying zero trust security models authorities sees double vpn service used by cybercriminals a coordinated operation by authorities in nine countries from north america and europe resulted in the take down of the double vpn service which allegedly served as a hideout for ransomware operators and fishing scammers double vpn which was heavily advertised on both russian and english speaking underground cybercrime forums offered its customers single double triple and even quadruple vpn connections for as little as twenty five dollars per month to help them hide their misdeeds a seizure notice appearing on the now defunct site indicates that law enforcement has taken possession of double vpn servers including details of all of its customers and goes on to state quote. Double vpn's owners failed to provide the services. They promised and quote microsoft research team reveals critical. Vons in nekia routers on wednesday microsoft's three sixty five defender research team revealed three critical authentication. Vulnerabilities impacting neck year routers. The first bug allows unauthenticated access to any page a susceptible device by appending get variables in sub string requests while the second flop permit side channel attacks which allow attackers to extract stored credentials in the final bug allows extraction of the net gear back n. t. g. r. b. k. Encryption key allowing remote attackers to decrypt an excess stored.

National Security Agency Microsoft North America Europe Vons
Temporal Product: Managing State With Ryland Goldstein

Software Engineering Daily

01:25 min | 4 months ago

Temporal Product: Managing State With Ryland Goldstein

"Done a show about temporal before and workflow engines in general. But i think it's a pretty deep subject and i like to start off by just exploring. The distributed systems related problems that a typical infrastructure team might encounter. That are still not solved by all these nice tools that we have today like. Aws and cooper netease and so on what are the outstanding problems. Yeah it's a great question from my point of view. It's actually sort of the same problems that people have been. Having even before distributed systems were like in vogue and they were the way to build applications. I think you know the same problems around. You know transaction optimistic basically guaranteeing that things like transferring. Money works out. Well those were problems that existed far before you know. Most systems were distributed world. These web scale companies. I think what ended up happening. Is that those problems they lingered you know. Those are still challenges that companies that are really important like banks and other financial institutions. even just like ecommerce. They still have to solve those problems. But now it's under the context of having to do it in a distributed environment and so it's essentially having to solve the same problems that were already challenging but now the pieces that you're actually building your application on top of in the things you're sort of relying on our shifting under you because their these distributed systems with all these edge cases

Cooper Netease
Temporal Product: Managing State with Ryland Goldstein

Software Engineering Daily

01:25 min | 4 months ago

Temporal Product: Managing State with Ryland Goldstein

"We've done a show about temporal before and workflow engines in general. But i think it's a pretty deep subject and i like to start off by just exploring. The distributed systems related problems that a typical infrastructure team might encounter. That are still not solved by all these nice tools that we have today like. Aws and cooper netease and so on what are the outstanding problems. Yeah it's a great question from my point of view. It's actually sort of the same problems that people have been. Having even before distributed systems were like in vogue and they were the way to build applications. I think you know the same problems around. You know transaction optimistic basically guaranteeing that things like transferring. Money works out. Well those were problems that existed far before you know. Most systems were distributed world. These web scale companies. I think what ended up happening. Is that those problems they lingered you know. Those are still challenges that companies that are really important like banks and other financial institutions. even just like ecommerce. They still have to solve those problems. But now it's under the context of having to do it in a distributed environment and so it's essentially having to solve the same problems that were already challenging but now the pieces that you're actually building your application on top of in the things you're sort of relying on our shifting under you because their these distributed systems with all these edge cases

Cooper Netease
"cooper netease" Discussed on .NET Rocks!

.NET Rocks!

04:27 min | 2 years ago

"cooper netease" Discussed on .NET Rocks!

"T shirt, visit d d dot dot net. Rocks dot com to get started. And we're back. It's Richard Campbell Carl Franklin run dot net. Rocks to our friend, rob Richardson talking about STO, and this sort of mature model of containers, orchestration dealing with multi clusters and the endless naval terms. They use. It's been so long heaven seen you since an entire commercial ago. Have you been? Seconds. Rob. What even with yourself? We've been shipping things all over the place. Yeah. You could ship quite a lot in thirty seconds. There you go. I love how Cooper Netease has all of these naval themes, and like all of the things building on top of it have now introduced says, as well is the oh, polling in all these things. We're gonna run out of words. We're going gonna have to start using like naval ranks and all sorts of very obscure, naval words that sailors, don't usually say in mixed company, you know. Yes. Naming things is hard. It is hard. Yes. And renaming things is harder. Because it's like okay, do I take the overhead of renaming all of them? Or do I just rename the ones that I bumped into today? What happens about those ones that I didn't bump into do I rename those eventually do? I not now. You can you definitely can get down the rabbit hole with the names. And yeah, it's the only after go so far. I don't know what the heck in this studio is, but it doesn't matter. I can see. I think I can remember this. Yeah. So close enough for the name should we explore? I actually I want to stay on the brownfield story. So we've got a customer, they're running in VM, you're starting to peel stuff out in containers. Do you wait until you've emptied the VM before you light this, upper, can, you do sort of interim phase with a few things running in containers and everything else, still in the VM? What's cool about STO? And I've never practiced it in this way, is that is DO in theory is this mechanism of communicating between things and is not necessarily tied to Cooper Netease. In fact, they very specifically have an implementation tier to get their traffic, shaping methodology into Cooper, Netease, so in theory, you could pointed at some virtual machine services and pointed at some container services. And that sounds interesting of ideally, I kinda wanna wrap all the things in this security blanket. And if it's running in VM, can I ensure that all the traffic coming out of the VM goes through my proxy? I don't know it feels like an interesting exploration. Right. And they I mean they're offering support for different containers services as part of the traffic management. But that's not the real issue. Right. The real issue is getting this stuff that isn't in containers at. All right. I mean in the end it's all Tia, lest HDP. So you should be able to get to it in the end. Yeah it's just data. More data. And I love that in the end is just data, but it's probably running overage to defeat nowadays. So in the end, it's just a web connection says that's kind of like our baseline assembly today. Yeah. You don't you don't really need to go further than that. Should we dive into some of these details about what these entities are within steel, like we know at envoys are, but mixers and pilots and citadels and galleys should we go down that rabbit hole? Yeah. Definitely. We can those start to get kind of weird as we dig out the pieces of another way to go is we can look at. So now that I have this proxy mechanism between my services. What abstractions can I build on top of that? So either path could be really entertaining to dig through. Well, you're the expert so you decide. When I have this mechanism where I've got this control plane, this pilot that drives traffic between containers. Well, now what if I drive some of my traffic to this other container and most of my traffic to the regular.

Cooper Netease rob Richardson Richard Campbell Carl Franklin Cooper thirty seconds
"cooper netease" Discussed on Software Engineering Daily

Software Engineering Daily

02:33 min | 2 years ago

"cooper netease" Discussed on Software Engineering Daily

"It's like people I've seen people try to size the market of life, cloud native or cloud software or Cooper, Netease market. I don't think it's like sizable at this point. I think it's just gonna grow and grow and grow and grow so big there's so much opportunity. It's so true. It's funny. I think you get that ask that question a lot, right? Like what's the size of? The market. And it's like, well, I mean like, you know, the economy, I don't know like what's the answer? It's like it's like, right? You know, if software it's the world and Cooper Netease each software. Right. Like, you need you need automation right in its twenty. I was always tell the story around why communities matter so much because reference the Twitter fail. Did you remember when when Twitter the like they used to see the fail all the time? I do of course. Yeah. In like that was what ten years ago? Right. And that was this big successful Silicon Valley company in the couldn't figure out how to deploy reliable software. Right. I mean, hell Salesforce still puts out like service interruption updates on their website that they're gonna take their site down. Right. Like we ten years ago. We didn't know how to build reliable software like really, no one. Did. We didn't have the primitives has said, no one. But one company knew how to build reliable software, and it's why if your internet feels flaky you go and you ping, Google dot. Tom to see if it's up, right? Internet's working you trust that Google is up more more likely than you trust your internet is up right in. So what happened was Google took this system? They wrote all the software in order to to make their their services reliable. And when they did that, you know, they called it board, and it was basically container orchestration. And then they open source did his Kuban Netease. And they gave this primitive to the world that now allows anyone to create truly reliable software. Right. I mean, they wrote the book on it the SRA book site reliability engineering, right and with this primitive. So, you know, the kind of circling back to Twitter they took the concepts. I could go is using and they built their own version of it. They caught it mazes right in kind of like, you know, they took the maze project, and they really, you know, use that internally as they used a solution that was contained orchestration in scheduling in order to solve their fell well problems. But now more and more companies, you know, have access to to build truly reliable software and. That's going to just change. What's what how we think about? How we use off wear. Right. So the opportunity is just enormous. Okay grant. We'll great talking to you. Thanks for coming on the show. Yeah. Thanks so much have your oven.

Twitter Google Cooper Netease Netease Kuban Netease Cooper Salesforce Silicon Valley Tom ten years
"cooper netease" Discussed on .NET Rocks!

.NET Rocks!

02:11 min | 3 years ago

"cooper netease" Discussed on .NET Rocks!

"Any service yet exactly right now is only for links workloads. Right. And and presumably at some point the Amazon Kuban any service on the Google will as well. Oh, yeah. Absolutely. So two things need to happen. So that they need to support windows twenty nineteen as an operating system for the VM. So. They didn't age that runs twenty nineteen on then Cuban TS one team needs to. So that will have the window support. And then the cloud operates is can bring nine to their offering. So I'm guessing night when we first because if you look the Cuban development community and they've got their own slant community week who follow what's going on most of the development Weiss being done, a ks to verify all the bits and pieces. So I'm guessing I guess we come fuss. But yeah, then then Google, and then we'll follow very likely to follow. But it it does open up the store to Cooper Netease. When says done, I just can't imagine anybody using anything other than Cooper says a service. Yeah. It's a valid point. So most of our customers right now using swollen because historically not sold the DACA supported in our own enterprise. Plus the platform we adopted Cuban Netease. So now, you can run on the same Kosta the same set of serve as you can run swim or Cuban Netease to get up so economic team who perfect Cuba, Netease who are deploying stuff with cube a different team. He professed swollen on the same set of his obviously on primal, or in the cloud using using is I'm so, that's that's pretty powerful. If you make a choice to to Cuba, Netease, then you can still use your DACA, compose files. So DACA, compose is the application definition language that says, right? I have a website at the uses this Dockery made on a have a proxy visas. This DACA remain on. I'm running a message cube with this image all that sort of stuff then the dog composed the entice is much simpler on this. What you use on on the desktop won't develop as us with your Cuban deployment. You can take your DACA, compose files and deployed to Cuba Netease as well. So you get the benefit of a simpler language, which is easier for teams to what together on if you if you go full Cuban TS to saying that it's a. A more complicated language. It just takes takes more time to get your head around all.

Cuban Netease DACA Cooper Netease Cuba Netease Cuba Google Kosta Cooper Weiss Dockery
"cooper netease" Discussed on Software Engineering Daily

Software Engineering Daily

03:31 min | 3 years ago

"cooper netease" Discussed on Software Engineering Daily

"Of coin base supposed to did with. I believe one of the core. Technical folks over at twenty one the company coined bits acquired called. Quantifying decentralisation to really great post. I'd linked to it in the in the blog on the podcast here. I think that both distributed systems and decentralized systems kind of go hand in hand what I've looked at and observed anyway, and in a lot of these buck chain exchanges and kind of crypto crypto currencies startups as well. As Stephen large token like networks and things is a lot of them actually run on Cooper, Netease, which is really interesting. So maybe not like inherently a lot of collaboration between those two communities. But interestingly this whole cryptocurrency blockchain ecosystem uses a lot of distributed systems technology in particular Cooper nowadays to build their products, build their networks and their stocks and so on so I think that eventually we'll start to see a lot more collaboration in a lot more sort of respect for both sides. I'll say one other thing here though, which is kind of maybe an emergent property of how the decentralized systems community has developed from the. Emergence of bitcoin white paper about nine years ago to now we started to sort of see people vector into that community driven by economic interests in sort of digital money an antagonist stick us stance toward our current financial system. Whereas the distributed systems community has been much more grounded around kind of computer science, and technology and building building more robust software and things like that very very different sort of entry philosophical and intellectual entry points in terms of the people that make up those communities. So I think that's probably part of why we've seen a lot of not necessarily polarization, but like a lack of collaboration. Well, it's possible. I'm basically asking the question. Hey were at a coober Netease conference could Bonetti's is based around computers. Computers require electrical engineering. Where's the electrical engineers, why aren't there electrical engineers this conference? Like eventually there is some point at which there is not enough porous Innis between two. Immunities that you just don't get as many electrical engineers at a cougar Netease com. Vast something that's much more directly correlated, which is decentralized systems build and run on top of distributed systems. And there are so many similar goals and outcomes that both those communities have trying to achieve in terms of building very robust, scalable platforms for large, you know, millions of users or large amounts of data that I think they should be communicating in clobbered a lot more and then they're not. So crypto currency protocols are open source are you investing in them? I think for Osas capital were really focused on business models and companies that we really understand. Well, so if you look at the sort of Representative list of companies in the commercial open-source software company index companies like elastic and red hat, and you know, get hub get lab meal. Soft Tomago Deby Cloudera res- labs. Hashi core. Many of these companies they. Tend to be sort of B two B B to C and oppress software companies really at the end of the day. Cryptocurrency protocols are very different animal and sort of fall outside of our circle of competence. If you will so we're just really focusing on what we understand really, well is an open source social network, a viable business. I think it could be I think it could be it depends on how you define social network..

Netease Cooper Stephen Tomago Deby Cloudera res Osas Bonetti Innis Representative nine years
"cooper netease" Discussed on Software Engineering Daily

Software Engineering Daily

03:45 min | 3 years ago

"cooper netease" Discussed on Software Engineering Daily

"So I'll give you a couple of really basic things. So red hat, people tend to call the open source projects upstream just because we think of things as there's the the open source project and then sort of in our business world sort of flows down into the things that become commercial products. Some people just call it the open source project. So upstream, open source project kind of one in the same. This who governs the Kuban ED's project, you know, wanted to make sure that we were all sort of adhering to this idea that Cooper Netease was going to be usable as a multi cloud project, multi vendor project and so forth. And so they created a set of tests that allow you to say, here's my distribution of Cooper Netease. Here's the thing I would take to market. I wanna run it against your set of tasks that will validate that we haven't changed anything that we haven't done anything differently that if somebody's starts running containers over here and then wants to move it to a different environmental work fine. And so that's where you hear the CF saying, we have. Conformant or certified Cooper Netease just relations. And so that's a good thing for the market. It sort of lets them know, okay. If I'm using vendor a. vendor b. service air be, I should mostly sink should all just work the way they are. And then I think the word fork, the reason people kind of get upset about forces. There's some folks in the in not just a Cuban is community, but have been any open source community when you add bits to to the open source project to an upstream project. Sometimes they'll say, well, you know, that only comes from this specific vendor, and that's a fork and the reality is lots of vendors. Lots of projects will add things to them for the very distinct thing in open source at essentially says, we took a copy of that project and we are going to we being whoever that is. We are going to essentially run a parallel project to that original one, and we're going to kind of disconnect ourselves from that. And there's reasons why that happens. Sometimes it's political. Sometimes there's technical, you know, the node community went through this a while ago, but in the case of coober daddy's their art. Any coober Netease forks. There aren't. There isn't a split in the community in any way, shape or form. So I think we try and be very careful not to use a word like fork just because it has certain very distinct implement implantations of what you're doing to the rest of the community. In the case of adding some additional features that are above and beyond. What's just in the open source project that typically is the first thing that you often see in a distribution is additional stuff that typically is intended to make it easier for customer to use more secure for a customer to use, maybe a unique user interface, whatever those things might be the conformance standards that the CNC f- has put in place as I understand. Those are to give con stamp of approval that the CF saying to, for example, an enterprise VIN enterprises shopping around for what kind of couvert Netease distribution. They wanna use. They can find one that has a stamp of approval by the CNC f, which will mean that there's going to not be. Much lock in or at least lock in will be minimized to an extent that the CNC f- can endorse it. Is that the right way of looking at the conformance standards? Yeah, I think so. You know, the CF doesn't want to be a gatekeeper actually the way that they do their conformance is really very cool. In essence, they take the exact same tests that they use to the community uses to build and validate, builds open of coober Netease and they go, here's the tools. So you don't have to wait for a long process from the CNC f you actually can do self validation self conformance. You've run through these tests. You send the results that come back to the CF. They publish them. So as a very basic starting point, if you're an enterprise in your saying, we're thinking about Cooper Netease and we don't want to just pull the bits ourselves..

Cooper Netease Netease Kuban ED
"cooper netease" Discussed on Software Engineering Daily

Software Engineering Daily

02:02 min | 3 years ago

"cooper netease" Discussed on Software Engineering Daily

"I've cooper netease cloud foundry mesas and then we have this variety of storage vendors we have amazon abs like we mentioned google persistent disk net app the some other legacy storage vendors how the variety of container orchestrators and the variety of storage types how have these communicated in the past because we've had cloud foundry for a while had mesa's for a while this point had kuprin eddie's for several years in these years leading up to the present how have the container orchestrators and the storage systems communicated so typically like before csi was introduced i think each different contain orchestrations system like cuba nineties call foundry mesa's they all have their own interface internally that the vendor has to implement so that the seal contain australian system can talk to those vander during the life cycle of volume for example for example kuban nettie state half flex volume on also the intrigue owning driver so that as a storage under like i'm a net up i can't eat to riot flex volumebased implementation to connect to criminalise on right in the intrigue on driver for dance so that's for tuba nineties floor on doctor mesa's cough andrei actually all these three are previously using this interface called docker volume driver interface on dvd i so that's an interface that's kind of internal to docker but stock is so popular dan those two other contain oxygen system decide to use that to talk to underlying storage vendor through dying trophies so i have a container on cooper netease for example i want to be able to write data from maya plication container to a persistent storage type there are many different storage types that i could be writing data to how does the container know how to connect to all these different storage types so fron user's perspective these are the details that's not exposed to the user so if you're a cuban as user that you won't use my sequel only run my sequel.

eddie vander cooper netease netease amazon google cuba andrei
"cooper netease" Discussed on Software Engineering Daily

Software Engineering Daily

02:02 min | 3 years ago

"cooper netease" Discussed on Software Engineering Daily

"I've cooper netease cloud foundry mesas and then we have this variety of storage vendors we have amazon abs like we mentioned google persistent disk net app the some other legacy storage vendors how the variety of container orchestrators and the variety of storage types how have these communicated in the past because we've had cloud foundry for a while had mesa's for a while this point had kuprin eddie's for several years in these years leading up to the present how have the container orchestrators and the storage systems communicated so typically like before csi was introduced i think each different contain orchestrations system like cuba nineties call foundry mesa's they all have their own interface internally that the vendor has to implement so that the seal contain australian system can talk to those vander during the life cycle of volume for example for example kuban nettie state half flex volume on also the intrigue owning driver so that as a storage under like i'm a net up i can't eat to riot flex volumebased implementation to connect to criminalise on right in the intrigue on driver for dance so that's for tuba nineties floor on doctor mesa's cough andrei actually all these three are previously using this interface called docker volume driver interface on dvd i so that's an interface that's kind of internal to docker but stock is so popular dan those two other contain oxygen system decide to use that to talk to underlying storage vendor through dying trophies so i have a container on cooper netease for example i want to be able to write data from maya plication container to a persistent storage type there are many different storage types that i could be writing data to how does the container know how to connect to all these different storage types so fron user's perspective these are the details that's not exposed to the user so if you're a cuban as user that you won't use my sequel only run my sequel.

eddie vander cooper netease netease amazon google cuba andrei
"cooper netease" Discussed on Software Engineering Daily

Software Engineering Daily

02:02 min | 3 years ago

"cooper netease" Discussed on Software Engineering Daily

"Anna applies that and help chart for that basic application to get you started right away and then allow you to augments those artifacts and checking into your a get hub repo properly so that they can be used by everybody nb tracked according to get commit hash along with your code and it gives you a high degree of consistency it's lets you start doing container native development right away against cooper netease and that's the first thing does a lot of words i know but the it's worth going on and having a look at some of the demo videos you get a feel for how easy that is indeed please continue okay so a problem with that is that those are only basic that's getting started applications and hello world we've got like hello ten language versions of the hello world applications in the draft bone you can use us get started building an application can you know as a service there's a larger problem that is as your service about men increases flexible that is as you master what's going on and you connect other services and things like this you're gonna be modifying your home charts you're gonna be modifying a container image to for example add environment variables and things like this as you do that those are things that we can't really detect because now you're building your custom application right your special thing in addition to which might be a private special thing about which we can know nothing and you don't want anybody else to know about it and so the question becomes how do you do that how do you handle that environment because it's not just getting started and the draft steps up here by giving you the concept of custom draft packs you can create a repository with your let's say you iterative on your your service and you worked on it and then installed it in a custom development are staging environment there some secrets in there the the real world should know so what you might do is you take your application any check into a get hub repo it's private or example.

Anna cooper netease
"cooper netease" Discussed on Software Engineering Daily

Software Engineering Daily

01:41 min | 3 years ago

"cooper netease" Discussed on Software Engineering Daily

"Yeah i think so too may do in their show and that's closer to reality so i i know we're we're running up against time but i wanted to talk a little bit about storage just because i saw you at the the storage volume group yesterday and so the question of storage if if i understand correctly is people think of containers as a place to run their stateless applications for the most part that's not to say that there's no state on a kuban as cluster you obviously have state if mostly in td as far as i know well that's like the state of the cooper netease clusters maintain a net d at least but but as far as having stateful long running applications i think the people are not using cooper netease for example to to host their own databases as much as they are using coober netease for applications that are interfacing with a database that's in amazon the guard ds or interfacing with s three or something and there is a lot of desire to get database and database like solutions to object storage at cetera file storage block storage on a cooper netties cluster so that building blocks can be built in a cooper netease cluster agnostic of a certain cloud provider am i understanding the motivation for working for the the storage so yes i think a lot of people talk about containers contain orchestrations and kube rene says being the thing that can start to give people cloud portability but how can you really get cloud portability if you're still tied in and locked in.

kuban cooper netease rene netease amazon
"cooper netease" Discussed on Software Engineering Daily

Software Engineering Daily

01:41 min | 3 years ago

"cooper netease" Discussed on Software Engineering Daily

"Yeah i think so too may do in their show and that's closer to reality so i i know we're we're running up against time but i wanted to talk a little bit about storage just because i saw you at the the storage volume group yesterday and so the question of storage if if i understand correctly is people think of containers as a place to run their stateless applications for the most part that's not to say that there's no state on a kuban as cluster you obviously have state if mostly in td as far as i know well that's like the state of the cooper netease clusters maintain a net d at least but but as far as having stateful long running applications i think the people are not using cooper netease for example to to host their own databases as much as they are using coober netease for applications that are interfacing with a database that's in amazon the guard ds or interfacing with s three or something and there is a lot of desire to get database and database like solutions to object storage at cetera file storage block storage on a cooper netties cluster so that building blocks can be built in a cooper netease cluster agnostic of a certain cloud provider am i understanding the motivation for working for the the storage so yes i think a lot of people talk about containers contain orchestrations and kube rene says being the thing that can start to give people cloud portability but how can you really get cloud portability if you're still tied in and locked in.

kuban cooper netease rene netease amazon
"cooper netease" Discussed on The Internet of Things Podcast - Stacey On IoT

The Internet of Things Podcast - Stacey On IoT

02:01 min | 3 years ago

"cooper netease" Discussed on The Internet of Things Podcast - Stacey On IoT

"Little blobs of compute infrastructure that you move places that run the code that you need so it contains all the libraries everything you need in the idea is basically stick all the libraries code everything you need in this container that contains storage the compute and you can just replicate is it replicating it as physically moving at you're basically there'd being copied yeah you're spitting it up in one place or another so that's what a container is and we're seeing a lot of this i'm actually one of the craziest things i'm seeing is a lot of new startups coming up with container platforms for the edge like bacher labels which mike okay why not so let's do a little deeper in talk about what makes good for these connections the ford is it just poured ability why does that matter is portability at speed so conceptually you can thank it's not entirely correct but conceptually can think of a container is a very very small vm than in fact what it is really isn't in fact what you can hit in fact it's a delta of small difference of a base level operating system that runs on and so it enables massive portability because they're very small quick to copy over networks and things like that as we were designing our age platform we use that as portability the other reason why we used it is because there's already an open ecosystem of things that running containers and we wanted to make those vailable on the edge as well so as an example if i'm a developer and i'm very fond of no sequel for example and there's already a container docker hub for it i can just pull that down to play it out to my age device in a way i go i'm using no sequel and so the other part that we loved about the container approach is that it was a very open approach because all those things already exist in the open using tools people are already familiar with so he didn't want to reinvent wheels accent so you guys are now talking about going one level deeper ya'll you guys are using cooper netease as the orchestration layer for your containers so what the heck is a virtual kubat.

developer cooper netease mike
"cooper netease" Discussed on Software Engineering Daily

Software Engineering Daily

01:48 min | 3 years ago

"cooper netease" Discussed on Software Engineering Daily

"A lot more value out of it and i actually ended up starting as a systems administrator after about a year into the degrees so the my schooling and my day job were able to play nicely off of each other in terms of what i was learning in both places so if you like that was one of the really key elements to my success in my degree program and in my subsequent career as a software engineer and his a systems administrator and somebody working in the tech industry oh yeah well that apprenticeship phase of either having an internship while you're in college or like you did it having a copathetic combination of going to school either online or in person together with a fulltime job where you're actually applying some of the skills that you're learning the the feedback loop between those two domains can be really productive and and satisfactory because you're you know you're not throwing away money on a degree while you're not make taking money from that knowledge and you're not going to a job where you don't feel yourself leveling up as much because even if even if you were you would be learning on the side so it's a the education plus occupation path is is pretty rewarding absolutely and that's also part of why continue to do freelance consulting is because it provides another outlet for morning new things and being able to play my day job off of my consulting and you know where i i might take on a consulting engagement where i'm working with cooper netease where that's a system that i'm working on evaluating for my day job so there are a lot of potential synergies between the two activities.

software engineer cooper netease
"cooper netease" Discussed on Software Engineering Daily

Software Engineering Daily

01:48 min | 3 years ago

"cooper netease" Discussed on Software Engineering Daily

"A lot more value out of it and i actually ended up starting as a systems administrator after about a year into the degrees so the my schooling and my day job were able to play nicely off of each other in terms of what i was learning in both places so if you like that was one of the really key elements to my success in my degree program and in my subsequent career as a software engineer and his a systems administrator and somebody working in the tech industry oh yeah well that apprenticeship phase of either having an internship while you're in college or like you did it having a copathetic combination of going to school either online or in person together with a fulltime job where you're actually applying some of the skills that you're learning the the feedback loop between those two domains can be really productive and and satisfactory because you're you know you're not throwing away money on a degree while you're not make taking money from that knowledge and you're not going to a job where you don't feel yourself leveling up as much because even if even if you were you would be learning on the side so it's a the education plus occupation path is is pretty rewarding absolutely and that's also part of why continue to do freelance consulting is because it provides another outlet for morning new things and being able to play my day job off of my consulting and you know where i i might take on a consulting engagement where i'm working with cooper netease where that's a system that i'm working on evaluating for my day job so there are a lot of potential synergies between the two activities.

software engineer cooper netease
"cooper netease" Discussed on Google Cloud Platform Podcast

Google Cloud Platform Podcast

02:02 min | 3 years ago

"cooper netease" Discussed on Google Cloud Platform Podcast

"Because the story was very much about vm's in cloud at that point and so google may this huge investment in cooper netease and built a team and the strategic goal was to change how the industry talked about portable workload units and we needed to do that no way that allowed cooper netties to be ubiquitous that was the first goal is we needed cougar netease to be everywhere we needed containers to be everywhere and in order to do that you have to build huge community and open source seemed to really obvious way to do that it's a much easier way than a single product because you get a lot of people's input you get a lot of engagement you get other people advocating for you and with you but you also can't then have one company leading it and so i was brought into make help make that transition and then that turned into sort of oh and i'm doing an open source project can you help me with my community and i'm doing an open source project and then we open sourced tensor flow and we had different strategic goals which then meant how do we deal with the community that has different strategic goals in what and i mean we've done open source for years there's there's lots and lots of open source work that google histon going back to the inception of the company but it was usually early on a scratcher on it and then upstream it make sure that we are being good citizens being good open source citizens and then there was of course chrome and android which were open source projects but there were very company led and the communities were much more about ecosystems applications and the adoption and ways to extend the particular project but cooper netease had to be different and so we've we've seen all these different strategies and now we're collecting group for google cloud platform that sits in beds in communities that are either i party communities communities that google has built and wants to continue to grow or third party communities like no j s recently joined the no jazz foundation board in order to help that project become more appealing to enterprises.

netease google cooper cooper netease
"cooper netease" Discussed on Google Cloud Platform Podcast

Google Cloud Platform Podcast

01:42 min | 3 years ago

"cooper netease" Discussed on Google Cloud Platform Podcast

"Nice so you mentioned something i think interesting there when you talk about the foundation what is order it's goals but also like what drives some products to go to cnc f and some don't and what's the impetus their foundations wanna one show the club need of compute foundation was created to house cooper nettie so the original vision as cooper netease was being built inside google even as we were just having a couple of partners and just having trials with it and working out how we were going to announce it well before i started that would have been late two thousand fourteen early two thousand fifteen there was a concept that in order for this to be much more trusted by the industry it couldn't be just google as i said it had to be really community led and google has had some challenges withholding things too tightly and so we wanted to make sure that it was clear that google was really intentional about this and so in july of two thousand fifteen when one point oh of cooper netease was announced we announced at the same time an intent to build a foundation and put cooper netease in the foundation we had looked at other foundations and talked about whether or not they would fit but the cloud native compute foundation ended up being created and we wanted it to be a broader story than just coober netease because cooper netease was the start of the transformation so the cloud native compute fundation looks at what it means to build up locations that are built in architecture primarily for the cloud so the architecture that it was framed around was container packaged dynamically scheduled and something else really important i'm sure.

google cooper netease cloud
"cooper netease" Discussed on Software Engineering Daily

Software Engineering Daily

01:48 min | 3 years ago

"cooper netease" Discussed on Software Engineering Daily

"People are monitoring things like elastic search reticent and my sequel right these are mongo db like these are all things that i did not expect to see you know like this as we were beginning to the data for for containers early on or even later with with cooper so stateful services are definitely becoming a a more popular thing to run their been surprised by by quickly people are getting into it surprises you because it's bold to put your central data store of record on cooper netease to be honest i don't it's hard for me to tell you what what people arguing in there i can tell you what know what what technologies the running right but it's hard for me to say is that the master is their master database sitting inside on top of that he's i think it's just people tend to think about or about containers illustrated workloads as place to put their stateless services and so as we dive into as we see people running stateful services there at least at first it was surprising never time we run the report i'm just kinda wondering who's gonna come out in the lead in terms of the technology we see there so that's been like engine x when engine next came in number one i was not surprised at all right like that's it's definitely like the web server of choice it seems within the world of when within the world of containers when i saw when i saw elastic search coming in number two on goober nettie that's i'm a little surprised by that but okay as we started to get into things like post grads in my sequel manga dealing also little surprise but this these days is just again not to make it's not a popularity contest but it's just interesting to see what comes out on top of only to see how the patterns in how people are using containers and orchestrators or changing other things you know other stats like talk about i think it's been interesting to see how deployment patterns indus practices have emerged on top of containers in orchestrators.

cooper cooper netease
"cooper netease" Discussed on Software Engineering Daily

Software Engineering Daily

02:02 min | 3 years ago

"cooper netease" Discussed on Software Engineering Daily

"And i think a lot of us who have been around the space for a few years or starting to kind of recognize that that you know people are really starting to adopt these things but everybody's still kind of focused on using it as is and it's really exciting to find people who are you know as embarrasses metal particle is you know maybe that's not how things look but i love the people are starting to experiment with these things and you know what could good level of abstraction look like on top of cooper netease because it does require a lot of knowledge to kind of learn and and use these things and then especially if you start talking about being an operator to that's always the big thing i tell people when they're looking to to adopt cooper netease is i worked for microsoft so would i love you to use ak s absolutely right but i think the real power in having a cloud provider do the stuff is just the operational expertise you don't have to have a coup netease expert in every company there's a lot of ways that distributed systems fail in really interesting ways and we were stacking up all the operational knowledge into every individual company and i think there's a lot of power in letting somebody else worry about that while you focus on your own business domain so i've done a number of shows about cooper netties in one of the things that those interesting came out of all the shows that i did the architecture for multi cloud and how that's going to look so it seems like in the near future many companies are going to have kuban eddie's clusters on different cloud providers like you might have one you might have kuban as cluster running on microsoft and you have a also kuban as cluster running on google and you use different clouds specific services in conjunction with those cooper netease clusters for example on microsoft maybe you're using cosmo's db and you you wanna have a coup grenades cluster for that database.

cooper netease microsoft kuban eddie google kuban