Wait, well today we have Sebastian, he will be talking about the Asynchronous SGL Alchemy. How are you Sebastian? Oh I'm fine, thank you for asking, yes. Where are you streaming from? I'm streaming from the Netherlands in Rijswijk, that's near the Heik. Oh nice, I'm in Amsterdam. How nice. Cool. Okay, I wish you good luck and thanks. You can start whenever you want. Well, hello everyone, welcome. My name is Sebastian. I'll introduce myself a little bit more later. But today we're going to talk about Asynchronous SGL Alchemy. It's a very cool new and exciting feature that will be, that's part of SGL Alchemy 1.4 that has just been released. And this beautiful painting is of an alchemist. You can see it at the Mauritshuis in the Heik if you're ever there. It's a beautiful painting of an alchemist and I thought it was fitting for this presentation. So since we're talking about Asynchronous SGL Alchemy, we also first need to discuss what the ingredients will be for this talk. And for that, it's basically this. We're going to talk about what the differences are between synchronous and asynchronous input-output. Now, mind you, this is not going to be an introduction of Asyncio in Python, because this talk isn't about that. I assume that you've already seen it, but we are going to discuss what the consequences are of Asyncio for SGL Alchemy and what you have to do. Then we're going to do a small comparison between synchronous and asynchronous SGL Alchemy. What are the differences? Which parts stay the same? Do you have to relearn the entire library again, or can you just rely on your existing knowledge? And we're also going to talk about a very important problem that happens as soon as you start talking about asynchronous input-output. And that is eager versus lazy loading in your SGL Alchemy objects. And this is going to be very important. So we're going to dedicate quite a bit of time in this presentation to that issue. Well, first of all, who am I? Well, I'm Svastjan.  I live in the Netherlands. And I'm currently working as a code smith and developer for Ordina Biteniers. Ordina is an IT service company in the Netherlands. We mainly work for larger clients. So we're an IT service company. We do a lot of consultancy work. And then, yeah, you can think, well, governmental organizations or banks or other larger organizations. That's mainly what we do. And we really try to focus within our Biteniers unit on enterprise-grade Python. So really developing Python as enterprise applications. So it's really a lot of fun. And we have a fairly large team, and it's a lot of fun to work there. I'm also one of the three owners of Python Discord. I don't really like the term owner, but it's a Discord terminology. So we just stuck with that. And Python Discord is an online community for Python enthusiasts. We currently have over 200,000 members, which is a lot. But obviously it's a little bit like Slack. So the actual active number of members is much lower. But still, we currently have over 100 volunteers who dedicate some of their time to discussing Python, helping others with Python, or organizing Python-related events. So that's really cool. And I'm really glad that I can be a part of that. And I'm really proud of that. So that is who I am. So now let's start talking about asynchronous SQL Alchemy. Well, first, let's first think about what it means for an application to be asynchronous. And one of the things that's really important is that we're talking about asynchronous input and output. That's where the name AsyncIO comes from. The IO stands for input and output. And that's really what's going on here. Now first, consider a very simple synchronous Python application. For instance, a very simple SQL Alchemy application. As a developer, you may have an idea that your application is structured in functions and classes and modules and files and packages, and that you jump all over the place. But if you think about it from a Python perspective, basically your application boils down to a list of instructions. And this is what we call a single threaded application. We just have a thread of instructions, and Python will execute those one by one for you. So that is really simple. So Python goes to the first instruction, and it goes to the second instruction, and it will only move on to the next instruction once that instruction is completed. It's not really relevant or important for us to really talk about what an instruction means. This is really a very abstract explanation. But what is interesting is when we hit this red instruction here, this is an instruction that performs input and output. And in this application, that is making a query to a database server and getting a result back. What's going to happen here in a synchronous application is that this call is going to be made. SQL query will be sent to the database. There it goes. And then what you get back is a response with your data. And Python will just sit here on this call waiting for the response to come back. And only once it's ready, will it move on to the next instruction. And this is basically what your single threaded application normally does. In Async.io, we're working with a slightly different model. So what we're working with here is that we have an event loop. And an event loop means that you can have multiple tasks that are all scheduled to happen at some time. So instead of having your application as a long list of instructions under the hood, it's still that it's better to visualize your application in terms of a separate tasks that you want to execute. And you always have a current task that Python is currently executing. But in addition to that task, you also have other tasks that are scheduled that are not yet being executed. They're just waiting there in that event loop until they get a chance to run as well. Something interesting will happen here if we try to do the same. If Python will first just execute those instructions one by one, but as soon as it hits this input-output statement, then something interesting happens. We're going to wait for the future result of this operation. We're going to await it with the await keyword. And basically what that means, it sets the process of input-output in action. It sends out the request, but then it also signals to the event loop. This task is currently waiting for something. It cannot do anything else. Let's just put it back into our event loop like this. And then in the meantime, while task one is waiting for the result of that asynchronous input and output, another task can become the current task and can start executing instructions again. This is the basic, very simplified idea of async.io, very high-level perspective. But what is important here for SQL Alchemy is that every little bit of input and outputs that we're going to do needs to be properly executed in such an asynchronous way. Because if you start executing synchronous input-output calls, so calls that really need to wait before they get the result back, then you will block the entire event loop. So it's important that every task that executes such an input-output operation really does that in an asynchronous manner. At the same time, if you now consider your new SQL Alchemy app, your fully asynchronous SQL Alchemy app, this is still something that is mostly about the SQL Alchemy application itself. It doesn't really have anything to do with the database. So what that means is that, yes, we need to make sure that every bit of input and output, oh, typo there, input and output is scheduled in an asynchronous way within our application. But the actual request that we need to send to the database and the response that we get back, the actual SQL query is going to be mostly the same as what it would have been in a regular synchronous SQL Alchemy app. So that asynchronous input-output part is really about how you schedule your operations within your own application. And this has one really big advantage for every one of us. That means that basically all of what you know about SQL Alchemy already, how you build queries, how you use selects, how you use width, and so on, will translate almost one-to-one to asynchronous situations as well. It's just about how you send out that query that's going to be different. And I think this is really reassuring. There were a lot of people fearing that when Async.io was introduced in the standard library, we would need to build some kind of a shadow standard library with all kinds of asynchronous features. You may have had that fear about SQL Alchemy as well, that you needed an entirely new SQL Alchemy with only asynchronous co-routine functions that you had to relearn the entire thing, but that's not the case. You can basically use what you already know. I think that's really great. Do notice that there's an old though here in the middle sentence, and that's what we're going to talk about later. There are some consequences when you're using things like implicit or lazy loading of data. That is going to be really important later. So, right. This was very high level. Let's see some asynchronous SQL Alchemy in action.  Then we can really compare what the differences are between the two versions. Mind you, these examples are going to be very simple, very simplified, because this is not a talk about very advanced features, what you can do with the SQL Alchemy query expressions. This is much more about the difference between synchronous and asynchronous SQL Alchemy. For those of you who are interested in reproducing these results, the versions I've used are Python 3.9. I'm using SQL Alchemy 1.4.22. There's an important note in documentation about this, and that is that the Asyncio extension is currently considered to be better level software. They predict that the interface is not going to change a lot from now, but you need to be aware of that. It's probably going to be, I don't know, I'm not involved with the project myself. I'm just a happy user of it. My suspicion is that it will be released in full with the 2.0 release. When it comes to adapters, I'm using AsyncPG version 0.23 for my Async database adapter and PsychoPG 2.9.1 for my sync adapter, and I'm querying a PostgreSQL 13.3 database, and I'm running it in an Alpine-based Docker container.  Right, so let's see something in actions. First of all, we're just going to set up the SQL Alchemy engine. This is the synchronous engine, and it's just using sqlalchemy.createengine. I enter the database URL, and one precaution, never hard-code your credentials like this EuroPython colon EuroPython in production code, but here for this example it's clear, and my database name is also EuroPython, and it's located, hosted on the local host, and should be accessible over ports 9876. I've also enabled the echo, which means that sqlalchemy is going to output a lot of information that we can use later to explain some of the stuff that's going on. I've trimmed most of it in the output that I'm going to show you, because there's a lot of output, but I'm going to show you some relevant parts of it, and I've enabled the feature of future is true, which means that I'm mostly going to use the new 2.0 style querying that will be part of sqlalchemy starting from 2.0. 1.4 is actually a really nice compatibility release. You can already start to use that new style query language and then your application will be future compatible, so forward compatible with the new 2.0 version. Since the async part uses that exclusively, I've chosen to do that as well for the synchronous part here. So right, now I've got an engine. Let's see how that works in an asynchronous engine. Well, it basically works the same. The only thing I'm doing different here is that I'm importing the async.io extension to sqlalchemy and that contains a function called createAsyncEngine, and I can use that to create a asynchronous engine for myself. So you can see here, I've specified the asyncPG adapter in my URL, but the rest of the data is basically the same. So at this point, the two pretty much look the same. There are no awaits here yet, which is also an important lesson. When you create an engine, there's no connection being made with the database yet, so you don't even know if your settings work. You will only see that when you first start communicating with your database. But now I've got an asynchronous engine and I've got an asynchronous engine that I can work with. Well, let's execute a very simple sql statement. This is basically the same introductory statement, sql statement that you can find in the tutorial. I've just changed the text to Hello, Eurobyte in 2021. So I create my statement sqlalchemy.text and if I use the synchronous engine, I can just do with engine.connect as connection or com, and then I can execute the statement and I can print a result and it prints Hello, Eurobyte in 2021. What's the asynchronous version of that? Well, that looks like this and the first thing that you should notice is that the statement that I'm issuing is exactly the same and that goes back to what I said earlier. The part that needs to go to the database is obviously just going to be the same query as that you're used to. The only thing that's really different is how you set up the connection. You now have an async context manager, async with engine.connect and when you actually execute your statement on the connection, you also have to await that result. Now, once I have that result back, that's going to be a regular result again because I'm not lazily loading in the results from the database. So if I then print the result, I get the same string out again. So if you compare the two, you can see that they're pretty much identical only for setting up the connection. So the actual part needs to do the input and the output with your database. That's something that's going to be different, but the statements that you're going to execute are mostly going to be the same. So everything you know about sqlalchemy, about making select statements, it's just going to carry over to the asynchronous sqlalchemy. Right. That looked rather simple, but what's the catch here then? Well, I think the main catch is that you cannot simply rely on implicit input and output.  You're not really considering this, and sqlalchemy will make implicit calls to your database almost all the time. To illustrate that, I'm going to introduce a very simple object relational mapper model. This is a traveler, and this is a really simple traveler. We're going to keep track of an ID, a created ad field, a name of the traveler, and an age of the traveler. What's important here is that the created ad field has a server default. This means that if you create a traveler instance and you save it in the database, if there's no value for created ad, then the sql server will run a sql function to get the current timestamp, and it will use that as the default for that field. What's important there is that this is something that happens in your database. Your application doesn't know that value until it has made a request to the database to ask for a value that's been created. That's something that we can see in action. Here, when I create a traveler object, Sebastian, that's my name, and I'm age 35. I can save that into the database with an ORM session. Then I start my transaction and I add my object. Since I'm using session.begin, this will auto-commit the object, so it will actually save the object in the database. That's basically what we can see here. This is the echo output of sql alchemy, trim down a little bit and here you can see the actual database transaction going on. This is until the print with the separator as you can see on the screen. You can really see here that sql alchemy will insert this new traveler into the database. Now, we want to look at what happens when we want to print the created add date for Sebastian. When the print statement hits here, everything below the separator line, you can see that sql alchemy has to issue another sql statement to the database to get that newly created created add value, because it was created in the database because it was a database default. Even a simple attribute access like Sebastian.created add here can implicitly send a request to the database for information. Well, in synchronous applications that's fine, that works, but in an asynchronous application that's not really going to work. So here we're trying to do the same thing. I'm creating asynchronous session for my ORM using the async session class. I've also specified expire on commit is false. This is a nice setting that means that my ORM object will not completely be invalidated after commit so that I prevent number of inputs and outputs I need. Just basically I'm going to do the same thing. I'm going to use my async session now with async with and I'm going to add the database object. Well, that part is going to work fine. But then when I get to the part where I want to print the created add here let's just move it up a little bit. Then it will try to retrieve that data from the database. It's going to make another call to get that created add value and then you can see that you get a exception. In this case the exception is a little bit cryptic. Something about a green light. We'll get back to that later. But what it basically says here was IO attempted in an unexpected place and that was what happening that is what is happening here. We cannot just use lazy loading in an asynchronous situation. So what's the solution for this? Well, for defaults there's a really simple option. If you go back to your ORM model you can add a mapper argument called eager defaults and this means that when you create your new object it will also return the value of the default that was created in the database. So we're going to execute the same bit of code again. I'm just going to create another Sebastian and what you can see now in the sequel that's being emitted is that there's a returning part and that returning part has Trevor got created add in it. So the database is going to send back that piece of information during the creation of the object and the print happens without failure because the information is already available. So this is something you really need to think about. If there's anything that needs to be lazy loaded you need to take care of that. There's also another situation in which lazy loading is really something you need to take consider and that is with relationships. Here you can see that the traveler is that the traveler class has been modified and now it has a relationship with the country and that's the destination country. So there's a destination ID which is a foreign key to country.id and there's a destination relationship attribute so we can easily access that country if we have a traveler instance. So what is the issue here? Well it's basically the same. Let's say that I'm going to add Sebastian to the database again and Sebastian likes to travel to Norway because they have a nice environment that we don't have here. You can hike there in the mountains. So I'm going to add Sebastian here but now I have an issue. If I now going to retrieve Sebastian from the database again with my session and I'm then going to look at Sebastian's destination and I can see that destination is not loaded and this is because by default SQL Alchemy only lazy loads in related models and there's a simple reason for that if you have a very complicated database with a lot of related models if it were to retrieve all that information at once when it gets a single instance for a single object then you would make huge SQL queries all the time so that's not really something that's nice. So the problem here is in asynchronous code normally when you then access the attribute implicit IO will take place to load that destination from the database but in an asynchronous situation that simply cannot happen. So what's the solution? Well the solution is to modify our statement and one thing that we can do is we can do a joint load and this basically tells SQL Alchemy when you retrieve Sebastian from the database you should also already load the related destination field that means that all the information will be prepared the database will be sent to us in one single go and now if I execute the same statement and I get Sebastian from the database you can see that if I print Sebastian then destination is filled with Norway and if I print something with where Sebastian is going it's going to say that Sebastian is traveling to Norway so it's really important in an asynchronous SQL Alchemy that you think about lazy versus eager loading and you need to use eager loading where possible. You really need to think about what are the attributes that I want to use on this overall model and you really need to load in that information beforehand or you have to load it in after but in an explicit IO call using the asynchronous methods otherwise you will just get errors all the time. So that's really important. You really need to take eager loading into account. Well then finally what if I want to run something that specifically uses a synchronous IO function well there's also a solution for that and that is run sync and what async session.runsync basically does it takes a synchronous IO function or a function that comes from synchronous IO functions and it will turn those into asynchronous calls under the hood using something called greenlets and this is really close to the database adapter level it's not something you see and that means that it allows you to use the metadata.createall which is a synchronous function normally you can run that with run sync and SQL alchemy using greenlet we'll take care of hello yes we'll take care of ah am I over time now yeah it's over time if you want you can finish or we can go for the questions I need only about one minute or so okay go ahead so under the hood the metadata.createall will now be called asynchronously you can even do this with your custom SQL alchemy functions but it's really important this only works for SQL alchemy IO functions if you try any other kinds of IO like web requests they will not be transformed into asynchronous calls so this is a really neat feature and it also allows you to use the old synchronous style just put it in a function and run it with run sync and then suddenly all your synchronous calls will still work so it's pretty neat but do be aware of how it works well and then the summary I think the most important thing is that you don't have to be scared of asynchronous SQL alchemy most of your knowledge will be directly transferable you do need to think carefully about operations and perform input and output and if you really want you can still run synchronous functions that do synchronous database IO functions with run sync and that's it for me thank you very much okay thank you so much it was really nice I've been using for for some time SQL alchemy 2.0 and I find it super cool you have some questions the first one is if you will be able to the code in a github public repo and share it in the chat later yes I will be able to I need to tidy it up a little bit but I will share it then are there any plans to change the defaults for asynchronous mode to use eager loading I suspect nearly everyone will hit these issues at least once that's a good question but I cannot answer it because I'm not involved in the project itself I'm just an enthusiastic user of SQL alchemy but there are some issues with eager loading by default and that's basically when you have a lot of relationships and you were to always eagerly load all those relationships that means that a very simple SQL call that would only normally get you a minimal amount of information suddenly turns in this very heavy long running SQL call in your database because it needs to load all those relationships between models and there could be many to many relationships in there all kinds of other relationships so I suspect that they will put the responsibility at your feet you really have to think about what is the information that I want to use instead of that they will just load everything for you because that can be very expensive that's my guess thank you so much there are a couple of more questions but I will add it in the channel thank you so much yes


Live from Dublin, Ireland, it's theCUBE. Covering Hadoop Summit Europe 2016. Brought to you by Hortonworks. Now your hosts, John Furrier and Dave Vellante. Okay, welcome back everyone. We are here live in Dublin, Ireland. This is a European version of theCUBE. This is SiliconANGLE's flagship program. We go out to the events and extract the signal from the noise. I'm John Furrier with my co-host Dave Vellante. My next guest is Rumerthi, the co-founder of Hortonworks. You are the CTO at one point. We now have a new CTO, but you're the co-founder. Arun, great to see you. Thank you, a pleasure. It's been a while, but it's fun to be back. Great to see you. You look great on stage, too. It was a great keynote. Really talking about the journey of Hadoop. It was nice to see the slides, a little throwback, 2006. Absolutely. It's been a while, isn't it? Through there, yeah. Tell us about, what's the world like for you these days, looking back like that? It's kind of amazing. One of the things I like about Europe is coming here. It gives you a sense of perspective on time. We talked about 10 years with Hadoop yesterday. I was at the Trinity College, and that one's been the first Provost they had was in 1592, so it gives you a sense of time. How small we are. Exactly. Hold it in my house. That was before the first pop, actually, which is actually. Yeah, so it's been an amazing journey. I couldn't have imagined how far it would come, but being here, we obviously want to go further. Hopefully, you guys and us will be talking in 10 years from now, and talking about the 20 years we did, not 10. Yeah, 10 years, congratulations. It's been a great run.  But you guys have done a lot of work, and what's interesting now is, under the new marketing and kind of the positioning, highlights kind of where you guys are going, this whole connected data platform. Absolutely. You know, as, we've always been focused as a, as a set of, as technologists and as a company, we've been focused on making sure we help our customers solve their business problems. Now, it's been pretty, it's becoming clearer and clearer by the day, especially over the last, I would say, 12 months. This notion of IoT is becoming, you know, important and real. It's been, we've been talking about IoT for a long time. You know, toasters and fridges for 10 or 20 years now. It's become real. I think there's a set of things which have happened. One is, it's getting cheaper and cheaper to move data around from the point of origin to its eventual destination place. You know, things like 3G and 4G definitely helps. Obviously, we play a part as a Hadoop community by making it really economically feasible to store and process data at scale, to curate data at scale. And last but not least, I think what we'll also see going forward is hardware itself. It'll get cheaper and cheaper to produce custom hardware, so you're going to stick hardware on everything, whether it's a Raspberry Pi, a $3 Raspberry Pi or whatever. So if you take these trends of cheap hardware or custom hardware, custom Asics, cheap communication channels and cheap storage and processing channels, it's the right, it's sort of the right point in time, if you will, from a technology curve to be able to solve this. And what we've also seen is, over the last couple of years, I'm sure, you know, there's the gardeners and everybody's talking about it, which is more data is getting generated outside the data center than within the data center at every enterprise today, whether it's social and mobile, you know, sensors, beacons, and so on. We, as a company, it was very important for us to, ensure we have a complete end-to-end story from the point of origin, which is where the Onyara acquisition came, and folks like Joe Witt, phenomenally smart guys, we love having them all at Hardenworks. It allows us to, you know, capture data from its point of origin into sort of classic analytics with Hadoop, and equally importantly, push the data back into the edge for, you know, better intelligence. And it's using the data for insights and actionable results. Absolutely. You know, one of these wiki-bonds talking about, and you mentioned Garda, but one of the things wiki-bonds talking about that I think is important is, taking the systems of intelligence concept to a whole other level, and they got a lot of traction with that, because the practitioners out there are looking at data, and Ragu from Microsoft talked about it, data is everything. You know, I wrote a blog post in 2007, saying data is the new development kit, kind of people like, what do you mean? It's now pretty clear that data is now part of the development process with DevOps and Cloud. Absolutely. Data is an ingredient for that. Absolutely, and you know, I think you put it well. So the way we see this is that every application that you're going to write in an enterprise is a data app. I mean, if you're not able to manage data, if you're not able to use data to derive actionable intelligence out of that, you're doing something less than ideal. So we feel like, again, if you go back in time, data is probably the most tangible asset you have in the enterprise. I mean, if you had a piece of software running in 1960, it's worthless right now, but if you had, let's say, an IBM stock code from 1960, it's definitely useful in some context or other. That's why data is the most tangible asset you have in the enterprise. The context is changing so rapidly that data's got to be fluid. Absolutely, and you've got to have lots of it, not just down sample data. Having data in its raw form is really important and we're starting to see that more and more of the industry sort of appreciated and actually take advantage. So since we're going down memory lane, I want to go back to the original founding days of Hortonworks. You guys used to have your, the original founders would have a statement that 50% of the world's data would be stored in Hadoop by whenever, 2015. Now, whether or not that happened, it's kind of irrelevant. The point was that was a sort of a unifying vision. And you're talking about, you know, the amount of data essentially that you can now economically store. Yeah, move and store, yeah. So have you sort of achieved the objectives of the intent of that statement? I think so, I think the biggest intent of that statement was to help people understand what we're talking about here, which is that data is the tangible asset they have and managing data and managing data is a skill that every enterprise needs to learn. And obviously the context has changed from the last 20 years or so. People who probably capture less than a person of data. However, if you look at what's happening in the world, probably more data has gotten generated in the last two years than his entire history of mankind, right? So I think that challenge is getting ever more larger and ever more important to solve, which is fundamentally being our thesis. And so is that your true North? Or is that just sort of plumbing and the true North is more sort of deeper business integration? Can you talk about sort of that current vision? Well, I think both are part of the true North. Like I said, people, you know, you cannot build software and applications in isolation, right? Which is why I think it brought up a great point which is having complete integration, whether it's security, whether it's, you know, technologies like the cloud, whether it's data governance, management and so on. Having that integration along with all the technology, along with all the investments you made in the enterprise, whether it's with Oracle or IBM or any of these guys, having that fully integrated version with in a secure fashion is super important. And that's how that helps us achieve the ultimate goal of managing data well and taking advantage of it. Arun, Dave first said when we did theCUBE when you guys came out and Claudio had a little bit of lead on you guys. Obviously that lead's changed completely around. Oh, Horton was going to be the red hat for Hadoop. I was kind of like, what people were talking about. And Dave would say, can there be a red hat for Hadoop? And that was kind of what people could put their arms around the open source paradigm. A lot of a lot has changed. Certainly you can't really say red hat was the Linux at a different time than Hadoop. We all know that, but brings up the point of kind of what you guys have turned into, which is essentially integration opportunity around open source. And this is something that we're teasing out on the Wikibon and SiliconANGLE team is we're identifying that most large enterprises want integration beyond some of the POCs or shadow IT land and expand adoption. And what does that mean for them? Because they want to integrate. And how do you guys help be a positive impact for that? So I think in our role now as one of the key, so you talk to any enterprise today that Horton works, probably it's the same for any of our competitors too. There's more data, or at least there's as much data in Hadoop as in any other system in the enterprise today, which means given the fact that everybody understands that data is important and it's tangible, we are a trusted partner to our enterprise customers, where we go in and help them integrate with not just their internal processes, but also with other vendors they may have, like a Pivotal, you saw the announcements today, Pivotal or an IBM or a Microsoft, we feel like playing that aggregated role of what through data is an important role, or an important sort of function we bring to the enterprise and we help them manage their data across all their systems, SAP, IBM, what have you. So I got to ask you the question around the startups who want to come in open source is really an organic environment. You guys run a great show here, it's really about the community, it's not a big commercial event that they have. I mean we're meant to keep it that way. The other shows do, but the integration's hard. So it's hard for a startup or even a company that's transforming to the cloud. Because of the scale involved, we heard Microsoft kind of tease it out by saying, hey we want to create these integration touchpoints. How has the bar changed for companies to win an enterprise customer with open source, with big data applications? What's the current things that you see as from a customer standpoint, what's the bar to the hurdle to jump over? So I think brought up a great point about Red Hat. I think we certainly, as a company, we have to be thankful for Red Hat because they showed that there was a business model around open source. And more importantly, we didn't have to sort of break new ground in terms of helping enterprise understand that there's a future with open source. A first class citizen, if you will. Exactly. Now we're now in sort of the privileged position of being able to sort of maybe help other sort of younger startups show that there's a future in this business. In terms of the integration thing, we see this too, which is we continue to want to make this out of the box integrated, whether it's with Microsoft technologies or Pivotal, because the bar right now is getting higher and higher, right? When I started on Hadoop back in 2006, it was just a tie project, right? So you could do whatever you want and people who liked it would download and run it. To fast forward that 10 years now, we occupy a pretty important part in the overall data stack at the enterprise, which means as Hadoop's become sort of the central, one of the more central pieces of your data architecture, the bar has gone up. Things like security and governance and metadata management and stuff. I never thought about 10 years ago because it wasn't important at that point. But right now, everything we build has to get secured, has to get integrated even within our own stack. Like when we started at Hardworks, we had probably the first version of HTTP, Hardworks Air Platform, the version one had about nine components. Today we have about 24, right? So every time we bring a new piece of technology in, we have to do exponentially larger amount of work to actually integrate it. And it's the same thing. I was just talking to one of our financial service customers, they're like, we love the fact that we can upgrade your software every six months because we trust you guys to do it. One of the concerns we have is if we upgrade your software, what happens to vendor X's software that is integrated with yours, why and so on? And it is a tough job. It's something that we continue to get better at, but it's something that we have to pay attention from an enterprise standpoint. So you talk about growing from nine to 24 components and a lot of that is sort of the original instantiation of Hadoop sort of hits limits. It's pushed to new use cases, so new components have to come out. Talk about how it's evolving. And there are some saying, oh, Hadoop is just a storage system. Okay, well, pretty good one actually. Lowered the cost, did some good things, but it's evolving. Well, I think, as with any technology, you either evolve or you die, right? I think Hadoop, for me, has become more of a brand in the ecosystem or a name for an ecosystem, but I sort of, one of my favorite examples is a ship of Tessias, right?  I think that's the same with Hadoop right now. Is it the same ship? It really isn't, but it's still the same name, right? I think, fundamentally, every piece of that stack has changed. Hope, you know, sometimes, mostly for the better. Sometimes you do have challenges, but as a community and as a technology, as a set of technologies, it's something we are very aware of. If you don't change, you die, right?  Well, Spark, I mean, memory and IoT are great examples of the evolution. Exactly. I mean, that's been a great direct impact. Absolutely. What's the impact of Spark for you guys? Where does it fit in the roadmap? I mean, other people kind of have positioned Spark a certain way. How do you guys do that? We love Spark. The fact that you can actually come in and do a more diverse set of workloads, whether it's SQL or streaming or whatever, using one API is really great. Now, having said that, we have to continue to push the bar. I mean, that's why we've been spending a lot of time internally on this notion of assemblies, which allows you to, you know, for me, good technology always fades into the background. It doesn't hit you in the face. Well, can you just back up for a second? Talk about assemblies. What is assemblies? And then go into... Absolutely. It's a good point. So for me, assembly is, if you look at what our customers are doing today, think of any application they're building, they have to put together a bunch of technologies. They have to put together Spark, and they have to have some NoSQL store, let's say it's HPS. They got to do some metadata management and security, which is NOx, Arrange, or any of these. And they want to maybe use a storm or whatever. It doesn't really matter. The point is we sell a bunch of these technologies, and the customer has to put it together himself or an ISV does it for us, right? Now, there's sort of fundamental limitations with in terms of skills and knowledge and sort of the effort it takes. And I think of it as sort of undifferentiated heavy lifting to put them over and over again, right?  And a new piece comes in, I got to test it again. Exactly, it's the revisions. Exactly. Now, wouldn't it be nicer if you go back to the Windows world? I mean, how many people wrote MFC applications? Very few, right? What people did was they downloaded an application, whether it was a notepad-like thing or word or whatever, and they downloaded and they ran, right? We feel like a similar thing needs to happen in the Hadoop ecosystem, which is instead of the customers putting these technologies together, we want a solution blueprint that you can download and run, right? And that's why it's got a specific configuration of components and how they're wired together. So, it's a runtime assembly concept, right? Exactly. So, you downloaded it, download it from GitHub, let's say. It's a simple spec. You pointed to your existing Hadoop cluster and Voila in sort of thinking in terms of- You are made a lot of the heavy lifting. Exactly. In sort of thinking in terms of technologies, you're thinking in terms of use cases. You're thinking in terms of, oh, I want a customer 360 application. I want a cybersecurity application. I want a farming application, if you will. So, you download, dot, and run, and sort of worrying about what's happening under the hood. So, in your slides today, you had the yarn.next, right? So, what is that? So, yarn.next is all about not.net. Not net, no. It's not next. It's not next. That would give me a trouble with that. That would be interesting. We have a lot to talk about then. So, for us, that's sort of the next phase of Hadoop. You can even call it Hadoop.next, right? Clearly, our marketing guys haven't gone into all of this yet. But- The power's never been. I'm sure. Now, the idea is, you set up this set of, you set up an API and a framework where you can now think in terms of a higher level solution blueprint, rather than in terms of individual technologies like Spark or Storm, right? So, for us, that's allowing those, you saw the spec I put up, right? I'm probably going to get crucified by putting code on a keynote. But that is a spec. You download the spec and you point it to an existing Hadoop cluster, you get an enterprise search application, right? We feel like that is really the next sort of phase for Hadoop, if you will. Like, the first phase of Hadoop was MapReduce, HDFS, then we got Yarn. Now, we've formed a focus on the app. So, take the first implementations and determine the recipes, basically. Exactly. So, the business impact is simplicity, speed, lower cost. Absolutely, solutions. Solutions, right? And we want to see hundreds of startups build those solutions and sell it. And so, what does it take for that to happen now? So, this is in what, you're just putting a spec out there? Yeah. So, in the community, this work has already started for the last, I would say, six to nine months. So, I would say, later this year or later half this year or maybe early next year, we get to a point where you can, I mean, if you go and download Hadoop code right now, you can actually play with it. But if you go from a product standpoint, we'd probably productize it in 2017. And this initiative that's in the community, vendors, customers together, what's the makeup of the- All of it. All of it, right? I mean, the promise for you as an enterprise is that you no longer have to worry about training everybody up in your enterprise on these skills. Sure, you'll definitely have some experts. But right now, to touch Hadoop itself, you need a bunch of skills, whether it's park or scholar, whatever it is. That's powerful. We want to make it so trivial that you can go to a vendor. They have a banking app or a 360 app or whatever. And you can download it. A lot of them will be open source. This allows people to the benefit to the startups and to our solution providers is they can come into these verticals with pre-packaged applications and compete and provide value. Absolutely. And make money. Exactly. We want them to make money. We want to provide the plumbing, but the way you put them together, I mean, a great example is the metron stuff they're doing, which is cybersecurity. We are building one of those apps too, right? Now, we're also building in a way where somebody, a startup would come, drive a specific machine intelligence app, a machine learning algorithm, and they can monetize it, right? We can do the plumbing that they can monetize it. So your role there in the context of building packaged apps is an accelerant. Is that right? Yeah, we want to build infrastructure apps so that there's a spec for you to build your applications. We will, in some cases, we will build the apps like Metron because we're forced to because there's nothing existing out there. But we want them to pump the market. Exactly. We are the catalysts. I mean, I think about Splunk. Splunk has some packaged apps that have been very, very successful, but that starts to bleed into your ecosystem. You don't want to do that too aggressively, obviously, right? We want everybody else to, we want, you know, a trissur or to bring an app, right? Like a banking app, they want to build it. Right now, it's hard.  They're doing a lot of heavy lifting. Obviously, they're doing it a lot of heavy lifting. Well, it's hard because you need domain expertise. Absolutely. You need a lot of data science, expertise in the tech jobs. Yeah, and they want to basically minimize the lifting and focusing on the customer work. You guys take care of that for, okay, so we're going to ask you a personal question. So what are you doing now? You went public, company went public. You're the co-founder. You kind of, I mean, there's always pressure at the next level, gun to your head, public company, a lot of pressure. What are you working on now and what's happening within your daily life in Hortonworks? Well, more meetings, for sure. More customers. That's a good problem to have. You wrote a lot. Customer business. Probably, yeah. Certainly more than a couple years ago. Coding, doing reviews. All my coding happens when I'm on a flight. So I look forward to some of them because that's the only time I get to meet the customers. But I do get to spend a lot. I mean, we've got a fantastic team and a community. I get to spend a lot of time with them sort of continuing to drive the roadmap, but obviously I'm not executing in it. It's my team executing, but it's still, you know, a different level of satisfaction. You guys have oversight and advisory work. Exactly. All right, so here's the billion dollar question.  You've seen this from the beginning, still growing with the company. I'm sure you get a lot of questions from entrepreneurs. There's a ton of opportunity. You mentioned the crypto stuff and the security stuff. What are the good white spaces for entrepreneurs to sink their teeth in? What advice would you give for the folks out there who are on GitHub, contributing code, who get a band of brothers together or sisters, if you will, and just come together and say, hey, let's tackle something. Let's sink our teeth into some new, cool, but relevant areas. What advice would you give them? What navigation would you show? What path is there? I don't think there's one path, but what I've learned from my experience is details matter, pay attention to details, but also make sure that your customer doesn't have to pay attention to details. So you have to pay attention because it's important for you to get things right, but also make it sure that technology blends into the background, because I think the best piece of software are best piece of technology are those which blend into the background. And last but not least, I love the Steve Jobs Code, which says real artist ship, so ship's off there. Okay, so if you were going to do a startup right now. No way. What would you do? No, I prefer, if you were, what would you jump into? Of the ecosystem in the Hadoop ecosystem, what's compelling to jump in on a wave right now? I think, you know, data is still, I mean, I love the code from, I don't know, it's probably you guys, right? Data is a new wild kind of code. I think data is still interesting. There's also FinTech, which is interesting, and security. I was going to say. Yeah, security is not conducive. Leads me to my security question. So let's say, so Rob Bearden says to your CIO, listen, I don't know who your CIO is, I've not met him. But anyway, he says, listen, I want you to present to the board and communicate to them on security, like for us, our own internal security. So the CIO goes to you and says Arun, what do I tell him? What should the CIOs be telling their board of directors about security? Well, I think clearly security matters, because there are jobs in the line and legal stuff on it. But also as a CIO, it's important to understand that security is a means to an end. We constantly have this, lots of times we have constant dialogue with enterprises where security is almost used as, as something to beat people up with. A blunt instrument. Exactly. But I think, like I said, again, a great piece of technology, including security, they blend into the background, they let people achieve their end goal, but obviously make sure that they don't fall into a trap of doing something illegal or wrong. Yeah. What about the ecosystem? Communities win. Absolutely. We're seeing that. I think we're an example of that. It's a great post on Medium, the guy who started Secret, anonymous apps, identity matters, and that kind of brought out this whole, kind of realization that who you are and what you work on in public essentially matters. Certainly open source, it's been this way. Now more than ever, community, it will be the defining factor in winners and losers because the stacks developing, the solutions are coming online through runtime assemblies and new reference architectures. What is the community success factor? Has it changed at all? Evolved? Can you share any color into what's the current state of the community? I think, again, a lot of my experience has been colored by the ASF. I continue to be a big fan of that. Give you a very simple example. We started the Atlas project about a year and a half ago with a bunch of customers actually. You asked about how we do software. So we started the Atlas project a year and a half ago. Over the last six months, we've seen an amazing amount of involvement from IBM in Atlas. It's not something that happened at the corporate level. It's something that's happening at the grassroots level, which is amazing to see. Engineers within IBM. Exactly. Okay. That's great. We're doing this. Exactly. We're doing this over time. Their strategy evolved to the fact that they now are big supporters of Atlas and they continue to contribute lots of their IP and software and time. So again, it's just a small example of how, even though obviously IBM has their distribution, we have ours, we still can collaborate in the community the same way we continue to collaborate with the cloud data on Hadoop or with Pivotal or whoever it is. So I think I'm a big fan of the community model, especially the model that the ASF brings along. I think that's here to say. Okay. Your take on the European show here, obviously it's always been Europe was different in the States, different requirements, obviously different privacy rules are pretty obvious. But as the community gets global, you got Asia Pacific, Europe, South America, Latin America, everything's kind of all now one black world. Are there similarities now? Is it blurring? Is it still different? Can you compare? I think they're getting more and more similar. In fact, some of our customers here in Europe are actually driving on aspects like security and governance even harder. Like you brought up the fact that data from France cannot leave its borders.  That was not a concern in the States, but we brought Atlas here and Ranger here and immediately we were told you have to do this. And that was great because it collectively allowed us to make our software even better. So I love the fact that we get, there's obviously a lot of similarities going forward as the markets mature, but I love the fact that we're getting newer and newer interesting and more interesting requirements out of Europe too. So I'm a big fan. Final question. What are you most excited about right now in the ecosystem, the tech? You mentioned Akka's Rift, obviously we put it on Facebook before we came on. Obviously AI is great, cognitive is good. You're seeing kind of the coolness of computer science around some of the futuristic stuff that we all dreamed about. What are you excited about that stuff? What other, can you share what you're excited about right now? In the Hadoop space or more general? More general. Yeah, in general, yeah. So growing up, my dream, I mean I start programming on a stand. So my pro, and I start playing chess around the same age. So my growing up, my dream was to build a chess playing software. But then at some point I learned Go, right? And I never imagined that, you know, you could write software to beat a human at Go. And here we are, right? It was, I'm blown away with what, you know, Dennis Hassibis over here in London has done. I think that's massive. I'm a big fan. I think it's a moment to celebrate for all of us as engineers. So what do you value guys think about that in the context, you know, Watson had this big grand challenge, right? And then now Go takes it to a new level, right?  People are geeking out. I mean, I think it's really wonderful. I mean, is it competitive to what Google and Facebook are doing? Is it just old? Well, there's an arms-raised aspect to the marketing side of it, though. But I think there's very few, and the population is growing, computer scientists are around this area. So it's just more promotion. I mean, the challenge of Go is significantly higher than chess. Now, Jeopardy, different situation, right? Well, I mean, things have obviously, it's a testimony to how technology can use to improve, right? I mean, one of the big things that Watson did really well was natural language processing. Now I've got a $120 device at home called Amazon Echo, which is probably as good when it comes to natural language processing, right? So it's pretty, it's an amazing horizontal applications as you were saying, John. I mean, Dave, I think people, there's a whole new wave, at least I was talking with Cloud Foundry CEO about this. We're older in the computer science, a little bit older than Arun, but when we were growing up, computer science, we kind of knew everybody pretty much now. The kids are natively embracing computer science as oxygen, and there's a natural thirst for geeking out on writing code and or either being involved in some sort of building or something. So I think when you start to see this automation facilitation around extracting away complexities, people get jazzed about it. I mean, I think Silicon Valley is going nuts. I think Facebook is a clear example of the Oculus Rift. You got the new cameras, you got Google self-driving cars. You have all kinds of cool things going on, Amazon with Echo. So I think, Dave, I think it's just just the beginning of a renaissance of computer science that we're going to see explosion. Well, being able to sort of access that tooling, that sort of AI tooling, NLP, whatever, in everyday systems is huge. When you can get non-programmers becoming programmers, that'll be the secret of the action. And essentially it's almost like 4GL back in the day. Is that something that you see as a new term reality? Look at a couple of things. Even look at things like 3D printers. Pretty much every kid is going to grow up with one pretty soon, right? Not with things like AI. Who knows what's going to happen.  The robotics clubs now are almost in every high school. You're seeing robotics exploding. Did you hear that story on NPR the other day about the kid, some college kid, who basically straightened his teeth with a 3D printer? Wow, really? He basically conducted ortho on himself. That's taking some good cash. I like to figure out how to hit my kids on the program. You know, a lot of people do it themselves. I got to call this guy. Believe me, I got four kids. I know exactly the racket called braces. And the reaction from the industry, the entrenched industry is, well, is there a good thing there wasn't bone disease in there, because that could have been, come on. He's just pretty amazing. Pretty amazing. Talk about disruption. Arun, great run. Congratulations on all your success. Great to have you on theCUBE, sharing your insight and experiences and just overall take. Appreciate it. And thanks for supporting us. Thanks again. Appreciate it. Definitely appreciate it. Good to see you. We are live here in Dublin. We'll be back with more live coverage here of Port and Works Hadoop Summit. Real great community. Not a big commercial show. Really getting down and dirty. A lot of education. And I bring the European flavor to it. So some great t-shirts day with, you know, the elephant with the Irish outfit on. Slauncha. I got to get, I got to get that. We'll be back with more after this short break.


This is one of the more fascinating parables in the Bible. Obviously, all of the parables, all of the stories, anytime something comes out of Jesus' mouth, it's important. But this one here, I don't think we pay close enough attention to and we should. It is very, when I say theologically rich, I mean theologically rich and a little bit of controversy as well. Let's jump into it. In Luke chapter eight, verse four, he's speaking about the parables and he says, when a great crowd was gathered around verse five he says, a sore went out and sowed seeds. And as he showed some, fell along the path and was trampled underfoot and the birds of the air devoured it and some of the rocks. And as it grew up and withered away because it had no moisture, verse seven. And some fell among thorns and the thorns grew up with it and choked it. And some fell on good soil and grew and yielded 100 volt. As he said these things, he called out, he who has an ear, let him hear. Why would you say that, Jesus? What's the point of Jesus saying, he who has an ear, let him hear. Is that to imply that there are some who have ears who cannot hear? Well, that's true. Remember, Jesus is gonna, as a matter of fact, he's gonna say just a little bit. He's gonna kind of explain this. The Jews who were not trying to hear, not trying to listen. At a certain point, Jesus said, you know what? From now on, I'll just speak to you in parables. So matter of fact, let's pick up in verse nine the disciples themselves also were having trouble understanding this and look what he says. In verse 10, he said to them, to you it has been given to know the secret of the kingdom of God. In other words, to them, I'm gonna let you know. And to others, there are some it had not been given to, but to you it has been given to know the secrets of the kingdom of God. For others, they are in parables. So for other people like these Jews, they are gonna have it given to them in parables. Why? He said to them so that seeing they may not see. And hearing they may not understand. So it's possible, matter of fact, everybody has the ability to hear, but everyone won't have the ability to understand. And we're gonna find out that that might be something, this ability to understand is something that's given to them or to us by God. So let's go back to it, verse 12, I'm sorry, verse 11. Now the parable is this, the seed is the word of God. In other words, so what we hear, the gospel, the preach word, that is or the Bible, that is the word of God. Anybody can receive it. Anybody can receive it because it's the word of God. That's not the issue. The point is not the word of God. The point is the seed and what it's sold on. Verse 12, the ones along the path are those who have heard then the devil comes and takes away the word from their hearts so that they may not believe and be saved. This part is extremely important. We're gonna come back to this. Verse 12, again, continue verse 13 though. The one on the rocks are those who when they hear the word, they receive it with joy but these have no roots. They believe for a while. Also important, they believe for a while and in time of testing they fall away. And as for what fell among the thorns, they are those who hear but as they go on their way they are choked by the cares and riches of pleasures of this life and their fruit does not mature. So the first set of examples of people who hear the word and then after a while, after receiving the word, hearing the word believing, later on they don't. Well, what gives? Well, here's the answer in verse 15. As for that in the good soil, they are those who hearing the word. Again, anyone can hear the word, anyone can receive it. They hold fast in what an honest and good heart and they bear fruit with patience. So the question is, how is it that they have a good heart versus the other? Is this heart a result of them? How do you, how could you, is it possible for you to prepare your heart to be good? Is that a work of view or work of someone else? Well, the fact of the matter is that is not a work of you. The Bible is clear that God has had a problem with man's heart. We are just wayward. We like to sin. We have a propensity to sin. We enjoy it. We enjoy being wayward. We enjoy doing our own things. Now we'll say we're gonna do the right things. We'll say that we're gonna follow God. We'll say that we believe and mentally we can ascend to those facts. We can believe it's possible guys to believe that I'm in sin. It's believed that I need a savior that I can't save myself. I can believe that I don't have the ability to save myself, but God has made a remedy by sending his son Jesus to pay a debt that I couldn't pay. He paid the debt by dying on the cross and God accepted that. He died, rose and I sent him to the side of the father. It's possible to mentally ascend to that statement, to believe that. It is possible to believe that and not be saved because you can believe it, but do nothing with that. You believe that, but it's not internalized. You don't live that. It's not something that is in you. Why? Because what is gonna cause you to keep believing that? What is gonna cause you to remain in that? What's gonna cause you to keep following, keep hearing, keep believing? What's gonna keep you from walking away? What's gonna keep you from not living a life where you're bearing bad fruit but living a life where you're bearing good fruit? What's gonna do so? Well, it's gonna have to be one or two things. Either something on the outside that makes you a fortune to do it or something on the inside. Well, we're not in the Old Testament and so it's not like we're gonna have the glory of God leading us and coming down and supping with us externally and having a prophet lead us and so forth and all these different offerings and so forth. We're not gonna have that anymore. What it's going to be, it's gonna be something on the inside, something internally and this is what God has prophesied in Deuteronomy 30.  He tells them first, do so themselves. They don't. As a matter of fact, they can't circumcise their hearts. They don't want to. It's not gonna happen. But God says that I will circumcise your heart and then we see it again in Ezekiel 11. Let's go there. In Ezekiel 1119, he says that I will give them one heart. This is what he's gonna do in the future, of course, as we're reading this, that future has arrived. I will give them one heart in terms of when I say arrived, let me clarify. It has arrived for us. And it's not arrived fully for the Jews. We'll deal with that at another point in time, but he says I will give them one heart and put a new spirit within them and I will take the heart of stone out of their flesh and give them a heart of flesh that they may walk in my statutes and keep my ordinances to do. They remember what we talked about in Luke 8. What does the word say? And let's go back to Luke 8 one last time not one last time, but let's go back to Luke 8, verse 15. Those that received the word, they did it with a, they hold fast to it in that good heart. So this good heart is not our work, it's his work. God is the one that brings about this good heart, this new heart, how? By taking his spirit, putting it into our heart and giving us a heart of flesh, remove this heart of stone. He also makes the same statement going back to Luke 8. I'm sorry, not Luke 8, but to Ezekiel. And let's go to 36. We've covered this before, because I will sprinkle clean water on you and you will be clean. I will cleanse you from all your filthiness and all your idols. Moreover, I will give you a new heart. There it is. And put a new spirit within you and I will remove the heart of stone from your flesh and give you a heart of flesh. And I will put my spirit within you and cause you to walk in my statutes and you'll be careful to observe my ordinances. And so he's saying what he will do, God is the one that's gonna do those things. As a matter of fact, Jesus bears witness also in John 3. He says to him in John 3.3, truly, truly, I said, that unless one is born again, the word here is, Genetheanothim born from above, born from the spirit of God, he cannot see the kingdom of God. So the first thing that has happened before salvation takes place is you have to be born from above, born again. And he uses three ways of saying it, born from above or born again, which is born of the spirit. The other way he says it is born of warden spirit. The other way is born of the spirit. They all three mean the same thing. And that's not a work that you do. That's something that God does. As a matter of fact, Paul bears that also in Titus 3. He says that he saved, that's God. He saved us, not we ourselves, but he saved us, not on the basis of deeds, anything that we could do, which we have done in righteousness, not even faith, but according to his mercy, by the washing of regeneration and the renewing of the Holy Spirit. So even the faith that we would have, we can't take credit for that because he did so by his mercy, by what regenerating us and the word that's used there, this word for regeneration, by the washing regeneration, is Palin, which is again or above, again Genomai, which is to be born again. The same thing that we see in John 3. The same thing we see in 1 Peter 1, 3 won't go there, but he says that God cost us to be born again. So the heart change that we need to have that's necessary for salvation, where the word is sown in our hearts. If the heart is a bad heart, it doesn't matter. But in our case, if the word is sown in a good heart, then it does matter. So let's go back to Luke. And so this is why verse 15 makes sense now. As for that in the good soil, they are those who hearing the word, hold it fast in an honest and good heart. So you gotta have that. But I wanna go over a couple of things that was stated earlier.  Where does that come from? Well, as a matter of fact, let me put something in the scriptures really briefly. I wanna take us to Romans. And let's go to chapter 11, verse 25 it is. He says, I do not want you to inform, this is Paul speaking of Israel, because they have these blinded eyes. He says, I don't want you to be informed brothers of this mission so that you will not be wise in your own estimation. But look what he says that a partial hardening has component Israel until the fullness of the Gentiles has come in. So they have this spirit of stupor that's over them. They cannot hear, they cannot see. They have this partial hardening. There are some Jews that do through God's sovereignty, but overall Israel has not. But it's been given to some to hear, to some to see. And so this is what he's speaking of in Luke 8. You can believe, but the believing is temporal. As a matter of fact, how we know it's temporal because we'll go back to verse 12. He says, the ones along the path are those who have heard. Then the devil comes and takes away the word from them. Well, first of all, how does he do so? That part is not totally clear other than to say that there's various different ways we can go about doing it that he can go about doing it through trials, testing, through wishing people's ears, whatever it's different things that will come our way to test to see that we are actually here. He's not actually reaching in someone's heart and pulling the word out. That's not what he's mean. This is really kind of idiomatically to say that he takes it from their heart. He's not doing it physically, but he's causing it to happen through other means. Or just speaking to someone, you can get enamored with other things of the world. And we see these different examples that are brought up in Luke 8, get cared. I mean, you can start caring about the riches of the world and so forth.  The reason why, the reason why you're not hearing it, is it's kind of pushed out because it hadn't taken root in your heart. There is no depth of soil for the word because why it was not sown in a good heart? Because look, here's the reason why he wants to do so. He says he wants to do so, so that they may not believe. Hina may pistosantes. This is in order that not they will be believing.  In other words, when the Bible refers to us as believers, he refers to us as people who are in a continual state of believing, this participle of an ING. So he doesn't really refer to us as someone that believe duh temporarily. He refers to us as someone who is believing. And Jesus makes a statement in John 6. He says that if you are believing at that moment, then get what you have. Eternal life, life right now going on for forever. How can he make that statement? Because you are in a state of believing. Why is that? Because you have a good heart and it's the Holy Spirit that's in you. Remember, the Bible says that he who began and could work in you, that's God through his spirit, he is going to complete it. He's that faithful. It's his spirit that's gonna keep us, as Ezekiel said, keep us walking in his statutes, keep us believing, keep us following, keeping us hearing. So once it happens, it's a foregone conclusion. It's a done deal. We are going to keep believing. The devil, however, wants to do the very best that he can to keep us from believing. He doesn't want us to be believing. Bad English, but hopefully you get my point. He doesn't want us to be believing. Why? Because to be believing would mean that we would be saved. So the devil wants to come and take the word as best he can so that we won't be believing. Well, how can he do so? He can only do so if the seed that's sown is sown on a bad heart, a heart that has not been regenerated. If the seed is sown on a good heart, there is nothing the devil can do. Now, the reason why this can be a difficult subject is because it necessarily deals with the fact that it is God's work at play first and foremost. The preeminent factor in this is God's work in our heart. That's the most important thing, what he is doing, what he has done, and that he is the one that's gonna see us through. Does this also deal with the whole issue of internal security? It absolutely does. Because again, that's the whole goal that we would be believing. So I hope this is helpful. I hope this shed a little bit more light on this parable. We go over this parable a lot, or at least sometimes. And sometimes we don't really flesh out what it's really saying, but hopefully as we just look at other scriptures, how it's leading up to this, how it fits in with what Jesus is saying. Hopefully it makes more sense. If you guys disagree, please let me know. I'd like to hear your comments on the other side. In the meantime, guys, be blessed. Amen.


Hi everyone, Joe for jazby's casebreaks.com. Hello. Hello. Hello. We're about to do some panini mosaic uefa euro Soccer hobby edition two box random country break number 33 one spot gets you two teams and At a pretty discounted price do the math on that it's pretty nice big. Thanks everybody here for getting there's all the Countries big. Thanks everybody here for getting in on the action Let's double you up one spot gets you two countries There's all the countries right there. Let's roll it randomize it six and a two eight times for names and countries one two three four five six Seven and eighth and final time. Yeah, we got a few soccer newbies here jazby's regulars, but soccer newbies here so After eight we've got a John down to Joe So I think maybe Rex Oliver and Logan we have to help them out crew Six and a two eight times for the teams one two three four five six Seven and eighth and final time. We got Hungary down to the Netherlands All right, John with Hungary Oliver with Poland John with Denmark Maria Malia with Sweden John with Finland Maria with Russia Jennifer with Italy Oliver with Portugal That's pretty good Rex with Turkey in Slovakia Joe with Belgium Steve with Spain David with France Steve with England Michael with Wales and the Ukraine John with the Czech Republic Jennifer with Scotland Michael with North Macedonia and Germany David O with Switzerland Logan with Austria and Croatia and Joe with the Netherlands now anyone want to Make some deal any trades. Let's order these teams alphabetically Don't think there's gonna be too many trades, but We'll give it a few moments. We'll keep the video running. We'll keep we'll give it a few moments here Yeah, last Bob Mojo is real Oliver got last Bob Mojo ended up with Portugal There's there's a few nice players on Poland as well like Robert Lewandowski is Polish And obviously Christian Ronaldo for for Portugal Diago Jota either as well John's got either one of his up for trade Czech Republic Denmark. Yeah, Rex has Slovakia and Turkey Kind of smaller countries. I feel like there's like a It's got to be a couple Slovakian players that are pretty solid Hey, listen if you get like a low numbered card a one-of-one or something like that a gold vinyl that'll be pretty nice No matter who the player is Logan would trade both of his teams for Portugal. That's Austria and Croatia Croatia was in the I think in the finals for the last World Cup Michael's gonna attempt a North Macedonian Wales and Ukraine a three-for-one deal Yeah, that's a good try Michael, but I think I think as much as much as Oliver doesn't know soccer. I think he knows Christian Ronaldo I Don't know if that's gonna happen Alright, it looks like no trade. Let's roll. Let's see what we got. All right TWC trade window closed. Let's print and rip Yeah, all hers like I think I'm good the final print out here hot off the presses Thanks, everyone for spending a bit of your Sunday night with me. Here's the final print out right here And again, I appreciate everybody rallying around this break and make this happen. I'd be happy to run this back too I think this is only a 12-spot break and there's some Some low-key good stuff in here. I think soccer can can be a little Can be a little underrated So give it a shot and all card ship So for those of you who don't know soccer all cards will ship. It might be a fun little project kind of kind of quickly do a little Little research on east to see where some of these What some of the values on these are especially if you get like parallels of rookies You'll buy again seeds. Well by the first spot get the ball rolling. That would be a big help. All right, here we go There's Joe feel ish. I mean this could be a big player All right, this is not his rookie car business. This is a Portuguese youngster coming up the ranks Jordan Pickford There's Diogo Diogo Jota Who's on my club liver police court a goal today? both for Portugal Mason Mount Or am I thinking a Mason Graham maybe Mason Greenwood is anyway Mason Mount for the three Lions for England and then we've got Lucas Masopost One out of 49 for the Czech Republic and that will be for John John with the Czech Republic. We got Jaden Sancho silver Nice one for England Steve with the three Lions Feel like I mean they got to the Euro finals. I know it was disappointing for them But a lot of youngsters who are probably by next year would be nice to have another year of Footy experience under their belts The next World Cup might be one of England's best chances to win it all for the first time since 60s our next little stack here. We still have not seen the autograph yet should be Coming up shortly another Jaden Sancho. That's just base edition though. The silver is obviously The bigger hit and a lot of a lot of these cards You know definitely worth worth grading to especially stuff like the Jaden Sancho silver Nice a mosaic pattern Eduardo come a vineyard For the blue for France. That'll be for David. Oh, he's also a bit I forget what club he plays for. He's also a pretty big name and that's a rookie card of his too France is another team with a bunch of youngsters on that squad He plays for Real Madrid a mosaic pattern. That's also a pretty big hit too. I want to say All right, here comes the autograph It's a dama triore a little happy face going on there as well That's for Spain. I forget what club club team he plays for he plays for Wolves Wolverhampton is the English Premier League club he plays for He's on the he's just a 25 year old kid playing for the Spanish national team of Spain. Yeah, that will be for Steve Kim nice an autograph on the board for you and These are And all card ships. It'll be you'll be getting all this stuff. All right Next box. These are very quick two box breaks one spot gets you two countries We don't need too many people to run this break back And I think it's just a even if you're not like a big soccer collector You may stumble into a nice hit and be able to resell it for a lot if you get the right teams Obviously just like any other break, but But it's pretty inexpensive and then everyone's familiar with the mosaic design. I think everyone's enjoys mosaic So that's something you can give it a shot if you want to tonight. Jaspy's case breaks calm. All right Here we go. Thank you for the fill. Good luck It's Jack real ish just a base card of his And a Christiana Ronaldo mosaic pattern nice parallel for Portugal Oliver Jumping in on a soccer break for funsies. It's great dot great dot nicely. It could be a nice hit There's Bucaio soccer Another England youngster Place for arsenal. There's Mason Greenwood. There's Trinkau Rookie mosaic. It's for Portugal. I'm a fan of the Virgil van Dyke. I'm not sure what this is value that Netherlands, but Joe The big center back for Liverpool He's healthy and I think that has made all the difference in the world and Makes all the difference in the world for Liverpool success. I mean From a solid back all the way up to the front You've got a good spine 54 out of 99 for the Ukraine Igor Karatyn blue parallel For Michael, I know Oliver never let him forget Rex will try to try to pretend like he goes hitless all the time, but there's there's some killing in Bapé Just a base version for France David. Oh Still a great player though, and we've got Nico Williams For Wales the Welshman going to Michael and Wales and I'm almost certain that Nico Williams is a Liverpool defender He kind of filled in admirably for yeah Liverpool kind of filled in admirably while during the Liverpool defensive crisis of the last season So there's our last autograph. Let's see if we can find some Some big parallels before we're at the end of this box There's another come a vignette For David Oh, and the blue Joe feelish There's a Poland's Robert Lewandowski red parallel montage and Pitch Masters Tony Cruz for Germany and that my friends is that thank you very much for getting into 2020 2021 Panini mosaic UEFA Euro soccer is a hobby addition to box Random country break number 33 another two boxes of hobby in the store if you want to check it out and I'll break some more footy with you next time. Bye. Bye. Jasby's case breaks calm


Personal Finance Powerpoint Presentation, Asset Back Security ABS. Prepare to get financially fit by practicing personal finance. Most of this information comes from Investopedia Asset Back Security ABS, which you can find online. Take a look at the references, resources, continue your research from there. This by James Chen, updated October 9th, 2021. In prior presentations, we've been looking at investment goals, investment strategies, investment tools, keeping them in mind. We're now asking, what is an asset back security, an ABS? An asset back security ABS is a type of financial investment that is collateralized by an underlying pool of assets, usually one that generate a cash flow from debt, such as loans, leases, credit card balances, or receivables. So often on the investment side of things, we're typically looking to have a diversified portfolio. We might be putting some of our money into equities, into stocks, which have a level of volatility that might be higher than fixed income, such as bonds, but which has a potential possibly for a greater gains. Then we might have some investments in fixed incomes, which could include something like bonds, could include other asset backed types of securities. When we invest in something like a bond, we are in essence basically loaning money to the issuer. We can think first, possibly of government bonds, because they're a good tool to compare against because they have very low, if not zero default risk, the likelihood that they don't pay back, basically the bonds. And then we can take a look at corporate bonds, which have a little bit more risk involved in them and so on. And then we can look at other types of investment strategies and tool, asset backed security ABS, looking for another way to help kind of support or secure the investment with that asset backed security. So it takes the form of a bond or note, paying income at a fixed rate for a set amount of time until maturity. So the format of it, the structure of it, similar then to a bond or fixed income type of instrument we're investing in. For income oriented investors, asset backed security can be an alternative to other debt instruments like corporate bonds or bond funds. So fixed income investors, possibly those that want that part of their portfolio or possibly those that are in like retirement or something like that, looking for that fixed income because it's what they're gonna be living on. So understanding asset backed security, ABS is, asset backed securities allow their issuers to raise cash, which can be used for lending or other investment purposes. The underlying assets of an ABS are often e-liquid and can't be sold on their own. So pooling assets together and creating a financial instrument out of them, a process called securitization, allows the issuer to make e-liquid assets more credible to investors. You got these assets that can't easily be bought and sold because they're e-liquid and you're gonna be putting them in such a structure that they can't be more liquid in essence, being able to be buying and selling them more readily. So it allows, it also allows them to get shaker assets off their books, thus alleviating their credit risk. The other underlying assets of these pools may be home equity loans, automobile loans, credit card receivables, student loans or other expected cash flows. Issuers of ABSs can be as creative as they desire. For example, asset backed securities have been built based on cash flows from movie revenues, royalty payments, aircraft, landing slots, toll rules and solar photovoltaics, which I'm sure they're really creative on that one. I think they just made up that word entirely, but then they made an investment strategy on it and somehow so in any case, just about any cash providing vehicle or situation can be securitized into an ABS. So for investors buying an ABS offers the opportunity of a revenue stream. The ABS allows them to participate in a wide variety of income generating assets, sometimes as noted above exotic ones that aren't available in any other investment. So that's a definitely exposure to some diversification that you might not get on the standard rotation. So how an asset backed security works, assume that company X is in the business of making automobile loans. If a person wants to borrow money to buy a car, company X gives that person the cash and the person is obligated to repay the loan with a certain amount of interest. So they're financing the car, you would think the car would be used as collateral on the loan and so on. Perhaps company S makes so many loans that it starts to run out of cash. So now they're selling their cars, they got a cash flow problem in their business, they're making revenue, but they need a cash flow component. So company X can then package its current loans and sell them to investment firm X, thus receiving the cash, which it can then use to make more loans. So if they sell the loans bundling, basically sell the loans, I can, they can allow them to liquidate or get the cash flow from the loans at the point in time they needed for their cash flow needs. So invest possibly buying more cars, obviously and so on, so they can keep growing. Investment firm X will then sort the purchased loans into different groups called trenches and the trenches contained loans with similar characteristics such as maturity, interest rate and expected delinquency rate next. So now we're sorting the loans out into similar characters. So investment firm X will issue securities based on each trench it creates. Similar to bonds, each ABS has a rating indicating its degree of riskiness that is the likelihood the underlying loans will go into default. So then you gotta of course look at these different loans and kind of put them into categorizations and try to determine what the likelihood of default is so that we can get some idea of risk involved here. Individual investors then purchase these securities and receive the cash flow from the underlying pool of auto loans, munis on administrative fee minus an administrative fee that investment firm X keeps for itself. So obviously it's gonna take some cost on the investment firm to be structuring these items. Special considerations, an ABS will usually have three tranches, class A, B and C. The senior trench, A is almost always the largest trench and is structured to have an investment grade rating to make it attractive to investors. So obviously we would like the higher investment grade rating typically, which would be the more secure investments to have a more assurance on the income stream. The B tranche has lower credit quality and thus has a higher yield than the senior trench. So obviously when you're looking at the B area, you're saying, okay if I have the opportunity of going to the less risk or the more risk, if there's more risk involved, I expect to get a greater return. So you got a greater return possibly here, but then of course you take on the greater risk along with it, the C tranche has a lower credit rating than the B tranche and might have such poor credit quality that it can't be sold to investors. That's not good. In this case, the issuer would keep the C tranche and absorb the losses. Types of asset-backed securities theoretically and asset-based security, types of asset-backed securities theoretically and asset-based security ABS can be created out of almost anything that generates an income stream from mobile home loans to utility bills, but certain types are more common. Among the most common ABS are the collateralized debt obligation, the CDO. A CDO collateralized debt obligation is an ABS, which is an asset-backed security issued by a special purpose vehicle, SPV. The SPV, the special purpose vehicle, is a business entity or trust formed specifically to issue the ABS, the asset-backed security. So there are a variety of subsets of CDOs, which are the collateralized debt obligations, including collateralized loan obligations, CLOs or CDOs made up of bank loans, collateralized bond obligations, CDOs are composed of bonds or other CDOs. Structure finance-backed CDOs have underlying assets of ABS, residential or commercial mortgages or real estate investment trust, REIT, REIT debt. Cash CDOs are backed by cash market debt instruments, while other credit derivatives support synthetic CDOs. Collateralized mortgage obligations, CMOs are composed of mortgages or more precisely mortgage-backed securities, which hold portfolios of mortgages. Through a CDO is essentially structured the same as an ABS, some considered a separate type of investment vehicle. In general, a CDOs own a wider and more diverse range of assets, including other asset-based securities or CDOs. Home equity ABS, home equity loans are one of the largest categories of ABS. Those similar to mortgages, home equity loans are often taken out by borrowers who have less than stellar credit scores or few assets, the reason they don't qualify for a mortgage. These are amortizing loans. That is, payment goes towards satisfying a specific sum and consists of three categories, interest, principal and prepayment. So when you think about obviously the flow of the loan for an amortizing loan, each payment usually is gonna be consisting of a portion interest, a portion principal, and you could have then the prepayment in effect as well. So auto loan ABS, car financing is another large category of ABS. The cash flow of an auto loan ABS include monthly interest payment, principal payments and prepayments, though the latter is rarer for an auto loan ABS and is much lower when compared to in home equity loan ABS. This is another amortizing loan. We've got the credit card receivable ABS, credit card receivables, the amount due on credit card balances are a type of non-amortizing asset ABS. So we don't have the same kind of amortizing table, for example, when you're paying back, say a credit card loan, you pay back basically the minimum payment basis is required and so on and so forth. So they go to a revolving line of credit rather than toward the same set sum. So they can't have fixed payment amounts while new loans and changes can be added to the composition of the pool. So the cash flow of credit card receivables include interest, principal payments and annual fees. There is usually a lockup period for credit card receivables where no principal will be paid. If the principal is paid within the lockup period, new loans will be added to the ABS with the principal payment that makes the pool of credit card receivables staying unchanged. After the lockup period, the principal payment is passed on to ABS investors. Then we've got the student loan ABS. ABS's can be collateralized by either government student loans guaranteed by the US debt of education or private student loans. The former have had a better payment record and a lower risk of default. And ABS will usually have three tranches. You've got class A, B and C. The senior tranche A is almost always the largest tranche and is structured to have an investment grade rating, a good rating to make it attractive to investors. The B tranche has lower credit quality and thus has a higher yield than the senior tranche. So once again, more risk with this with the less quality investment possibly comes along with a higher rate of return that could be possible but more greater likelihood for loss. The C tranche has a lower credit rating than the B tranche and might have such poor credit quality that it can't be sold to investors. In this case, the issuer would keep the C tranche and absorb the losses. What is an example of an asset backed security? A collateralized debt obligation, CDO is an example of an asset based security ABS. So it is like a loan or bond one backed by a portfolio of debt instruments, bank loans, mortgages, credit card receivables, aircraft leases, smaller bonds and sometimes even other ABSs or CDOs. So this portfolio acts as collateral for the interest generated by the CDO which is re-appaid by the institutional investors who purchase it, reaped by the individual investors who purchased it. What is asset backing? Asset backing refers to the total value of a company shares in relation to its assets. Specifically, it refers to the total value of all the assets that a company has divided by the number of outstanding shares that the company has issued. In terms of investments, asset backing refers to a security whose value derives from a single asset or a pool of assets. These holding act as collateral for the security backing it in effect. So what does ABS stand for in accounting? In the business world, ABS stands for, quote, accounting and billing system and quote, what is the difference between MBS and ABS? An asset based security ABS is similar to a mortgage backed security MBS. Both are securities that like bonds pay a fixed rate of interest derived from an underlying pool of income generating assets usually debts or loans. The main difference is that an MBS as its name implies consists of a package of mortgages real estate loans. So you're kind of more restricted on the mortgage backed securities to obviously real estate loans. In contrast, the ABS is usually backed by other sorts of financing, student loans, auto loans or credit card debt. Some financial sources do use ABS as a generic term encompassing any sort of securitized investment based on underlying asset pools in which case an MBS is a kind of ABS. Others consider ABS's and MBS's to be separate investment vehicles. So there could be some ambiguity in terms of the classifications between the two as you could see could be some crossover. In other words, you might say, well, an MBS is an ABS, but an ABS is not necessarily an MBS, right? So how does assets securitization work? Assets securitization begins when a lender or any company with loans or a firm with income producing assets earmarks a bunch of these assets and then arranges to sell the lot to an investment bank or other financial institution. This institution often pools these assets with comparable ones from other sellers, then establishes a special purpose vehicle, an SPV, an entity set up specifically to acquire the assets, package them and issue them as a single security. The issuer then sells these securities to investors, usually institutional investors, hedge funds, mutual funds, pension plans, et cetera. The investors receive fixed or floating rate payments from a trustee account funded by the cash flows generated by the portfolio of assets. Sometimes the issuer divides the original asset portfolio into slices called tranches. Each tranche is sold separately and bears a different degree of risk indicated by a different credit rating.