24 Burst results for "Coober Netease"

Full Circle Weekly News #180 - burst 2 - Analytics 2.2

The Full Circle Weekly News

01:00 min | 3 months ago

Full Circle Weekly News #180 - burst 2 - Analytics 2.2

"De Denardo seuss's CEOS said quote this deal upon closing will combine seuss's strength and Enterprise Lennox, edge computing and a I. Lab, strength in Coober Netease making the combined company, the open source innovator of choice. Here the notable releases this episode. To add twenty four a new remix out focusing on applications for kids, schools, and universities. Endeavor is July. Releases out on their first anniversary with new infrastructure. Susan Lenox Enterprise Fifteen SP two out improving under devops HPC and cloud offerings. Plasma five dot nineteen dot three updates are out with the normal bug fixes and improvements. Lineker meant twenties upgrade path is out but can be time consuming. Canoe Cash Ford Auto and four dot one is out with a new new cash cli command for running reports and information.

De Denardo Seuss Canoe Cash Ford Auto Coober Netease Susan Lenox Lineker
Tilt: Kubernetes Tooling with Dan Bentley

Software Engineering Daily

05:36 min | 6 months ago

Tilt: Kubernetes Tooling with Dan Bentley

"Way way to to get get in in trouble. trouble. Let's Let's start start to to talk talk about about what what you you have have built built with with tilt. tilt. Can Can you you explain explain what what the the tilts tilts product product is is yeah yeah I. I Hope hope so so You You told told me me in in a a in in a a couple couple of of minutes. minutes. Share Share what what we we are are trained trained to to do do with with tilt, tilt is is make it it that that multi multi service service development development is is easy easy that? that. You You can can get get back back to to where where you you were. were When when you you come come in in in in the the morning morning or or when when you you join join a a team, team, you you just just type type tilt tilt up, up, and and it it takes takes all all of of the the source source code code for for all all of of your your different different services, services, and and it it spins spins them them up up in, in. so So you you have have a a developer developer instance instance that that could could be be running running on on your your laptop laptop could could be be running running in in a a cloud cloud cluster, cluster, and and you're you're. You're able able to to win. win. You You hit. hit. Save Save then then see see that that code code running running for for real real not not in in a production environment, but you can load it in your web browser, and you can interact with it, and you can change any line of code whether it's go code in the graph, Q. L., server or type script. That's running in the front end or a JVM, service. Right kind getting live, reload for your entire stack and so. What's important there? Well, one thing is the speed of from when you hit save. How long does it take until you're codes? Running developers are this fantastic and evil kind of lazy. Where if they see a shortcut, they'll start doing it. And it will end up being unsafe at some point, and then you've saved yourself some time because it's faster as you do it, but. When it gets out of sinker, askew. You then have to spend hours figuring out what's happening. And so I'm really proud. That tilt supports live update that you can actually update containers that are running in the cluster, even in the cloud in less than a second. You would never want to do that for your production workloads, but it's the way that you're able to get the same kind of feedback loop low latency as you had before, you moved to Coober Netease for development. And then I think the thing that we've realized is. You don't just need to get the code out there. You also need to get the feedback when there's a problem when a pods and crash loop back off when it dies when it can't even except the camel. You're able to see it in the U.. I because tilt runs as a web APP. It's running on your laptop. Your seeing it in your browser at local host, but you're able to get a holistic view, and so in addition to the logs in the center of your screen over on the right. There's a sidebar that shows you. Each

Developer Coober Netease
Tilt: Kubernetes Tooling with Dan Bentley

Software Engineering Daily

05:36 min | 6 months ago

Tilt: Kubernetes Tooling with Dan Bentley

"Great great way way to to way way get get to to in in get get trouble. trouble. in in trouble. trouble. Let's Let's start start Let's Let's to to start start talk talk to to talk talk about about about about what what what what you you have have you you built built have have built built with with with with tilt. tilt. tilt. tilt. Can Can Can Can you you you you explain explain explain explain what what what what the the the the tilts tilts tilts tilts product product product product is is is is yeah yeah yeah yeah I. I I. I Hope hope Hope hope so so so so You You You You told told told told me me in me me in a a in in a a in in a a in in couple couple a a couple couple of of minutes. minutes. of of minutes. minutes. Share Share Share Share what what what what we we we we are are trained trained are are trained trained to to do do to to with with do do tilt, tilt with with tilt, tilt is is make is is make it it that that it it that that multi multi multi multi service service service service development development development development is is is is easy easy easy easy that? that. that? that. You You You You can can get get can can get get back back back back to to to to where where you you where where you you were. were were. were When when When when you you come come you you come come in in in in in in the the morning morning in in the the morning morning or or when when or or you you when when join join you you join join a a team, team, a a team, team, you you you you just just just just type type type type tilt tilt tilt tilt up, up, up, up, and and and and it it takes takes it it takes takes all all all all of of of of the the the the source source source source code code code code for for for for all all of of your your all all different different of of your your different different services, services, services, services, and and and and it it it it spins spins spins spins them them up up them them up up in, in. so So in, in. you you so So have have you you a a have have developer developer a a developer developer instance instance instance instance that that could could that that be be could could running running be be running running on on your your on on laptop laptop your your laptop laptop could could could could be be running running be be running running in in a a in in cloud cloud a a cloud cloud cluster, cluster, cluster, cluster, and and and and you're you're. You're you're you're. You're able able able able to to win. win. to to You You win. win. hit. hit. You You hit. hit. Save Save Save Save then then then then see see see see that that that that code code code code running running running running for for for for real real real real not not not not in in in in a a production production environment, environment, but but you you can can load load it it in your in web your browser, web browser, and you can and you interact can interact with it, with it, and and you can you change can change any any line line of code of code whether whether it's it's go go code code in the in graph, the graph, Q. L., Q. server L., server or or type type script. script. That's That's running running in in the front the front end end or or a a JVM, JVM, service. service. Right Right kind kind getting getting live, live, reload reload for your for entire your entire stack stack and and so. so. What's What's important important there? there? Well, Well, one one thing thing is is the speed the speed of of from from when you when hit you save. hit save. How How long long does it does take it take until until you're codes? you're codes? Running Running developers developers are this are this fantastic fantastic and and evil evil kind kind of lazy. of lazy. Where Where if if they they see see a shortcut, a shortcut, they'll start they'll start doing doing it. it. And it will And end it will up end being up being unsafe unsafe at some at some point, point, and and then then you've you've saved saved yourself yourself some some time time because because it's faster it's faster as as you do you do it, it, but. but. When When it gets it gets out out of sinker, of sinker, askew. askew. You then You have then to have spend to spend hours hours figuring figuring out what's out happening. what's happening. And And so so I'm really I'm really proud. proud. That That tilt tilt supports supports live live update update that you that can you actually can actually update update containers containers that are that running are running in in the cluster, the cluster, even even in the in cloud the cloud in in less less than a than second. a second. You You would never would never want want to do to do that for that your for production your production workloads, workloads, but but it's the it's way the that way you're that able you're able to to get get the the same same kind of kind feedback of feedback loop loop low low latency latency as you as had you had before, before, you moved you moved to Coober to Coober Netease Netease for development. for development. And then And I then think I think the thing the thing that that we've we've realized realized is. is. You You don't just don't need just to need get to get the code the code out out there. there. You also You also need to need get to get the feedback the feedback when when there's a there's problem a problem when when a pods a pods and crash and crash loop loop back back off off when when it dies it dies when when it can't it can't even even except except the the camel. camel. You're You're able able to see to see it in it the in U.. the U.. I I because because tilt tilt runs runs as as a a web web APP. APP. It's It's running running on your on laptop. your laptop. Your Your seeing seeing it in it your in your browser browser at local at local host, host, but but you're you're able able to get to get a holistic a holistic view, view, and so and in addition so in addition to the to the logs logs in the in center the center of your of screen your screen over over on the on right. the right. There's a There's sidebar a sidebar that that shows shows you. you. Each Each

Developer Coober Netease Netease
Edge Computing Platform

Software Engineering Daily

12:11 min | 11 months ago

Edge Computing Platform

"We're GONNA talk about edge computing today and particularly red hat's strategy strategy around that. Give me two recent applications that you have seen of edge computing so to very often reasons. Why the applications WANNA run the etch is latency which means you want to have very fast request response and the second one is reducing bandwidth over the network and those are very to have very often mentioned once? They're way too many other reasons why to do that. And for me. These two reasons are mainly the consequences of what I want to achieve and if I want to improve user experience does are probably the two The latency is probably the first one if I want to reduce the cost probably reducing. The with is another one but then there are other reasons for example risk factors. I want to improve resilient therefore I want to run my applications nations at the edge and have them running in very completely isolated environment so there are really many reasons by the two. Most mentioned wants is definitely latency latency and bandwidth so the type of edge competing. We've had for a pretty long. Time is CDN infrastructure CDN infrastructure is fairly basic. It's if I make a request for an image for example apple that image is GonNa get cashed at the edge and then subsequent requests to that resource will be sent to the edge because the edge can be closer to the user and the edge. Might it'd be a content delivery network. That is pushing out that content to a lot of different locations so that a user news Becca Stan has rapid access. A user in Texas Texas has rapid access the kinds of edge computing. That we WANNA do. Today is very different than that type of simple request response for an image for example. What kinds of computation do we want to do at the edge today? I don't want to repeat myself but it's always it depends ends on the use case and there are many industries which are doing competing for different reasons. All let's take for example Industrial Iot in the production. Shen lines where they are running. They are having multiple sensors in their production lines to control quality production for example of the product the sensors are generating a lot of data data and this data is being analyzed and is being responded is the product quality. Okay can I continue in the direction or do I need to interrupt and just a process. This is kind of application which needs very fast rapid response you cannot really rely on sending that over the network to centralized location do the processing there and then and get the response back so this is very often reason why you want to push the edge computing to location of the IOT industrial but there are also reasons. Why want to centralize? You don't want to do everything only at the edge. There are reasons why you want to do centralization so imagine I have the industrial plans and I have them all over the country but I need to train my machine learning models from different examples and I want to gather those examples from different locations therefore I need to centralize them somewhere then do training model. They're likely in the centralized location and then push out only the train models to do the fast decision making at the edge so this is one of the examples right and that architecture makes a Lotta sense because in order to train the machine learning models you need all the data centralized in a particular place or you need some large subset of the data or you need the new training examples. Whatever the data to train the models takes a lot less space than the actual models that can make a decision that can improve application infrastructure? So we need to start deploying thing these models to the edge now if we talk about the types of CDN infrastructure that has been there for a long time where you're caching an an image and then you can request the image at the CDN layer if we're talking about hosting machine learning models versus hosting basic images. Do we need different different infrastructure to run those machine learning models instead of simple. CDN Type of infrastructure. Absolutely we do and it depends on the context. What kind of application I WANNA run? Therefore the machine learning very often or for example video processing or similar requests we we might need data processing. We need real time kernels we need. GP use use very often to speed up. The processing can reduce the cost of the processing power so the type of the hardware which is enabling the the use cases is specific for the application which needs to run on top of that the CDN is very simple. Use Case as you mentioned you don't really need much of the processing Specific processing processing. But if you need to run for example containerize network function. It has very high requirements on the fast data path and networking or it needs to access the real time kernel which difficult CDN networks don't need Ari talking about machine learning stuff. I've also heard of widespread bread edge competing use cases in the telecom industry. Can you tell me about those applications. So S Forty Telco Day one to do editing edge competing for multiple reasons. I would separate it into two categories first. One is to run their own brighter X.. Networks and for that that is the containerization containerization of their network functions. As you know there was a progress of running network functioning onto bare metal itself with specific hardware than it moved to. VM's and now it's to moving through containers and here the Yukon. We actually saw demo of the proof of concept how to do the five G. fully running on carbonated. That is one of the kind kind of the application. Because at the antenna level you need to have the processing as close to the signal as possible so that you again reduced latency NC and you don't have to push all the data through the network to raise the swap that is the main requirement for five G. or main features of the five G. The second use case for the telcos is to monetize their infrastructure. which they are building for the five and that is to provide mobile edge edge computing platform for all the independent service vendors or other enterprises running their applications? So I can be an enterprise fries which has branch offices and in order to get access from those branch offices to pass processing. I might want to run my applications closer to those branches not necessarily centralized in my data center which might be private cloud one national data center but I might take an advantage of my telco provider either to run the application closer to my branch office and not a very common use cases gaming or augmented reality where you take advantage offbeat as close to the end user with a cell phone or the smart devices possible so that they have the good user experience and then to date on experience instaflex so I understand correctly. Telecom like verizon. They need to build essentially data center infrastructure telecom data center center infrastructure to support five G. for their basic cellular customers and in order to get additional value. Oh you add that infrastructure. They are adding the capability to essentially lease out those resources to enterprises that might need similar functionality to that same five G. infrastructure basically they're already building data centers and they're like well we might as well reuse this for edge computing. That's exactly right amazing. So as red hat you basically have an opportunity to help a telecom like horizon that is not historically thought of itself as a cloud provider to the extent that I understand it become a cloud provider. Essentially yes I would not necessarily called provider but mobile computing platform provider. Absolutely the and any of these telcos or service providers in general. It doesn't have to be Telco. Only it can be Internet service provider as well think of comcast or others that is to raise. Is there infrastructure which they need to build to support five G. we can think also of the other use cases when they want to place a device to the end user premise itself. So you can think of Smart Stadium. It's aware you have broadcasting of different games for example you need a server which needs to run there you you need high bandwidth. You need to broadcast it. So what verizon or other Telcos do they place the server there at the stadium at the end user premise and the a US benefits of their infrastructure behind or s in consumer for example. I'm a comcast user. I have my set top box at home. Currently the setup boxes being used for very specific services for example to get my TV streaming on my screen but but in order to use this device to be more generic we start talking about the universal customer premise equipment to turn these very specific use case oriented devices into more generic computing platforms to turn on your home into smart home and connect the Iot devices devices to it and provide different kinds of applications running there. Okay so that's a very different kind of edge computing. It's very different kind of competing but it is still edge computing. Okay Eh. What role would red hat have in that kind of application? The like. I'm comcast I've given you a dumb set top box and now we WANNA turn into like a smart connected home thing. Comcast is still owner of that server or of the device which is running at your home so they need to run some operating operating system. There they need to run some platform which is enabling to run applications on top of that. And guess what the applications are very often containers so we can and think of for example taken to the extreme Kluber not seen at box so real quick the applications running on my dumb comcast sorry to call comcast dumb calling the box. I'm not calling comcast dumb. Those applications that are running on the set top box. They're running in containers. They might some of them might rerunning depending ending on the vendor interesting. Okay sorry continue. So and then you can think of that device to have a marketplace of different applications which can run at that device. So he doesn't have to the only TV streaming you can now have audio streaming or you can now connect your light bulbs and half the LIGHTBULB manager running on top of that box so beat really generic computing server. which can run any kind of applications and then the Internet service provider can give you? This is the marketplace of APPs these vendors who are contributing there you you can deploy your APP or on your up there. And is that to say that coober netease would be useful as essentially a consumer operating system in that environment or maybe open shift is the operating operating system or is it just a lennox just a single node. You don't actually need to distribute system. You're you need new elites distributes have containers running on the same note. But it's just a single all note it is just a single note in our homes so in our home you probably don't want to have free service to have physical H. A. So so you have one single server which is transformed tobback's which is a single box running operating system which is always the core of everything you need need to enable the hardware in some way and then you need some platform or you need something which is orchestrating the workloads on top of that depending on the level of orchestrations auto healing or other things. You need there then. You need difference of services from for brands to run on

Comcast Verizon Telco Industrial Iot Texas Becca Stan Smart Stadium Apple Tobback United States ARI
Edge Computing Platform

Software Engineering Daily

12:11 min | 11 months ago

Edge Computing Platform

"We're GONNA talk about edge computing today and particularly red hat's strategy strategy around that. Give me two recent applications that you have seen of edge computing so to very often reasons. Why the applications WANNA run the etch is latency which means you want to have very fast request response and the second one is reducing bandwidth over the network and those are very to have very often mentioned once? They're way too many other reasons why to do that. And for me. These two reasons are mainly the consequences of what I want to achieve and if I want to improve user experience does are probably the two The latency is probably the first one if I want to reduce the cost probably reducing. The with is another one but then there are other reasons for example risk factors. I want to improve resilient therefore I want to run my applications nations at the edge and have them running in very completely isolated environment so there are really many reasons by the two. Most mentioned wants is definitely latency latency and bandwidth so the type of edge competing. We've had for a pretty long. Time is CDN infrastructure CDN infrastructure is fairly basic. It's if I make a request for an image for example apple that image is GonNa get cashed at the edge and then subsequent requests to that resource will be sent to the edge because the edge can be closer to the user and the edge. Might it'd be a content delivery network. That is pushing out that content to a lot of different locations so that a user news Becca Stan has rapid access. A user in Texas Texas has rapid access the kinds of edge computing. That we WANNA do. Today is very different than that type of simple request response for an image for example. What kinds of computation do we want to do at the edge today? I don't want to repeat myself but it's always it depends ends on the use case and there are many industries which are doing competing for different reasons. All let's take for example Industrial Iot in the production. Shen lines where they are running. They are having multiple sensors in their production lines to control quality production for example of the product the sensors are generating a lot of data data and this data is being analyzed and is being responded is the product quality. Okay can I continue in the direction or do I need to interrupt and just a process. This is kind of application which needs very fast rapid response you cannot really rely on sending that over the network to centralized location do the processing there and then and get the response back so this is very often reason why you want to push the edge computing to location of the IOT industrial but there are also reasons. Why want to centralize? You don't want to do everything only at the edge. There are reasons why you want to do centralization so imagine I have the industrial plans and I have them all over the country but I need to train my machine learning models from different examples and I want to gather those examples from different locations therefore I need to centralize them somewhere then do training model. They're likely in the centralized location and then push out only the train models to do the fast decision making at the edge so this is one of the examples right and that architecture makes a Lotta sense because in order to train the machine learning models you need all the data centralized in a particular place or you need some large subset of the data or you need the new training examples. Whatever the data to train the models takes a lot less space than the actual models that can make a decision that can improve application infrastructure? So we need to start deploying thing these models to the edge now if we talk about the types of CDN infrastructure that has been there for a long time where you're caching an an image and then you can request the image at the CDN layer if we're talking about hosting machine learning models versus hosting basic images. Do we need different different infrastructure to run those machine learning models instead of simple. CDN Type of infrastructure. Absolutely we do and it depends on the context. What kind of application I WANNA run? Therefore the machine learning very often or for example video processing or similar requests we we might need data processing. We need real time kernels we need. GP use use very often to speed up. The processing can reduce the cost of the processing power so the type of the hardware which is enabling the the use cases is specific for the application which needs to run on top of that the CDN is very simple. Use Case as you mentioned you don't really need much of the processing Specific processing processing. But if you need to run for example containerize network function. It has very high requirements on the fast data path and networking or it needs to access the real time kernel which difficult CDN networks don't need Ari talking about machine learning stuff. I've also heard of widespread bread edge competing use cases in the telecom industry. Can you tell me about those applications. So S Forty Telco Day one to do editing edge competing for multiple reasons. I would separate it into two categories first. One is to run their own brighter X.. Networks and for that that is the containerization containerization of their network functions. As you know there was a progress of running network functioning onto bare metal itself with specific hardware than it moved to. VM's and now it's to moving through containers and here the Yukon. We actually saw demo of the proof of concept how to do the five G. fully running on carbonated. That is one of the kind kind of the application. Because at the antenna level you need to have the processing as close to the signal as possible so that you again reduced latency NC and you don't have to push all the data through the network to raise the swap that is the main requirement for five G. or main features of the five G. The second use case for the telcos is to monetize their infrastructure. which they are building for the five and that is to provide mobile edge edge computing platform for all the independent service vendors or other enterprises running their applications? So I can be an enterprise fries which has branch offices and in order to get access from those branch offices to pass processing. I might want to run my applications closer to those branches not necessarily centralized in my data center which might be private cloud one national data center but I might take an advantage of my telco provider either to run the application closer to my branch office and not a very common use cases gaming or augmented reality where you take advantage offbeat as close to the end user with a cell phone or the smart devices possible so that they have the good user experience and then to date on experience instaflex so I understand correctly. Telecom like verizon. They need to build essentially data center infrastructure telecom data center center infrastructure to support five G. for their basic cellular customers and in order to get additional value. Oh you add that infrastructure. They are adding the capability to essentially lease out those resources to enterprises that might need similar functionality to that same five G. infrastructure basically they're already building data centers and they're like well we might as well reuse this for edge computing. That's exactly right amazing. So as red hat you basically have an opportunity to help a telecom like horizon that is not historically thought of itself as a cloud provider to the extent that I understand it become a cloud provider. Essentially yes I would not necessarily called provider but mobile computing platform provider. Absolutely the and any of these telcos or service providers in general. It doesn't have to be Telco. Only it can be Internet service provider as well think of comcast or others that is to raise. Is there infrastructure which they need to build to support five G. we can think also of the other use cases when they want to place a device to the end user premise itself. So you can think of Smart Stadium. It's aware you have broadcasting of different games for example you need a server which needs to run there you you need high bandwidth. You need to broadcast it. So what verizon or other Telcos do they place the server there at the stadium at the end user premise and the a US benefits of their infrastructure behind or s in consumer for example. I'm a comcast user. I have my set top box at home. Currently the setup boxes being used for very specific services for example to get my TV streaming on my screen but but in order to use this device to be more generic we start talking about the universal customer premise equipment to turn these very specific use case oriented devices into more generic computing platforms to turn on your home into smart home and connect the Iot devices devices to it and provide different kinds of applications running there. Okay so that's a very different kind of edge computing. It's very different kind of competing but it is still edge computing. Okay Eh. What role would red hat have in that kind of application? The like. I'm comcast I've given you a dumb set top box and now we WANNA turn into like a smart connected home thing. Comcast is still owner of that server or of the device which is running at your home so they need to run some operating operating system. There they need to run some platform which is enabling to run applications on top of that. And guess what the applications are very often containers so we can and think of for example taken to the extreme Kluber not seen at box so real quick the applications running on my dumb comcast sorry to call comcast dumb calling the box. I'm not calling comcast dumb. Those applications that are running on the set top box. They're running in containers. They might some of them might rerunning depending ending on the vendor interesting. Okay sorry continue. So and then you can think of that device to have a marketplace of different applications which can run at that device. So he doesn't have to the only TV streaming you can now have audio streaming or you can now connect your light bulbs and half the LIGHTBULB manager running on top of that box so beat really generic computing server. which can run any kind of applications and then the Internet service provider can give you? This is the marketplace of APPs these vendors who are contributing there you you can deploy your APP or on your up there. And is that to say that coober netease would be useful as essentially a consumer operating system in that environment or maybe open shift is the operating operating system or is it just a lennox just a single node. You don't actually need to distribute system. You're you need new elites distributes have containers running on the same note. But it's just a single all note it is just a single note in our homes so in our home you probably don't want to have free service to have physical H. A. So so you have one single server which is transformed tobback's which is a single box running operating system which is always the core of everything you need need to enable the hardware in some way and then you need some platform or you need something which is orchestrating the workloads on top of that depending on the level of orchestrations auto healing or other things. You need there then. You need difference of services from for brands to run on

Python packaging landscape in 2020

Talk Python To Me

05:32 min | 1 year ago

Python packaging landscape in 2020

"Chris. Welcome back to talk by thirty. He thinks how's it going. It's been a while it has been awhile how it has been since the summer of two thousand eighteen so not quite two years. But it's definitely been awhile since you were on previously. You're on to talk about. Continuous integration. Continuous delivery rate with Python. And you know that was a really popular episode. Actually I thought the topic would be popular but you came across with all all these little tools and techniques that people just love and so yeah I was really great and I will probably learn more about cool tools and techniques this time around to. Yeah sure it was a a good episodes to kind of get everything up together in a nice little summary Feral so yeah anybody. That's interested is a good one. So let's maybe fill people blend on what you been up to lately day to day. Sure if you are on the software development side but it sounds like you're on the testing and like process making sure stuff works works for the folks around you that they don't build bad software as well so when we recorded that last episode. Yeah I was mostly doing development side but I was in a small all team so I was tied into everything. Qa builds and everything. But since. Then I've transitioned to a different organization and I mostly doing Qa now 's okay tooling which is still involves build stuff but not really developing a product more developing tools to help test and release code. That's cool so you're basically basically in the developer tool space but for internally for your company not like Jimmy rains or the microphone. Like that right right and I've done that in my career. You're a lot actually like it because they can walk over and talk to my customers and tell them that you like this and they're like no it's not okay so fix it. That is super super cool. Feeling I've worked thin small offices where basically the users of the software they were a few offices or little space down and it was like all right what we need for the next week. Is this come back three or four days later. This is what I built. I know you ask for this but I think this part can be automated to. Where do you think about like either like Oh? That's amazing using her. Now what were you doing. Of course you can't do that and so on. It's that quick feedback loop is pretty cool. Yeah it just helps you. Produce something productive for people that will help their productivity. Yeah cool so well that sounds really fun and also related a little bit to what we're going to be talking about now. Yes yes so. I WANNA start really high level with our conversation. 'cause ideas we're going to dig into some of the options for for packaging python applications and I think before we even dig into the details of how we do that. Some of the cool tools out there honestly. I think we have to define what the heck that means. And it's not because we just need to be precise but I think to different people have vastly vastly different expectations and needs some tools. Completely solve that and if your your desire is different it's completely broken like imagine. I want to get my web web APP onto a server to run consistently maybe docker and coober. Netease is the perfect answer. If I have a accounting in application I want to give to accountants running a coup Bernice cluster is not the right answer right like these are really really different. So maybe what are some of the definitions of of what packaging might mean for different people. What's the spectrum out there right so even in the ORG? I'm in right now. We actually have this problem because we have a wide range of tools right so if you're building a bunch of services with sap is to help you deliver something to that's remote or let's call cloud like two people rate that might like you said that's something you might WanNa package as a docker container as as a service running an on a server which is a different deliverable. Then Dan say a double click. This icon here desktop application. That you'd want to deliver if you're one wanting to say create a log viewer. Refer somebody to help them. Process that information right and is completely different from some utility where you just want to provide a quick library or or other people to write more code using your library and all that you'd WanNa deliverable for all of that would be different in and something that makes more sense to the user in the environment that they're in different environments Yup absolutely like. I suspect you're kind of on the border at at work right because because you are working with developers so it's it's probably reasonable to say well there's arrest in point or there is a command line tool you type in the a command line and magic happens so the rest endpoint easy rate. So there's there's this gooey uses some rest. Api and you can track your execution of your tests. For example you can see how things are going. But when you're talking about the actual test you wrote the needs a library for you to access the infrastructure and a bunch of services in that infrastructure that might relate to just stuff. You need an requesting resources for testing or using other integrating with other tooling. That will help you with that rate which is then completely different from some utility. That'll tell me. Give me the list of all the all Mike compute that I have available to run tests on right. Yeah and then that utility needs to run and every developer's machine and then how you distribute that starts getting complicated.

Developer Netease Bernice Cluster Jimmy Rains Mike SAP DAN
Interview with Anil Dash Discussing Web Development

Developer Tea

09:55 min | 1 year ago

Interview with Anil Dash Discussing Web Development

"An ill welcome to the show thanks for having me it's kind of honor I feel like I've I've seen your work for a long time and I think the world is a better place because of what you do but for those who uh of for whatever reason they haven't encountered what you do the things that you are part of can you can give a basic background to the work that you're doing Jack make stuff on the web And so the first thing I became known for his I I started blogging about twenty years ago reading about software in pop culture and whatever else and then you didn't have to be he didn't have big late you consider tries though and then along the way I got to work a number of startups in the early days of social media out build a tool Co. movable type those sort of one of the first big long tools these billy's till the post and Gawker and things like that and then we'll recently a lot of my work has been around trying to enable collaboration creativity coating together so I'm on the board of Stack overflow and Sankara blow actually spun out of call our creed also travel links other products and about three years ago I took over the company and we launched so the latest in that series of products called glitch and it has become a very substantial very interesting community people creating web stuff together in it's both a platform we can code right your browser and instantly ship up to the entire web and also a really great creative community reconsider the People's work remix it in and and clower together and it's been a pretty you know knock on wood every night success and the gates we've had it just lots and lots devs come in and be like Oh this brings back creative feeling Ron cody and so we ended up actually rename the company to glitch and focusing all in on it and since we decided to do that about a year year and go it's really taken off people now built millions of APPs on the and that's one day to day is running the company and getting direct with the community and I'm GonNa ask you a intentionally broad and difficult question about glitch now I'm not sure Who is glitch made four and who is it made not for WHO's not made for I guess is a better with it and I can use English properly today who is it not made for that's a great question so the first thing I thought about is every Hamed a developer tool in the past it had always been this felt like they hadn't pictured guy sitting at a desk with a black turban screening green taxed on and that was the sort of the ethos in the aesthetic in and the mindset of this thing and who's GonNa prove your command line is this is how you became a developer and we actually have a great cohort of people that work that way and they're using this as a tools English but it wasn't that we put them I thought we know we check that box those kinds of developers but for people interestingly on other the opposite ends of the occur from that's the the middle of curve adopters on one enter a real experts who lobby on the web but have had you know any I be in differing views are created toward the tools of us and and I think they've lost some of the the joy the fun of just making stuff and sharing it because it's become very complicated you can't just ship stuff and all of a sudden you're negotiating your deployment environment and also stuff it's just in the way and so those very very experienced coders I think have lost the the fun of the soul of connecting them to creating an the other end are beginners in this can be a kid is learning to read the first line of each to mail it can be experienced over trying API that they haven't used before this sort of back to square one or somebody that doesn't take themselves coder at all maybe they do you know they edit formulas in spreadsheets workers like that the share in common you've got some technical skill but they're a little bit out of their comfort zone a little bit out of the norm in for them listing Louis they had the same needs that expert coder has when they just want to get an idea of their head which is I don't WanNa worry about the overhead and complexity I don't WanNa be distracted by getting something just the basics running I won't be expresses idea I wanNA capture this this little mood of inspiration than I had before evaporates because it's so fragile seen same way as like you know a lot of friends with musicians and all of us have in other guitar two new residents were sitting next to them so that they got it songs in their head they can just capture it and the same thing applies for for making stuff on the web were sometimes you said this fun idea you get out there on glitches as easy as remix it and change it tweet it to be exactly what you need for managed that's in your head we're making everybody that's ever had a moment that you don't be cool thank you know what the world should see this one little idea yeah that's super cool so there's a lot to be said for lowering the barrier to entry both for people who are you know well into the industry now the job and doing fine but also perhaps more importantly for people who are not in the industry who want to try something for the first time but they don't WanNA learn sixteen hours worth of coober netease material exactly right that's not what they're looking for and even like I can't I can't provisional serve on aws again the deploy script but my Gosh I don't want to you just WanNa make something in in back in the day I used to be able to go on Geo cities or journal or whatever the time and just sort of like shop something onto the Internet and it got worse and then it got hard you know and so he's got some difficult than it couldn't just you know try something can just experiment and so having I feel where it's like I said as joyful it's just like tapping out a song piano or something I it's a really Nice feeling yeah I think so so what you've said is this really cool the idea of of a quick idea get it out on paper and you know I think a lot of people may have a misconception about glitch based on our conversation so far that's only made for like these prototyping ideas but there's actually these like the ability to do production level thing right yeah so I mean we run glitch dot com visit south on which is estimated and that's obviously you know Michigan legal for us it's very important out but but either lots of companies where you you're not going to run your air traffic control system on it you're not gonna that's nine you're not gonNA run the Stock Exchange on it sure did that a lot of times or just like I wanted you know we have some old proprietary apple or company and we would like to have it ah you know drop something in the slack so we have a reporting system in I just wanted to set it up but I'm the one the president the office who has permission to launch production apt to do all the I'm stopping I don't WanNa ask the IT guys to do it for me in the third quarter of next year and so maybe I can just put something together and I think that that's the taste but I think it's true at home or somebody who's like I just wanted to you know put together a website to organize early neighborhood wants to clean up the park the playground I want to have to do a facebook group for it and there's a lot of different ways of capturing that impulse but their relapse and they really run and they there full stack and they are us any framework and toolkit API I do think a lot of times we start with that in Nicole were all of like in the technical bonafides and not so much the creative impulses destined care about the most is you actually figure out any tech you need to or any you will learn a teenage learn if there is an idea that just animates you so much that you need to create it in the world and Sony learn that way to begin with or at least started that way and And we wanted to sort of enable that because the expert coders are very well tended to there are tons of resource capabilities but the people who are like just need to get this idea out there and then maybe they got some experience coating or maybe you tone but will handle all that other complexity offer you WanNa go if you want to run the large scale production side like you are that's great that's all in there you don't have to think about that we start right yeah I think there's there's an interesting discussion here that kind of merges when when you start thinking about you know that seam between and I'm back when I was an agent he works especially I saw the same pronounce Stephen Moore but it's between the kind of creative people and technically adept people Zainur and develop per prototype kind of people where the designers kind of quarantines to this area where you know they might be able to make a motion prototypes they may even be able to work with HD on Java scrip- right but there's no way that that stuff is GonNa make it over that seem is not going to get into the quote real APP yet right and it got harder to because we introduce the frameworks of the toolkits build scripts that you couldn't just tweet it yourself now you you had have this knowledge

Jack Sixteen Hours Twenty Years Three Years One Day
"coober netease" Discussed on Software Engineering Daily

Software Engineering Daily

01:48 min | 2 years ago

"coober netease" Discussed on Software Engineering Daily

"That appear to directly compete with one another and that becomes in some ways a fascinating story. I was doing a lot of coverage of the container orchestration system wars. There was this period of time where Docker had reached market acceptance and people were looking for what is the best solution for managing all of my Docker containers is it going to be Mesa sphere. Is it going to be Docker swarm is it going to be Hashi Corp? No mad, and then eventually Cooper Netease came out, and it it reached enough saturation or market share or was marketed. Well enough that people said, okay. This is what we're settling on and AWS head and placed a strong bet on any of the particular orchestrators they had placed a bet on their own proprietary orchestrated the CS one. And then when Kuban has got accepted, there was a sense that it impacted the strategy of AWS how did coober Netease. Impact the strategy of AWS from my mind. I think you you nailed it in that there were a lot of different competing standards, more or less and when coober Netease emerged as a more or less defacto standard across the board. It feels again, I have no inside information on this that it sort of caught AWS flat-footed, they wound up releasing e ks or the AWS elastic container service for Cooper, Netease. Apparent they could pay by the syllable for that one. And it was very much a one dot product when it launched it took over fifteen minutes to provision a cluster. It was not at all clear what permissions at needed. So you needed to grant it rolls that were incredibly broadly scoped it didn't wind up doing logging appropriately. The horizontal pot.

coober Netease AWS Cooper Netease Docker Hashi Corp Mesa sphere Kuban Cooper fifteen minutes
"coober netease" Discussed on Software Engineering Daily

Software Engineering Daily

01:41 min | 2 years ago

"coober netease" Discussed on Software Engineering Daily

"How do I do monitoring? How do I do service discovery between these applications and the way that a lot of folks initially approached this problem is that they make it? The business of the application to figure that out. So every application has bits of this code tucked in to try and do this. And it doesn't really scale if you want to change the way that service discovery happens you need to update every application within your ecosystem. And if you're a running at large scales that could be hundreds thousands of Microsoft is that you need to to update. And so it's DO is an open source project that was formed that built on top of the primitives at coober Netease provides and tries to solve these challenges of trying to make it easier to glue together Microsoft services, so that application developers can be even more one one more step removed from the the complexity of how the application runs, and they can focus more on application code. And then K native is a play in the server less space, which is taking things a step further and saying just give me your application that you. Your code that you want to run as a container, and you know, this system will figure out how to run it for you. You don't have to worry about Cooper, Netease. You don't have to worry about how things interact with each other. We'll make it even more simple for you. And so I am really excited to see where these projects are going to go in the future and see adoption grow there and see how it they're solving problems for customers in terms of just let don't worry about the infrastructure focus on applications saw deli. Thank of software engineering daily. Thank you very much for having me. It was a pleasure..

coober Netease Microsoft Cooper
"coober netease" Discussed on Software Engineering Daily

Software Engineering Daily

03:23 min | 2 years ago

"coober netease" Discussed on Software Engineering Daily

"There are so many different ways that people deploy coober netties. The cloud provider way is often through a managed service like Amazon has e ks. That's their elastic coober. Nettie service, Google has a similar thing. G K E, Azure, has a similar thing. But then you could also just spin up EC two instances, you could run coober Netease across EC two instances, you could use like normal coober Netease vanilla coober Netease. That is not at all tied into Amazon E ks and you could run Kuban editor over you wanted to on top of those EC two instances, you could also run coober netties on your your on Prem servers. If you've got an on Prem installation. Or if you if you're set up in a way that you can't be entirely on the cloud than you know. Maybe you're you're running Kuban natives on your own machines. In addition to that, there are these layers on top of kube. Netease. There are these management layers like platform nine where you work. That's a management layer that you can operate your infrastructure more easily or that sits on top of coober Netease. So maybe you're using Netease, maybe using coober natives with a management layer like platform nine maybe using Kuban Netease in the cloud. Among all these different use cases, who are the kinds of people, and who are the kinds of users the type of customers the types of enterprises that would want to deploy a server 'less on coober Netease, framework like fishing. So we definitely see a lot of on Prem us to start with and this bar, partly because you know, we at from nine since we have a management layer for coup Bonetti's for on Prem users. This is like a way better than managing it yourself. So it gives you all the benefits of g k or r e s with your physical. So so these folks are looking for example at there. Infrastructure investments and saying how to use Martin as a fabrication development on the stuff that I've already bought, and then maybe died do that infrastructure not just because of investment, but because storage, for example, and they wanted to be able to run functions on them. So we definitely see entre Musa's going for fishing on their communities clusters and the other class a Fuser's. I see and these are almost discharged sect are folks for whom the Vida's public cloud service offerings are too limited in some veiled another. So this can be either the total Runtime you spoke a bit about infinite cloud capacity in the beginning. But a lot of people don't reach the limit. And so can feel that it's infinite, but you want it will quote gets big enough. His start hitting rate limits which are different for radios. Clouds does a really nice academy study on on Goldstar, ten performance of the big city public cloud server la- systems as. Are your booklet demand goes up, and they all sunk Shen vetted efficiently as workloads go up. And so as you start pushing against those limits, so there's a Runtime there is the rate. Limiting that is the simply the idea that you may want to package your own Yonne dependencies that made each, you know, size limits of Lambda until on but Vida's limits people reach, and they kind of go to go to fishing on carbonates and.

coober Netease coober netties Kuban Netease Kuban Vida Amazon Prem Bonetti Nettie Google entre Musa Goldstar Shen editor Martin
"coober netease" Discussed on Software Engineering Daily

Software Engineering Daily

03:24 min | 2 years ago

"coober netease" Discussed on Software Engineering Daily

"Talked about the architecture of a service framework built on top of coober Netease. So I want to review some of the stuff that we talked about last time. But for the most part, we'll talk about newer things. Just catch some people up. What's your current definition of that word service? I see we're going straight to the heart questions, you know, to be honest. I think just like the term cloud. It has started losing meaning. But that said it is both bit oven. Asp additional dumb. It's the idea that you can deal with applications without dealing with service. Right. That's the most basic idea and it ablaze in. Nation of this is is obviously Lambda, but you know, they then expanded it to be more to be other services. And I think like there's been this sort of what is FAZ, and what is several functions as a service, sources sober less. And I think if you look at the history of application development platforms a lot of the cut in definitions of surveys can be applied to platform said existed awhile ago, but this is sort of a newer take on for example, Baz or Google app engine. A lot of these things are by in many ways Serra's item reading a tweet from someone which was half jokingly saying that server less means somebody else's Cooper nineties cluster. Does it somebody? That's actually pretty good definition. Exactly if somebody else's managing Harvard and servers, so you and giving you any kind of API at the dip lie and manage services on it. That is in some sense, several less sorry end as one more little point, which is that another thing that's become died to so. Over less, but isn't really in the term is the idea of paying for what you use. And conversely and in the private clouds face being having resource utilization that's very closely proportional to actually use it, right? That resource utilization thing, I think that's going to be important in in this conversation because the conversations I usually have around service also tie in with conversations around containers contain orchestration, the deployment of containers. So when I'm talking to cloud providers, for example, about containers. I had a show recently about the container offerings on AWS. And they have this range of things they have you can obviously deploy on coober Netease. You can deploy on their e c s which is sort of like deploying on their managed Cooper Netease. They have standalone container instances, they have this Amazon far gate thing where you can just deploy a a long lived container without having a man. Cooper, Netease cluster. And then they also have the AWS Lambda offering which is quote server less, but it's basically I deploy function. And when that function is going to execute it spins up a container and then executes that function on the container and the container spins down, and I don't have to really care about any of this just gets executed for me. So we have a wide variety of ways that we could deploy a function that we could deploy a service against this infrastructure in varies. You know, we're going to get the same pretty much the same thing out of it. We're gonna get an execution of that function. Whether it's deployed on a coup, Netease cluster, or it's deployed on a service function. So what's the difference? What are we looking at here?.

coober Netease Netease Cooper Netease Cooper AWS Baz Serra Amazon
"coober netease" Discussed on Ruby on Rails Podcast

Ruby on Rails Podcast

04:28 min | 2 years ago

"coober netease" Discussed on Ruby on Rails Podcast

"Netease. Than what Lincou de will give you is extremely powerful telemetry and reliability and also security kind of mechanics without you having to change your code because way, it works is all those proxies get inserted alongside your code. And it doesn't matter whether you using ruby or not. But all of your calls will go through these little lightweight Lincoln, d proxies and will measure the success rate of everything. And will you know retry when things are going wrong, and we'll do circuit bringing we'll just add all these kind of operational layers. And so as a result, your Apfel stay up, you know, even if they're a little partial failures escalate to take down the entire app, you'll have visibility excuse me. You'll have lots of disability into everything that's happening. Whole bunch of benefits. We can give to you without you haven't actually change your code. That makes sense. And so, you know, a lot of you know, ruby on route doubts are holding their wearing a lot of hats. So they're doing everything from you acts to front end back end, including DevOps. So it sounds really like having weaker d in your toolbox as ruby on rails developer. You're just gonna get a lot more insight as to as you're deploying that application out for free. Really like, I mean, it just sounds like it's pretty easy to set up and really get into -ployed out. So I mean, it looks like a really fabulous product for us. Like, we just have a lot of empathy for for developers. Who are you know, often kind of putting these situations like, okay, we're using medics now like everyone got on board, and, you know, make things work and and He's kind of kind like. of like, well, gosh, you know, that founds really easy. But when you actually deploy, you know, five services or ten nevermind hundred handful you run into issues really really quickly and the want wanna be able to to help. Excellent. So there as you mentioned there are a lot of competitors in the container space. So why did you decide to commit sick nineties? Yeah. I think that that that was pretty easy. Well, so so I I'll say coober Netease is an area of focus, but we do support other platforms. And there's two versions of Lincoln d and kind of like a slightly different story between those two versions. But most of the adoption that we have seen with Lincoln has been in the context of these. And so for us, it's not like a like, a moral choice or anything. We're just going is just the data driven choice. We're going to where people are using the most. Okay. And so what does it mean that Lincoln d is cloud native computing foundation project? Yeah. That's a good question. So the the cloud computing foundation or the CNC F is a it's kind of like the Apache offer foundation. There's it's one of these kind of open source hosting foundations. It is the foundation that hosts Cooper Netease and permit Theus and a bunch of other cloud native projects in the space in addition to Lincoln D, And so for us it just felt like the right home. You know, we are a boy it is a startup, but the project is open source project that were building that were sponsoring has to be a first class open source citizen. Right. It can't be like we hold back. These certain features, and you have to pay money for this because like this which Indies and production like this has got to be a full full-fledged fully open source project. And so for us having a home, like the f- has been valuable just in in kind of as a way of showing the world, look, this is a neutral party, and they own the IP and they own the trademark, and they own the code and buoyant is a, you know, obviously, we we have heavily invested in Lincoln d because we're spending all of our precious life juices. Lingus thing. But it is a cloud native computing project, and it's not a point project. And I think that's a big that's a big difference for for folks. Want to adopt open source? They're always a little wary of like, okay. It's open source in name only, which can have could go away. Or you know, I mean that that happens and just by being a CNC f project? I I would see that develop for like this projects here to stay this project has support this project part of an ecosystem, I think there's are all positive things yet. Yeah..

Apache offer foundation Lincoln d Lincoln Netease. Cooper Netease Lincou de developer Lingus Theus
"coober netease" Discussed on Software Engineering Daily

Software Engineering Daily

02:04 min | 2 years ago

"coober netease" Discussed on Software Engineering Daily

"These are obviously regulated industries, these industries that have a very high bar on compliance and also security. They have a lot of customer data that's very, very business critical. So I think three years ago there was there was much concern about using containers as a technology for security conscious enterprises. There's been a lot of progress on the technical front in in the realm of security container, security, container, security, infrastructure, security. You know, Runtime security in just security constructs in coober Netease overall have made tremendous progress in the last three years. And I think that is. As evidenced by the fact that there are now so many of the financial institutions in so many of the regulated industries that are using coober Netease in production. In fact, so in, I wouldn't say that, you know it is being used at a very large scale. The entire companies using who were not as there are some, but I think it's still on the way on the way to mainstream and massive adoption in these regulated in highly security conscious industries. But it certainly being used in production, which means that it's the base capabilities are starting to be there. Some of the base capabilities and these were mostly all introduced more than a year ago. Role based access control, you know is was stable in the one point, eight release and for context we're now working on the one point, twelve release. We just we just finished the one point eleven release last week. So this is a while ago. Now that role based access control became stable, and it was available for a year or more before that, but that basically allows you to set granular controls on who can. Do what in your cluster and the network policy, which is an l. seven. Sorry is in l. four construct for which applications which pods can talk to each other and being able to set that at a policy level on an l four basic capability. Again, I think that enterprises need combining that with l. seven policy controls which are now offered through Ichijo is is an add on on top of Cooper Netease that provides not only service to service authentication and this type of l..

coober Netease Cooper Netease Ichijo three years
"coober netease" Discussed on Software Engineering Daily

Software Engineering Daily

02:04 min | 2 years ago

"coober netease" Discussed on Software Engineering Daily

"These are obviously regulated industries, these industries that have a very high bar on compliance and also security. They have a lot of customer data that's very, very business critical. So I think three years ago there was there was much concern about using containers as a technology for security conscious enterprises. There's been a lot of progress on the technical front in in the realm of security container, security, container, security, infrastructure, security. You know, Runtime security in just security constructs in coober Netease overall have made tremendous progress in the last three years. And I think that is. As evidenced by the fact that there are now so many of the financial institutions in so many of the regulated industries that are using coober Netease in production. In fact, so in, I wouldn't say that, you know it is being used at a very large scale. The entire companies using who were not as there are some, but I think it's still on the way on the way to mainstream and massive adoption in these regulated in highly security conscious industries. But it certainly being used in production, which means that it's the base capabilities are starting to be there. Some of the base capabilities and these were mostly all introduced more than a year ago. Role based access control, you know is was stable in the one point, eight release and for context we're now working on the one point, twelve release. We just we just finished the one point eleven release last week. So this is a while ago. Now that role based access control became stable, and it was available for a year or more before that, but that basically allows you to set granular controls on who can. Do what in your cluster and the network policy, which is an l. seven. Sorry is in l. four construct for which applications which pods can talk to each other and being able to set that at a policy level on an l four basic capability. Again, I think that enterprises need combining that with l. seven policy controls which are now offered through Ichijo is is an add on on top of Cooper Netease that provides not only service to service authentication and this type of l..

coober Netease Cooper Netease Ichijo three years
"coober netease" Discussed on Software Engineering Daily

Software Engineering Daily

01:31 min | 2 years ago

"coober netease" Discussed on Software Engineering Daily

"As your container service simplifies the deployment management and operations of coober netease eliminate the complicated planning and deployment of fully orchestrated containerized applications with cooper netease you can quickly provision clusters to be up and running in no time while simplifying your monitoring and cluster management through auto upgrades and a built in operations console avoid being locked into any one vendor or resource you can continue to work with the tools that you already know so just helm and move applications to any coober netease deployment integrate with your choice of container registry including azure container registry also quickly and efficiently scale to maximize your resource utilization without having to take your applications offline isolate your application from infrastructure failures and transparently scale the underlying infrastructure to meet growing demands all while increasing the security reliability and availability of critical business workloads with azure to learn more about azure container service and other azure services as well as receive a free book by brendon burns goto aka dot ms slash s e daily brendon burns is the creator of coober netease and his e book is about some of the distributed systems design lessons that he has learned building kuban eddie's that e book is available at aka dot ms slash s daily.

brendon burns kuban eddie
"coober netease" Discussed on Software Engineering Daily

Software Engineering Daily

01:31 min | 2 years ago

"coober netease" Discussed on Software Engineering Daily

"As your container service simplifies the deployment management and operations of coober netease eliminate the complicated planning and deployment of fully orchestrated containerized applications with cooper netease you can quickly provision clusters to be up and running in no time while simplifying your monitoring and cluster management through auto upgrades and a built in operations console avoid being locked into any one vendor or resource you can continue to work with the tools that you already know so just helm and move applications to any coober netease deployment integrate with your choice of container registry including azure container registry also quickly and efficiently scale to maximize your resource utilization without having to take your applications offline isolate your application from infrastructure failures and transparently scale the underlying infrastructure to meet growing demands all while increasing the security reliability and availability of critical business workloads with azure to learn more about azure container service and other azure services as well as receive a free book by brendon burns goto aka dot ms slash s e daily brendon burns is the creator of coober netease and his e book is about some of the distributed systems design lessons that he has learned building kuban eddie's that e book is available at aka dot ms slash s daily.

brendon burns kuban eddie
"coober netease" Discussed on Software Engineering Daily

Software Engineering Daily

02:02 min | 2 years ago

"coober netease" Discussed on Software Engineering Daily

"Kind of like templates of of expected behavior for very very services yet hopefully some of the vendors do or somebody has them someday so on each node the coober netease model is there's several pods several pods fit into a node in their containers within each of these pods and if we're trying to detect a militias behavior we are going to look at system calls when you look at the system calls that the containers on a given node are making what for the familiar with lenox what is a system call can you explain that term sure system call as a call a particular process would make to the colonel to do something like says a particular function is something like a like a like a memory access something like like dumping dumping remarks will be be reflected in system calls and why is it useful to to be looking system calls from a security standpoint from a security standpoint system calls are the one of the main way as that a container would try to do anything so what i mean by that is if a container can't do something in memory in its own application and he's asked the colonel for you know more memory more resources to connect to another container to do anything all of that has to go through the kernels and so a system call is going to be a large fraction of what we see the container doing won't be reflected in the system calls of the containers is doing in some of the security solutions that people deployed to coober netease you'll have a model where one of the pods on the node is a management container explain what a management container is yeah so a demon center posed containers that container that you would run on on every node running in promote would have the ability for example to look at another container system calls management container in in a typical model we're talking about a a runtime security solution is another container that would look at the output of that of that privilege container or that perl module and say hey you know these calls look anomalous so when we're talking about having an no model that you're running on your containers and to look for now.

"coober netease" Discussed on Software Engineering Daily

Software Engineering Daily

02:02 min | 2 years ago

"coober netease" Discussed on Software Engineering Daily

"Kind of like templates of of expected behavior for very very services yet hopefully some of the vendors do or somebody has them someday so on each node the coober netease model is there's several pods several pods fit into a node in their containers within each of these pods and if we're trying to detect a militias behavior we are going to look at system calls when you look at the system calls that the containers on a given node are making what for the familiar with lenox what is a system call can you explain that term sure system call as a call a particular process would make to the colonel to do something like says a particular function is something like a like a like a memory access something like like dumping dumping remarks will be be reflected in system calls and why is it useful to to be looking system calls from a security standpoint from a security standpoint system calls are the one of the main way as that a container would try to do anything so what i mean by that is if a container can't do something in memory in its own application and he's asked the colonel for you know more memory more resources to connect to another container to do anything all of that has to go through the kernels and so a system call is going to be a large fraction of what we see the container doing won't be reflected in the system calls of the containers is doing in some of the security solutions that people deployed to coober netease you'll have a model where one of the pods on the node is a management container explain what a management container is yeah so a demon center posed containers that container that you would run on on every node running in promote would have the ability for example to look at another container system calls management container in in a typical model we're talking about a a runtime security solution is another container that would look at the output of that of that privilege container or that perl module and say hey you know these calls look anomalous so when we're talking about having an no model that you're running on your containers and to look for now.

"coober netease" Discussed on Google Cloud Platform Podcast

Google Cloud Platform Podcast

01:45 min | 2 years ago

"coober netease" Discussed on Google Cloud Platform Podcast

"Hi and welcome to episode number one hundred twenty four of the weekly google cloud platform podcast i'm ach mandal and i'm here with my colleague as always melanie work hello melanie how you doing today doing okay how're you doing i'm doing all right coughing dot com so coughing will probably happen all year for now exactly just me laugh and everything will be fine this mark mark now operates at coughing level exactly but yeah this week super excited we have the vp of infrastructure for google cloud platform eric brewer joining us today yes it was fun talking with erik he has a wide variety of experiences and background and that he was one of the key players bringing about cuba nettie yeah actually yeah which was super cool it was but before we get into the interview as always we ever coatings of the week and we have a question of the week and this week's question is if i want to visualize the network traffic between pods services within my coober netease cluster is there an easy way to do this is their spoiler alert so but before we were talking about that and that'll be at the end cool things of the week so you may have heard of next next is the big cloud event that we have the big cloud conference that we have on google cloud and it is officially july twenty four twenty six tickets now available we'll have a link check it out and then i know we also have some satellite cloud next events that are coming up i guess it's best to say next or is it cloud next suspect marketing i'll get me later anyway so the other events that are coming up is in london october tenth and eleventh and then also tokyo the nineteenth and twentieth can you register for those dates just sign up sign up and you'll get updates on stuff.

vp eric brewer erik google cuba tokyo
"coober netease" Discussed on Software Engineering Daily

Software Engineering Daily

01:34 min | 2 years ago

"coober netease" Discussed on Software Engineering Daily

"About this from inception you need to be designing it in that you need to have these high level kpi's these golden signals need to be at the top of what you're monitoring and then you should be familiar with them right like they're not something you should not know should know how all those systems work and that's probably i mean i think that's the same advice i'd give anyone it's not specific to stripe i i think the best advice wouldn't be right wherever possible you should be doing all of those things and i think you'll have a really good experience if that's the way you build stuff out all right cory watson thanks for coming on software engineer daily no problem thanks for having me again go cd is a continuous delivery tool created by thought works it's open source and free to use and go cd has all the features you need for continuous delivery model your deployment pipelines without installing any plug ins use the value stream map to visualize your into end workflow and if you use cooper netease go cd is a natural fit to add continuous delivery to your project with go cd running on coober netease you define your build workflow and let go cd provisions and scale your infrastructure on the fly go cd agents use coober netease to scale as needed checkout go cd dot org slash s daily and learn about how you can get started go cd was built with the learnings of the thought works engineering team who have talked about building the product in previous episodes of software engineering daily it's great to see the continued progress on goes cd with the.

software engineer coober netease cory watson
"coober netease" Discussed on Software Engineering Daily

Software Engineering Daily

01:34 min | 2 years ago

"coober netease" Discussed on Software Engineering Daily

"About this from inception you need to be designing it in that you need to have these high level kpi's these golden signals need to be at the top of what you're monitoring and then you should be familiar with them right like they're not something you should not know should know how all those systems work and that's probably i mean i think that's the same advice i'd give anyone it's not specific to stripe i i think the best advice wouldn't be right wherever possible you should be doing all of those things and i think you'll have a really good experience if that's the way you build stuff out all right cory watson thanks for coming on software engineer daily no problem thanks for having me again go cd is a continuous delivery tool created by thought works it's open source and free to use and go cd has all the features you need for continuous delivery model your deployment pipelines without installing any plug ins use the value stream map to visualize your into end workflow and if you use cooper netease go cd is a natural fit to add continuous delivery to your project with go cd running on coober netease you define your build workflow and let go cd provisions and scale your infrastructure on the fly go cd agents use coober netease to scale as needed checkout go cd dot org slash s daily and learn about how you can get started go cd was built with the learnings of the thought works engineering team who have talked about building the product in previous episodes of software engineering daily it's great to see the continued progress on goes cd with the.

software engineer coober netease cory watson
"coober netease" Discussed on Software Engineering Daily

Software Engineering Daily

02:02 min | 2 years ago

"coober netease" Discussed on Software Engineering Daily

"Deleted this pods and i need to shut down this pod i mean it does some other things as far as mounting and configure apps and volumes and things of that nature but it's really the workhorse on the note it's the thing that does the most work everything else is kind of just changing state inside coober netease so if we think about like say a replication controller a replica set its job is just to monitor replicas set objects and then see how many pods match those labels and then create a new one or delete one based on that so they're really just kind of creating and modifying objects which within the kind of the kuban netease api server so since you joined microsoft you started working on the virtual cuba it project in this allows nodes within the couva netease cluster to be backed by services outside of that cooper netease cluster so rather than using just a node whether than interfacing with just a note or a virtual machine at the lowest level you could potentially interface with server service functions or with ephemeral container instances like the aws fargo or as your container instances explain the motivation for the virtual culet there's actually it's interesting so we have a chaos which is our managed communities offering where we manage the control plane for you and we're not responsible for the team you know myself included that created virtual keble kind of aren't responsible for the initial idea of doing this i'm not sure who triggered it but brendon burns wrote the first implementation of in type script called the connector and it did the same thing but what kind of myself on the team i worked with are responsible for this kind of this concept of making its own project where it's modular were anybody could kind of plug in these interfaces and things like that and writing it in.

brendon burns netease microsoft
"coober netease" Discussed on Software Engineering Daily

Software Engineering Daily

02:23 min | 2 years ago

"coober netease" Discussed on Software Engineering Daily

"Go cd is a continuous delivery tool created by thought works it's open source and free to use and go cd has all the features you need for continuous delivery model your deployment pipelines without installing any plug ins use the value stream map to visualize your into end workflow and if you use cooper netease go cd is a natural fit to add continuous delivery to your project with go cd running on cooper netease you define your build workflow and let go cd provisions and scale your infrastructure on the fly go cd agents use coober netease to scale as needed checkout go cd dot org slash se daily and learn about how you can get started go cd was built with the learnings of the thought works engineering team who have talked about building the product in previous episodes of software engineering daily and it's great to see the continued progress on kgo cd with the new kuban eh these integrations you can check it out for yourself at go cd dot org slash se daily and thank you so much to thought works for being a longtime sponsor of software engineering daily we're proud to have thought works and go cd as sponsors of the show so just if i can give a crack explaining re explaining what you just said so you've got these smart contracts that are written in perhaps a language like solidity solidity compiles down to edm byte code and each of those vm bite code instructions has a gas price associated with gas price the term to use their for an e gas prices societas with each op code right so there's a gas price socio with each op code which means that your solidity smart contract is gonna compile down to a collection of these vm by codes and the and the the total price of the contract is going to be the some of those e vm instructions and then when somebody wants to call that smart contract because they're going to have to call the smart contract on every full node that is on the theory and blockchain because every full note is running that smart contract and every full note is going to have to execute that smart contract to maintain the same state.

coober netease kuban
"coober netease" Discussed on Security Now

Security Now

01:39 min | 2 years ago

"coober netease" Discussed on Security Now

"Auto scaling means that as you use your coober netease engine and you get demand because you design the next best thing to sliced bread it'll scale right up no problem and here's something really nice at a lot of other providers don't do it also scaled down in the quiet periods so you spend less money google is the only hyper scale cloud provider to offer an sla for clusters running on coober nannies it's also backed by experts on google security and reliability engineering team and we know how good they are it's hip and pci compliant and you're never locked in because of course it's coober netease it's open so with coburn netease engineer free to take your workloads out and run them anywhere coober nannies is supported learn more about the all the wonderful things that can happen when you start using coburn netease engine developers go to g dot co slash get g k e today g dot co slash get g k e for google google coober netease engine if why if my twenty five year old self could see me doing an ad for something called goober google kober nettie i would've said okay you've lost your marbles time for you to retire google coober netease engine it's real and it's yours at g dot co slash get g k e today aig pay funny but nat but it's you know now it's all yeah google kuban as engine of course yeah i know what you're talking about.

google engineer coburn netease twenty five year