6 Burst results for "Kuban Attis"

"kuban attis" Discussed on Data Engineering Podcast

Data Engineering Podcast

02:09 min | 9 months ago

"kuban attis" Discussed on Data Engineering Podcast

"Hello and welcome to the data engineering. Podcast the show about modern data management. Have you ever had to develop ad hoc solutions for security privacy and compliance requirements. Are you spending too much of your engineering resources. On creating database views configuring database permissions and manually granting and revoking access to sensitive data. Satori has built the first data ops platform that streamlines data access and security so tories. Data cops automates data access controls permissions and masking for all major data platforms such as snowflake redshift and sequel server and even delegates data access management to business users. Helping you move your organization from defaults data access to need to know access to data engineering. Podcast dot com slash satori. That's sat r. Today and get a five thousand dollar credit for your next satori subscription when you're ready to build your next pipeline and wanted test out the project you hear about on the show you need somewhere to deploy it so check out. Our friends over at lynn owed for their managed kuban attis platform. It's now even easier to deploy and scale your workflows or try out. The latest helm charts from tools like pulsar package herrmann dragster with simple pricing fast. Networking object storage and worldwide data centers. You got everything you need to run a bulletproof data platform. Good data engineering. Podcast dot com slash leno. Today that's l. i n. Od and get a one hundred dollars. Credit to try out of kuban eddie's cluster of your own and don't forget to thank them for their continued support of this show. Your host is tobias macy and today i'm interviewing vikrant do bay about q. Book into their q. Lake project for building pipelines for your data lake house entirely and sequel so the crowd. Can you start introducing yourself. My name is club. I hit engineering at kill book. Kill the business analogy startup. And i'm very excited to be here. And do you remember how you first got. Involved in data management.

"kuban attis" Discussed on Software Engineering Daily

Software Engineering Daily

05:31 min | 1 year ago

"kuban attis" Discussed on Software Engineering Daily

"Could move workloads. Sure there was the dream of kuban. Attis multi cloud single. Api workloads across multiple clouds. No one's really doing that yet. And if you are like please do a conference. I think everyone would want to see it. The fact that people don't even do conference talks about that solution kind of proves to me. No one's even really doing it because it's just a hard problem but even if you could easily do that easily run a workload in any cloud anywhere. You still have a data problem right. You have a data a network problem. And that's why places like. Aws they make the data so easy the data in s. three as that central world around all these other services because the more you put in three the less likely you're galil aws. I almost believe that that's one of their signals of knowing you know people are locked in. There is like the more data you had like. If you're gonna move its are you gonna move expedites out of like unlikely right. You're just gonna leave your workloads there. Some people do and they can. It's atypical usually. It's one of those that were data goes as we need it but most of it's never accessed again. Think of how many pictures people take and store and various services that are using s threes. Their storage for that and never actually access those things again. Like how many pictures taken where you take the picture you access at once and then it sits there forever and rods. Because you don't need to know what your dinner receipt was back in two thousand fourteen. But they can't get rid of it because you kind of actually might need to present that at some point in case of an audit or something. So how do you solve those problems. Well you wind up finding ways to do this at scale massively. So much of that is almost certainly dead stock slash data. That will never be touched again. But god help them. If one day it goes on available. Yeah i mean that was the dream of the startup. I was that was sony. Email archiving and like you're never going to probably need that email again until you need it and when you need it like it's probably because you have lawyers asking you for it right so having a place that you can put an object like an email or bundle of emails and not have to think about it for a really long time is so compelling like who wouldn't want something like that just dump your data here and maybe i'll do something with it later and navy. Some proc manager comes along is like oh god we can do some analytics all this data we have and because it's all there right now you can do stuff with it. I'm really looking forward to seeing what the future cloud holds. The challenges though is that there are over fifty billion dollars a year now in run rate and bat is an awful lot of revenue pouring in there but they got there by reaching out specifically to developers and infrastructure people to wind up driving cloud adoption. The next fifty billion is not gonna come from those folks. It's gonna come from a lot of the blue chip enterprise style companies that are migrating in various directions. And that's a challenge that historically aws has done a relatively poor job of learning to speak to those businesses in ways that resonate talking to the it ops person who is not going to learn cloud formation. They're going to do things in the console for example is a bit of a stretch for them in many cultural respects. You can't do bottom up adoption the same way anymore because it turns out neither developers nor operations folks in. It are empowered to sign a fifty million dollar. Cloud deal the second time because the first time they did. They were fired and prosecuted. Yeah i mean amazon. They're not known for that. They're not known for being able to speak to. We'll call like the old guard enterprise. There's a lot of data centers still out there. There's a lot of workloads that are still in those data centers and you ve. Companies like oracle and microsoft. That are odyssey this way. Better at telling that story to those people everyone thinks. I'm kidding when i say this about microsoft but the honest truth is is that they have forty years of experience apologizing for software failures and that is exactly what you need to do in the cloud because things break all the time and at scale that is what happens and you never get away from that. So you best be able to articulate that in a language and a context that you're angry customers understand and appreciate and microsoft is the undisputed expert in that space. Yeah i mean. Microsoft has the advantage in the enterprise. We've been in the enterprise for you know thirty plus years right. It's so easy for them. They're already there with exchange server and all other components that tie into it with active directory. They know how to talk to those. It folks and they're already involved in those engagements whereas amazon amazon is not selling an email service to these companies. They're not selling domain controllers services and exchange services and file. Services and share point microsoft. Already they're already have their foot in the door. So feel like amazon has a big hill to climb in order to even meet them at their level right. They have to go way above to get to those. You know old guard. It ops folks that are dealing with exchange servers and share point service shares. And things like that and sure amazon has a whole slew of things that you could use. That can kind of replicate that service. But like if. I'm an exchange admin i kind of want hosted exchange. I'm going to go to microsoft to get my hosted exchange. I wouldn't even think of amazon for that service. Even though they could probably provide a pretty similar offering and one of the biggest problems now is there fifteen different services that.

amazon microsoft Microsoft forty years thirty plus years oracle fifty million dollar second time fifteen different services first time Attis sony one over fifty billion dollars a y two thousand fourteen kuban three one of the biggest problems s. three single
"kuban attis" Discussed on Software Engineering Daily

Software Engineering Daily

05:16 min | 1 year ago

"kuban attis" Discussed on Software Engineering Daily

"They'd spent five years learning operationally by getting it wrong and learning from those mistakes. Everyone else was coming from behind. Had an awful challenge to be it turns out. The cloud services are super sticky. Yeah absolutely once you're in like moving off is not something that you're really likely to do. Moving data it's just too expensive. Even if you could move workloads. Sure there was the dream of kuban. Attis multi cloud single. Api workloads across multiple clouds. No one's really doing that yet. And if you are like please do a conference. I think everyone would want to see it. The fact that people don't even do conference talks about that solution kind of proves to me. No one's even really doing it because it's just a hard problem but even if you could easily do that easily run a workload in any cloud anywhere. You still have a data problem right. You have a data network problem. And that's why places like. Aws they make the data so easy the data in s. three as that central world around all these other services because the more you put into s. three the less likely you're galil aws. I almost believe that that's one of their signals of knowing you know people are locked in. There is like the more data you had like. If you're gonna move peta bites are you gonna move expedites out of serie like unlikely right. You're just gonna leave your workloads there. Some people do and they can. It's atypical usually. It's one of those that were data goes as we need it but most of it's never accessed again. Think of how many pictures people take and store and various services that are using s threes. Their storage for that and never actually access those things again. Like how many pictures taken where you take the picture you access at once and then it sits there forever and rods. Because you don't need to know what your dinner receipt was back in two thousand fourteen. But they can't get rid of it because you kind of actually might need to present that at some point in case of an audit or something. So how do you solve those problems. Well you wind up finding ways to do this at scale massively. So much of that is almost certainly dead stock slash data. That will never be touched again. But god help them. If one day it goes on available. Yeah i mean that was the dream of the startup. I was that was sony. Email archiving and like you're never going to probably need that email again until you need it and when you need it like it's probably because you have lawyers asking you for it right so having a place that you can put an object like an email or bundle of emails and not have to think about it for a really long time is so compelling like who wouldn't want something like that just dump your data here and maybe i'll do something with it later and navy some product manager comes along is like oh god we could. We could do some analytics all this data we have. And because it's all there right now you can do stuff with it. I'm really looking forward to seeing what the future cloud holds. The challenges though is that there are over fifty billion dollars a year now in run rate and bat is an awful lot of revenue pouring in there but they got there by reaching out specifically to developers and infrastructure people to wind up driving cloud adoption. The next fifty billion is not gonna come from those folks. It's gonna come from a lot of the blue chip enterprise style companies that are migrating in various directions. And that's a challenge that historically aws has done a relatively poor job of learning to speak to those businesses in ways that resonate talking to the it ops person who is not going to learn cloud formation. They're going to do things in the console for example is a bit of a stretch for them in many cultural respects. You can't do bottom up adoption the same way anymore because it turns out neither developers nor operations folks in. It are empowered to sign a fifty million dollar. Cloud deal the second time because the first time they did. They were fired and prosecuted. Yeah i mean amazon. They're not known for that. They're not known for being able to speak to. We'll call like the old guard enterprise. There's a lot of data centers still out there. There's a lot of workloads that are still in those data centers and you ve. Companies like oracle and microsoft. That are odyssey this way. Better at telling that story to those people everyone thinks. I'm kidding when i say this about microsoft but the honest truth is is that they have forty years of experience apologizing for software failures and that is exactly what you need to do in the cloud because things break all the time and at scale that is what happens and you never get away from that. So you best be able to articulate that in a language and a context that you're angry customers understand and appreciate and microsoft is the undisputed expert in that space. Yeah i mean. Microsoft has the advantage in the enterprise. They've been in the enterprise for you know thirty plus years right. It's so easy for them. They're already there with exchange server and all other components that tie into it with active directory. They know how to talk to those. It folks and they're already involved in those engagements whereas amazon amazon is not selling an email service to these companies. They're not selling domain controllers services and exchange services and file. Services and share point microsoft. Already they're already have their foot in the door. So feel like amazon has a big hill.

microsoft Microsoft amazon five years forty years oracle thirty plus years fifty million dollar sony s threes second time first time Attis over fifty billion dollars a y one two thousand fourteen single kuban aws billion
"kuban attis" Discussed on The 6 Figure Developer Podcast

The 6 Figure Developer Podcast

09:58 min | 2 years ago

"kuban attis" Discussed on The 6 Figure Developer Podcast

"From a developer standpoint. Your Code is the thing the Henry optimizing and although you could develop and tasks in the container running. The truth is to do that correctly. Requires you to master a lot of other details. That have nothing to do. You become a container developer in not an application developer and that he will call it hinge between native developed at an what is supposed to be immutable immutable infrastructure. Immutable applications means that you gotTa really sort of from a developer language sampling. You gotTa really can't nail the experience with retooling ask at individual developers love kind of geeking out on that and it's wonderful but what it means is that over the last three. To five years at scale we moved away from the container native developed. We really we just failed to take things like trapped in there. Were others like I say till gets close to this and there are a couple of other projects that are pretty good that we're we're trying and since we failed to give that tooling enough work fast enough. Basically developers an operational work when passed and now most people moved to a building the container on a push to get and that makes containment more of integration solution more a CIC pipeline solution in less of a developer choice that turns out to be the default. It's not necessarily the best or the worst way of doing it. Just you can see that trend happening the result of that then that connect makes real easy to see why things like get off says the sort of flow right begin to be important because now you can drive your whole engine of development and artifact creation delivery off of what happens in get as opposed to what a developer might have. Done it all sorted. You can see how involved in a way that has to do with the developer reception in the inability to sort of as a huge mass of talented people. Sort of all skill up on container esoterica at speed. We really basically said you know what? Actually that's more trouble than it's worked and so that's sort of where we stand now. It's actually go ahead and optimize on from a language standpoint and choose your language and then try and work with your Surrounding environment to make sure that the tool for the language builds your containers directly for debugging then also released another problem with containers. That's hard to get around with. Some languages can debugged the same container the ship making things immutable there. But other languages you gotta actually put the debugged container and run that and that is slightly different than the real the real code. And so you get into these when you really start using this stuff heavily you got to be a master of that song. Which is certainly doable. People are doing it but what it means is in an organizational situations as opposed to you know smaller companies were. They're closer full stack. Beverly do everything kind of things. Yup Looking at Separation of concerns. There somebody becomes an application operations team and they work on the templates developers consume and the pipelines developers use as opposed to the actual application. The developer does everything and just so. That's one of the things that I always wanted to sort of just dump out in one place. It's an amazing actually process transformation where there were opportunities two years ago that we no longer happen soon. Nobody's GONNA learn contains at that well as a result one of the audit results of that is that containers are mostly way too big and heavy like I'm not even talking about windows containers like people ship containers eight hundred eggs too. Because they can't very related to all of that. I have been using containers for development for a few years now started with a angular application and we needed to run the same in Dev as wouldn't production because we're running into issues with node being upgraded or not upgraded different versions on different developers. So kinda built up the containers for that to work so that we got a consistent environment all the time when everybody's computer assault a lot of problems absolutely will end then in my in my newer applications. I'm doing blazer and I made sure to default to a containerized Build but in visual studio and an just me doing it on my own. I've always used docker. Compose should should like a a developer. Select I guess a development my situation. Where I'm I'm the tech lead so I'm the one responsible for making sure that the builds are good for development and can be deployed not. I'm not to devops level of of the and all that stuff but I work with devops to make sure stuff works so someone in my position. Should I be doing Cooper Netease I don't even know I know. Roughly what Cooper Netease is but I was kind of think of it as like this. This V. Land that has all the containers for your application not whereas like well. I guess I look at it as exactly the same thing that compose Kinda does So how'd you know that's a fair view so I also am on the first of all you know caveat? I love kids a lot of fun. It's a great. It's a great system but it's a tool. Don't fetish your tools. I can say that I like to laugh about. I'm dead serious. Do not finish through tools. The reason being is because I'm you can see I'm great so there are so many tools I have eaten consumed and if this process they in my life that what I can tell you. Tools are great when they serve your needs in survivors question to you is you. Don't need a New User Newton no Cobra Nettie until in fact. It's slaps in the face of so like how do you build and deliver right now? Do you know where you're up. Steam drops her container or your application if they drop uncoordinated and you don't know why do you even care? Yeah I think they're just doing a service okay. So whether it's APPs like we'll talk about Microsoft terms or whether it's you know anything else right like it could be any pads you give them a container or you give them a bundle stuff right. Maybe so for example you drive Using containers as a consistent development environment right so the entire bet team could be slightly wiry or you know and yet when they're inside that container they're always getting exactly the right thing for delivery behave so it doesn't even matter whether you're delivering the containers are not pointers containers. Already helping you. And that's great. That is a fantastic tool and it continues to work off the communities very straightforward understand in fact the details of course are complex. Because you know orchestrations hard work but it's basically taking the container. You built the APP and then giving it to a docker host and running one of those and then wanting to run ten and then wanting to run a million so you gotTa build a program that runs a million so coronets runs a million fauria and if it falls over the replace it you know in. You don't have to do that okay. That is a fairly simple berry. Hi Ho obviously you know. Description of what communities does so your take on. It is right. It is another way of looking if you've done darker and you're familiar with docker composed files for example. A composed file is just another way of looking at a got one two three of these. I've got over here. And they connect in this way and I'm GONNA go logically. Speaking composes. A fantastic way to think up from the developer standpoint of a distributed application basically services talking to services and you can look at them and see how they interconnect and so forth coup Bonetti's manifest is just a more complex version of that and so for example if you get to communities. That's a that's an implementation detail of what you're doing and looking at when you look at compose compose great format and. I'm hoping we're going to see a lot. More that uses that format coming for That's why I really appreciate that. We have decided to kind of kick that responsibility down the road to to folks that are interested in maintaining in creating that infrastructure virtual infrastructure for us in coober netease that not every developer has to know all of it to to be able to develop. We just have to know enough to make sure it's containerized. Yes that's absolutely true as a developer. If you haven't gotten into yet explicitly right like Sony even say. Hey here's money you will if you're building processes which is an apple to process especially like websites web. App is a just an end point. That serves html supposed to or API. You know things like this. If you're building one of those right keep building. You should not be distracted by Cooper Nannies can give you an example. Why another Tory story of the five years of carbonates and that is a wall along. The other things that happened is that originally Kuban attis was a very simplified tower flea. Powerfully structured partially flexible architecture scale out individual processes that were the process continues right okay and there are lots of knobs inside coronation can touch and the thing about it is. The delivery mechanism is.

developer Cooper Netease CIC apple Cooper Nannies docker Kuban attis assault Microsoft Cooper Beverly Cobra Nettie Sony Ho Bonetti
"kuban attis" Discussed on Software Engineering Daily

Software Engineering Daily

02:00 min | 3 years ago

"kuban attis" Discussed on Software Engineering Daily

"We're sick of tire to to manage community. So we won't like Eka. Yes. Now, we won't like manage control plano demoss ter- in. I think people are still not yet that excited about the continuing instances in the service containers because right now a lot of people are in the exploration mode. So they won a load of control. So they wanted employ wanna see what happened in. I think that the we're gonna see Creedy pretty soon how the extent excitement is going to sharply increase around. This. We already seeing it Marcus tumors went when we peach damage. Until them busiest what ocean ause, I see the moment. I see like how people like their eyes are shining using. Oh, are you serious? Can you really deliver that if if? Yes, that's that's like the holy grail. We just deployed containers in the infrastructure of self manages itself. And I think we're hitting that sweet spot right now to what's the contrast between the experience of somebody who distributes their micro services application across a self managed Kuban Attis cluster versus distributing their micro services across container instances, whether they're container instances are on far gate or on ACI Iran spot inst- ocean. The is there something you get out of distributing it across a coober Netease cluster. You're managing yourself. Of course, is is is just like a really something very manual versus something so automatic. So even think about it. If you run your containers on on a static infrastructure. So you're probably paying anywhere from like thirty to forty percent more on the the underlying compute because gotta static. Maybe it will scale up and down from time to time, but it will not fifty two of to the actual location need, you know, that's the that's easiest part and the war..

Kuban Attis Creedy ACI Iran Marcus forty percent
"kuban attis" Discussed on Software Engineering Daily

Software Engineering Daily

04:52 min | 3 years ago

"kuban attis" Discussed on Software Engineering Daily

"Still extremely fast extremely performance and via plug ins can also be extended to do things that perhaps Kong doesn't do out of the box in a service, mesh deployment. But you're right. The feature set of north south and the Fisher set of east-west is very similar and all the things we usually do in east-west or all the things we do in our. South will have to adopt in more and different patterns. So being able to rate limiting circuit breakers. Al checks being able to keep that late and down being able to observe what's happening within our systems. It's not a concern that's specific to one or another. It's a concern that both nurse out and east west will have to fix and therefore Kong is being used for that today. So is the service mesh model for Kong is it the model of deploying aside car to each of the services and then having a central control plane that the sidecars are communicating with you got it. So you're getting nine deploy Kong as a service mash by injecting Kong as a sidecar proxy to a Microsoft Office. But get spot from agnostic. So you can do that with Kuban Aries you can do that with a sidecar container. But you can also do that on any other platform that supports so conch supports fifteen different deployment methods. We support any. Containers Mazuz feared Decio as we support vanilla Docker. Of course, we support any cloud, Azure, Amazon Google, and we also support bare metal platforms. So basically with Kong, you could start a service mash that runs across Kuban Attis, but not limited to coober nineties, also Imprimis and on machines and any other cloud. So effectively it's a platform agnostic hybrid mash that you can deploy with calm when I've talked to people about service mesh performance is a really big concern. Because if you have for example, a service proxy, that's deployed is a sidecar to all your containers. And it's sitting next to your service in every service. Request is going through that sidecar. For example, if your service proxies written in Java, then even just a pause can really give you a serious performance penalty. And that that can be problematic. If this thing is is a bottleneck to every single service request, tell me about architect, dating the sidecar what you have built in the sidecar turns out that when we built our run time. So like we said engine X low and loo edge it we're able to achieve a great performance in most use cases, Asaba millisecond processing performance. So that same Runtime we've been running for traditionally pay gateway is also so lightweight and so fast that out of the box it support service mash, so that's why we were able to support one run time for both east west and north south. That's pretty cool. That sounds like a bet you were very happy to find that out. Well, it happen for a reason. I guess so I mean is there any is there any material? So what you're saying is basically the same software that is in the API gateway that has been accepting requests from the external internet and doing routing through the API gateway in a performance fashion. You can just retool you can just repurpose that in Assad car to be able to have services communicate with each other. Yeah. Not only that we can do that with a better performance than envoy, for example. Really? So tell me more about like how you think this market is going to unfold because I was guy go to these kube cons, the Cooper, Netease conferences, and there's if there's any water cooler, or like, you know, hot hot topic right now, it's sort of like, what's you know, who's gonna win the service mesh world or do you need a service mesh? So how do you think this world is going to unfold and how big of a market? Do you think there is for the service mesh? Usage, you know, Microsoft disease that are very hot topic right now, not everybody needs Microsoft disease. I mean, Microsoft sees that are harder to deploy harder to manage his anonymous significant premium that developers will have to deal with once the move to Microsoft sees. So it's a great architectural pattern. If we're talking about extremely large use cases that have to be hyper scaled in hyper optimized with micro services architecture. Now, are we talking about Microsoft uses the way, we make that Microsoft's architectural work is with service mesh service mash, it's not at the -nology service mashes a pattern, and so you can implement service mash by using a wide variety of technologies that are available to developers today..

Kong Microsoft Kuban Attis Google Decio Al Netease Assad Imprimis Cooper