Hello and welcome. My name is Shannon Kemp and I'm the Chief Digital Officer of DataVersity. We would like to thank you for joining the latest installment of the monthly DataVersity webinar series, Advanced Analytics with William McKnight, sponsored today by CouchBase. Today, William will be discussing assessing new database capabilities, multi-model. Just a couple of points to get us started. Due to the large number of people that attend these sessions, you will be muted during the webinar. For questions, we'll be collecting them via the Q&A section, or if you'd like to tweet, we encourage you to share highlights or questions via Twitter using hashtag ADV analytics. And if you'd like to chat with us or with each other, we certainly encourage you to do so. To open the Q&A panel or the chat panel, you'll find those icons in the bottom middle of your screen for those features. And just to know the chat defaults to send to just the panelists, but you may absolutely change that to network with everyone. And as always, we will send a follow-up email within two business days containing links to the slides, the recording of the session, and any additional information requested throughout the webinar. Now let me turn it over to Rick from CouchBase for a brief forward from our sponsor. Rick, hello and welcome. Sorry about that, Shannon. I was muted. No worries. We're not seeing your screen right now. You stop sharing. All right. Let me get that back on. All right. Good to go. Looks good. All right. So thanks a lot for that introduction, Shannon. I'm going to take this opportunity to quickly tell everyone a little bit about CouchBase, which is a multi-model NoSQL document database. So I'll also be talking a little bit about the CouchBase analytics service, which helps our clients perform analytics on real-time data. And then I'll talk a little about some use cases and customer successes. All right. So why CouchBase? Well, CouchBase is a little bit different. We're a single platform that includes capabilities and services that support different functional requirements in a single multi-model database, which obviously helps to reduce vendor sprawl. CouchBase is fast. The memory-first architecture, elastic scaling, automatic replication and synchronization provides fast performance from the edge all the way to the cloud, even as we scale. We're also flexible. Data is stored as JSON documents. That gives developers the flexibility to dynamically update the data structure as the application needs change. So as the application grows and the needs change, you can update the schema as the data is read into the database, as the data is read from the database, which is much faster and a lot more flexible. CouchBase is also familiar. It's designed to make the transition from the relational to the NoSQL world easier. So our customers can move from their relational traditional databases to a NoSQL database, but they can still leverage skills like SQL. And they can also duplicate the relational database models within CouchBase. For example, schemers and tables in the relational world are available in CouchBase as scopes and collections.  Capabilities like multidimensional scaling allow users to configure clusters based on the workload. So you can configure your cluster based on the type of workload you're running, which helps to minimize wastage. So you're not wasting resources, you're utilizing all your resources, which in turn allows you to be more effective and more cost effective. Alright, so we've got three different options for CouchBase. The first option I'm going to talk about is CouchBase server, which is a self managed offering, and it's available on all the cloud vendors. This gives our options a lot of control so they can maintain control over their data. And it also gives them the custom ability to manage their workloads as they wish. And then they can leverage their existing DevOps teams and DDAs because those skills can transition over to CouchBase. And they can also implement their own management strategies and tools. And generally, our customers deploy CouchBase server using Kubernetes. Then we have CouchBase mobile, which is an offline first data access database, which allows peer to peer syncing. So the IoT devices can peer to peer sync with each other, and then sync back up to CouchBase server when they have access to the server. We also offer automatic data conflict resolution, which is very important because as you gather data from these edge devices, it can sometimes be difficult to determine which data is the most current. And then we also CouchBase Capella, which requires no administration, it's a D-Bass offering, and it's very easy to start and start building remote applications, meaning mobile applications, and also conventional database applications. The setup is fast and easy, maintenance and upgrades are handled automatically, and that allows for a faster time to market, and then the returns on TCO. Basically, you can get performance from less nodes with CouchBase, which helps to drive down your environment costs. So let's talk a little bit about the CouchBase Analytics service specifically. This service allows isolation of transactional data from analytical data, which helps to speed up the processing on both sides. So you have separate nodes for each group of data, and therefore each processing group is done much more quickly. Each service is able to perform faster. The separation means that the transactional jobs and analytical jobs can run in separate environments. So again, you can do things like complex analytics, joins, aggregations, etc., on a shadow copy of the data that's in your operational environment. And both of these services support SQL querying. So that helps to shorten the learning curve because you don't have to learn a proprietary query language like you do with some other platforms. The data in CouchBase is saved as JSON documents, which means that developers can assign structure when the data is returned from the database. So ETL required. You don't have to transform the data as it's being ingested into CouchBase. You can assign a schema as the data is read from the backend database. Also, a lot of our processing is done in memory. So which means CouchBase is a lot faster. And then all our nodes are equal. We don't have any management nodes. So all nodes are available for work, no node wastages, which obviously improves our efficiency and ultimately lowers TCO. So what are some of the requirements for an analytics platform? Well, it needs to be timely. Well, most organizations, modern organizations are data driven. They need to be able to analyze data and extract information very quickly. And they need to be able to make decisions on the data that they're generating and then analyzing. So CouchBase helps to solve that problem by making your operational data immediately available, which improves your flexibility. I talked a little bit earlier about the ability to assign a schema when the data is read as opposed to when it's ingested. Again, this helps to improve speed. And then CouchBase is also scalable. So both your analytics service and your data service can scale up as needed. This diagram does a pretty good job of explaining the CouchBase architecture. So as I mentioned earlier, the analytics data is housed on separate nodes than the data service data, than the actual data from the operations of the company. So we've got separate data nodes for each set of services. As you can see here in the middle box, you can run your operational apps on the data service and then you run your analytical apps on the analytics service. Users can also join data from disparaged data sources. So for example, here on the lower right, you can join data in Azure or in S3 to your CouchBase analytics service and then query that data from the analytics service, which is obviously very important. And it's a very good perk to have, right? So you can have data sitting in S3, even say CSV files, you can link that data to your analytical data in CouchBase and then search both those data sets from within the analytics service. And then we also have connectors for BI tools to visualize your data. And we have a native CouchBase Tableau connector, for example, that you can use to visualize your data in CouchBase. Alright, so let's talk about some customer stories. I'm going to focus on this e-commerce example. Basically what we have here is a need for real-time marketing. Lots of organizations want to be able to market in a timely fashion to their customers. So they need to analyze the dynamic data and they need to do it in as close to real-time as possible with the goal of creating professional marketing campaigns and then reducing the time it takes to execute their ML models on their analytical data. So in practical terms, CouchBase is able to help our customers reduce the time it takes to create these targeted marketing offers. And then we can enhance the ability to gather insight from their customers and determine trends. The whole point is to make it faster for these companies to react to their customer needs. Alright, I'm going to run through these examples because we're running a little bit low on time. One customer that uses CouchBase analytical service is Domino's and again they use it for real-time marketing. We're able to help them reduce the time it took to run their ML marketing models. So they have models that they need to run on their operational data in order to determine how to market towards their customers. We have that data separated into CouchBase Analytics.  Another example is that of the Cincinnati Reds. Again, I'm going to just quickly summarize this. They needed real-time analytics also and we're able to provide that for them and help them to increase their customer retention and also the reporting capabilities within the organization. Alright. And here we have a few customers who utilize CouchBase. As you can see, we kind of run the gamut. We've got customers across various sectors. We help them to improve their user experience. As I mentioned before, reduce cost and then speed up their time to market for their analytical applications. Alright, that's about it. Thanks a lot, Shannon. I'm going to turn it back over to you. Thank you so much for kicking us off and thanks to CouchBase for sponsoring and help to make these webinars happen. If you have questions for Rick and about CouchBase, you may submit them in the Q&A portion of your screen and he'll be joining us in the Q&A at the end of the webinar. Now let me introduce to our speaker for the series, William McKnight. As he has advised many of the world's best known organizations, his strategies form the information management plan for leading companies in numerous industries. He has a prolific author and popular keynote speaker and trainer. He has performed dozens of benchmarks on leading database, data, lake streaming and data integration products. And with that, I'll give the floor to William to get his presentation started. Hello and welcome. Hello, Shannon and welcome everybody. Thank you so much, Rick, for kicking us off here. It's a pleasure to have a strong database that's in the area that I'll be talking about today. Here is the sponsor that being CouchBase. Today we're going to talk about assessing new database capabilities. I guess they're still kind of new. And that is multimodal or multimodal. You'll hear me say probably both things you'll hear both things set out in the industry. Essentially it's the same thing so something to get used to more terminology. So when did this all start this idea of multimodal well in 2012 the term multimodal database was coined by Luca Garooly. He's saying that wrong during his keynote presentation at the NoSQL Matters Conference in Cologne, Germany. And the beginnings were traditional SQL database solutions, starting to add support for the JSON data type. I remember this as NoSQL became more prominent widely adopted in the early and mid to 2010s. I think it's a pretty important topic why because is it are we destined that our architectures will forever get more and more complicated and will be adding more and more vendors and more and more products to it. It sure seems that way. So whenever I see a little pocket here of, well, maybe we can do some consolidation around that I really look hard at that because our architectures are getting pretty complicated out there and I think I've spent some time in in past sessions talking about that and all the layers of the architecture and so much more than it used to be so where we see an opportunity for a database to actually handle multiple data types. I think it behooves us to check that out. By the way, you gotta gotta buyer beware here, because who's not multimodal out there multimodal out there. I went to four conferences last month, and mostly put on by database vendors, but either way there was a lot of database vendors at them I always seek them out and of course I have my usual briefings that I'm taking from database vendors leading up to this presentation I'm asking them about their multimodal capabilities and oh yeah they have they have all these multimodal capabilities out there right. Now I think that some of the models that are part of multimodal. You have to have certain a certain level of capabilities for really to be enterprise grade, and really for it to make sense within your enterprise for you to even consider it for a true enterprise. There are some capabilities that you need within all the aspects of the models that you are going to use in these databases so buyer beware be careful. Everybody's multimodal to some degree but we're going to talk today about some criteria that you want to apply to the models to make sure that it's good enough for you. That's a little bit more about me. I've been introduced. Keep in mind that a lot of what we'll be talking about today has to do with coming from the no sequel marketplace. No sequel now not all of the formerly known as no sequel vendors are still embracing the term some are, but I like the term so I'm going to use it. And it has to do with those databases that are not straight up sequel against relational databases alright. So it's a little bit about McKnight consulting group we offer strategy training and implementation for making data into the asset that it needs to be for your organization and we've done this for several global 2000 organizations as well as the mid market to high degrees of success. So if you have any questions about your architecture technology, your roadmap, your organization. Let me know maybe you can help. And these are some of the clients that we have done this for a lot of finance a lot of health care but really we cover all verticals, as far as that goes now you're out there making a lot of decisions today. I know you are. And I know it's more complicated than ever to be in this business, because there's, there's so many failure points where if you get one layer of the architecture wrong out of 10, you're still bringing the whole thing down or at least limiting the capabilities a bit and it's like I said more complicated than used to be there's an unprecedented variety of data store choices to meet the needs of varied workloads there's no one size fits all that chip is sale, maybe it'll come back. Now I see glimmers of hope for more consolidation beyond what we're talking about here today. That would be nice but today is not that day enterprises have many needs for databases including cash operational data warehouse master data ERP and so on plus plenty of there's plenty in the operational area by the way that we can itemize out here but we all know databases the enterprise without them I don't know where enterprises would be still working with flat files I guess. While vendor offerings have exploded in recent years and do time frameworks will integrate components and what amounts to a single offering yeah that's what I was talking about a single offering. So if price performance offerings for adjacent workloads in an enterprise have materialized and I'm here to say that buyer beware but I believe that some of them have and let's take a look as we go ahead. No one size fits all once again. Just to pick on some of the data types we're talking about here cash cash database, which we don't always think about it's not a straight up relational database right. It's the smartest database and the trade offs of expensive fast in memory storage and slower storage. Internet as an internet example might indicate it's selection is all about access speed, it must have some millisecond response, and it must hold its speed as a high number of users pound the database now I'm talking about things as if you must do this you must do that always put the lens of your enterprise on it. But I do believe that once you get into one of these areas you're going to go where a lot of my clients have gone where a lot of the industry goes in terms of, you know what you need so multi model. It's a pretty loose term out there. So, let's try to put some flesh on that there are many data types. Web crawlers, open link data in no particular order here. Jason. Yeah, pretty predominant like I said, a lot of this multimodal business came because there were Jason databases emerging and relational databases said hey, we can take that on as a data type and do some things with it. XML kind of same thing there. XML not as big in favor today as Jason but still there of course documents. We'll talk more about that as we talk about document stores binary files being your video audio that sort of thing. Graph. We'll talk about that log files log files is is huge log files list actions that have occurred and web servers maintain these long files listings, every request made to the server with log file analysis tools. It's possible to get a good idea of where visitors are coming from, often they return and how they navigate through a site. And hopefully the rest of these are pretty straightforward. Let me mention web crawlers that might be new to some people it's a internet bot, which systemically browsers the web, typically for the purpose of indexing the web. So like another term for it might be spider. So anyway, these, these are some data types that we're trying to get a handle on within the organization, and we can just put it in a good old relational database good old legacy. So why rows and columns database. Why do we need something else why did the no sequel phenomena emerge, and this must have been by guessing and putting a year on it right here now that maybe a dozen years ago or so. When this really emerged and gave us some real options here. So why no sequel why not just straight up relational databases. Well, you get more data model flexibility. You get more services as a data model, there's no schema first requirement you load the load data first, and load what you got, and hopefully you don't make a mess of it, and load too many incongruent data types into one of course there's still some design left and no sequel databases people forget this you get faster time from date acquisition relaxed acid that's atomicity consistency isolation durability. You know all those things that you need for good transaction processing. Incidentally, some multi model databases ensure acid guarantees across all data stores which is much harder to guarantee an individual databases. So, even though I say yeah relax acid that's a good thing. Some vendors do it and do it well and it doesn't really impact performance anymore, but it used to be used to be that none of these had acid low upfront software and development costs. It's true for a lot of things beyond no sequel when it comes to the cloud programmer freedoms fault tolerant redundancy and linear scaling. So there are many ways that no sequel design solve problems more efficiently than traditional SQL and relational systems. In many cases, those systems require complex processing that can be avoided by no sequel systems. The use of document orientation for example avoids one of the most complex pitfalls of application, the mapping between objects and relational systems. This is known as the operational relation object relational mapping problem. Okay, why no sequel let's let's just keep on here. These are some of the things that were fundamental to no sequel and that's distributed file systems. Of course, this is true for Hadoop. This is true for cloud storage as well. We have multiple nodes and blocks placed across those nodes strategically, we won't get into the algorithm too much here today. But the policy is based on a copy written to the node creating the file written to a data node within the same rack, and a third copy written to a data node in a different rack usually three. And we can change that of course, I usually want to leave it at three. And the idea being that you are now down to 0.00. I don't know how far I want to go out here. I don't have the ability that any that you'll lose any data, and that's obviously very important underpinnings of the entire DFS ecosystem, your design goals you want to scalable to thousands of nodes. Assume failures are common they're going to be more common with this type of commodity hardware target this towards small numbers of very large files. And right once read multiple times. These are highly scalable that to thousands of nodes and massive files. We're talking hundreds of terabytes to petabytes that can now be stored in these no sequel databases, and they don't use mirroring or raid they have other mechanisms, namely the one I just showed you the two dedicated blocks to deal with a wide variety of failure types, and the secret sauce of the whole thing is that they will quickly restore their fault tolerance and they will quickly restore. If something goes wrong, so load balancing fast access and fault tolerance for underpinnings of the entire no sequel movement. Now let's get into some of the no sequel databases and capabilities and I hope that you are thinking today about these capabilities in context of the database that you're working with. Is it truly multi model. Does it have these type of case these types of capabilities if they even claim graph. If they don't claim graph, and you need graph, and you probably do. That would mean you probably need a separate graph database okay so therefore there's one less opportunity for great consolidation there. Now the property graph, there's really only a couple out there, Neil 4j is kind of dominant in the space, but it's, it attacks some of the same problems that we're going to see on the next slide when I talk about the semantic graph now. This is a bit of a property graph model, I've given a whole advanced analytics presentation on graph databases. So, you know, I'm, I have high affinity for them, a lot of use for them that I can find in an organization you can to whenever there are relationships whenever they're important, because you can relate nodes by type and direction, and you can have name value properties. So, this is a property graph here, you see there are, why it's a property graph, there are properties on the relationship so this person named and apparently in the upper right, owns the Volvo. She owns it that's the property, the person in the upper left Dan drives the Volvo so drive is the property and then there are, there can be other attributes assigned like he's done that since January 10 2011 etc etc that's a property graph and then there's a semantic graph and they are different in how they attack largely the same problem although semantic graphs tend to be a little bit more scalable. And obviously the storage is going to be different there are more limitations I would say on a semantic graph and there's plenty more vendors of semantic graph and this is really taken off in the past few years so look for your need for this in your multi model database look for your need for this in the enterprise the data stored as what's called an RDF triple store, which is three elements working together. It's a semantic databases only work with RDF. It is users of third party data in RDF that was the initial target market, and now it really works across all data sets and sparkle SPAR QL has the equivalent functionality to the language that we might use in the property graph like cipher and examples of semantic graphs like our Lego graph and Eureka I think linked open data is linked data that is open content, we don't need to be concerned too much about that, but if we have graph problems in our organization. We need a graph, we need a graph solution, don't try to force fit this into your relational database and I think that's part of my message for today. Don't try to force everything into the relational database unless it's a multi model database, and it can do all these things. Yeah, I'm leaving a lot of judgment on the table for you because, well I can't help it. That's the way it is this is a complex job and, frankly, I think it's only going to get more complex for quite a while, the way things are going. The mass entry of vendors into the space that we're in and so on exciting times. So databases are multi model when they can be either, for example, a key value store or a document store. And that's probably kind of a low hanging fruit when it comes to multi model key value plus document or document plus key value. And I'll get into document and key value explain what they are. Key value example might there's a key, and then there's everything else you have to access everything by the key, the timestamp for example in this in this example timestamp is the key couch base is a multi model database for example, because it supports multiple data models including key value document graph and search and others. A lot of what I find in terms of what drives which platform to use which data model to use. It depends on the data type. And, yes, of course it does depend on the volume of data that you have for that data type. The more volume might drive more robust solutions, you can get away with less robust solutions if you have the lower levels of volumes of the data types that aren't your core data types. But, generally speaking, if you have CSV CSV or web logs, that's going to be an either a column, or a document store, and I'll explain all these as we go along documents and a document store, Jason document store, metadata catalog column or document, key images and documents, key value, and RDF and link data as discussed a graph store so your data type will drive a lot of the model that you need to use again is try not to force fit things you don't have to force it anymore. Let's start with keep well continue into key value stores. I almost said start with because this is sort of where a lot of the no SQL marketplace began. This is no sequels OLTP equivalent. As a matter of fact, as a side note, I will say that I believe that a lot of these no SQL databases are taking the reins from relational databases when it comes to operational databases, operational databases of course they're still databases are still relational for the for the most part but I do see quite a bit of modern applications using no SQL databases in place and maybe that'll be clear as I talk about this a little bit. OLTP is pretty simple. There's not a ton of functionality it's fast. It's an associative array data model. There's a key and there's a blob pair I say blob even though it can be columns so to speak, but the columns are really not accessed individually. And for many that's a knockout factor that's a problem, but if you need high levels of speed key value is for you, you retrieve value given a key, all accesses by the key. The difficulty is that your application cannot run arbitrarily selection arbitrary selection queries like select splat from table. And so it needs to know where to look for objects in advance. And that can be pretty limiting but if you're, again, trying to deal with high volumes of data, trying to access it fast maybe you can deal with that these are databases like react redis mem cash Berkeley hamster Dynamo project of Alderman open source and Amazon Dynamo DB. Yeah, all the major hyperscalers have products in this space. All right, key value stores continuing on here they are technically horizontally scalable fast, very fast resilient to cluster failures, simple, and all nodes are equal there can be thousands of TPS per CPU core you can use indexes to look up keys. React for example uses solar. All data stores do a hash of the key to determine the location in the cluster, which obviously that's part of the secret sauce of being able to find the rest of the record, based upon the key. It's good for any single objective unstructured data blobs speed wherever speed is important like in multiplayer games online games period shopping carts, it can handle part of that processing pretty well. Geo localized processing where you're trying to take advantage of exactly where a person or thing is. It's obviously transitory speed when you can't be down. These are very resilient databases, which is great. And they give you a lot of speed key values often a good choice for serving advertising content to many different web and mobile users simultaneously with low latency. That's probably the main use for content of this sort, e.g images or text can be stored in key value using unique keys generated either by the application or by the key value store itself. And these can get up to 100,000 writes per second. Wow, pretty fast now a lot of key value stores or at least the ones that started out as key value stores are, you know they've moved into multi model, and I'll have something to say about that as we go along here. Now it's time to define the multi model database. Multi model database, it's a single integrated database that can store managing query data in multiple models such as relational document graph key value column store and cash. It is the opposite approach to polyglot persistence anybody hear that anymore. To polyglot persistence that was the idea that we should use multiple databases in a workload, each to its own to its own unique value proposition and stitch it all together, which yeah we still do that for sure. But we do want to limit that the multi model idea is not new. So we have a database used to support multiple workload categories, albeit on a limited basis. What is new. Why I put it in the title is because if they're really capable today, and make sure that what, make sure that your selection, and your expectation of how a solution will work, one of the models is in line with what the capabilities really are, and that they're not just putting band-aids on under the hood. Like for example I know we passed it already but when it comes to graph. It's one thing to be able to access data via graph and use graph algorithms on data. So if under the scenes it's not stored as a triple store, that's going to perform really slow. And at some level of an enterprise workload that's not going to work. Document oriented databases couch basis a document oriented databases database. Key value stores, in other words, they have all the value, all the value propositions of key value stores, but they have added capabilities as well, like the ability to nest sub documents. So the data here stores JSON or XML, largely JSON with the tree light start structure, and your ability to group data together more naturally and logically so key value stores plus different things like the values are queryable. Remember I harped on that as a challenge with key value stores, the values are queryable materialized views yes indexes yes documents are addressed by your eyes, these support rest interfaces. Good for things like event logging content management, real time web serving and e commerce. So it replaces SQL abstract programming, where you frequently in SQL you don't have values for things but you still have to store a placeholder for in the relational model. And frequently that's going to be a null or or an empty column sometimes zero, what have you. We don't have to do that when it comes to document oriented databases. The idea is store all data together documents are self describing hierarchical tree structures, unlike key value stores the value part of the field can be queried and that's a big plus. They're good for I mentioned some things, but here's some more they're good for a lot of things they are the general multi purpose. And so these are, I would say, the dominant model for no sequel, and a great place to launch off into the other models as a vendor of a document oriented database so the strongest, the strongest let me say this right the strongest multi model databases come from a document oriented background. And in case it's not all clear. This is a document example, baking recipe, the type mama's cornbread you see the ingredients you see it's nested blah blah blah we won't be making that cornbread today but you can see what some of the ingredients are for that if you do make that let me know how it goes couch base has elastic scalability always available. Global deployment, some of the things that Rick mentioned before it's a key value store where the value is a JSON document which makes it a column store. If not JSON it's a 64 byte string, the JSON is eligible for indexing, and there's no extra step of taking the database down to change the schema or anything like that. There is a I could go into this in detail I'm going to try to hold back here but I'm excited about document database okay and the hash there's a hash part where they have an even distribution of the data. So the data is distributed based on the hash there are data buckets and they have this. They have this algorithm that there's so many buckets and it's mapped into a certain number and blah blah blah, and it's really a beautiful thing how the data gets distributed. You can have multiple no SQL solutions working together this is that poly got persistence approach, and you would use a key value store for the shopping cart and session data document or column store for consuming completed orders. A good old relational database for inventory and financials and a graph store for customer relationship for marketing. You could use a good multi model database, and that's part of the point here today the mission critical store in all of this frequently just does compact come back to relational key value pairs are good for fast and simple document oriented for flexible models and modeling and column stores for time series data let's get to that column stores are data models, also known as big table with frequently with column families where you can group different columns together and that data will be stored contiguously it's kind of like a column database in terms of how that part of it is handled. It produces used for querying and processing very light schema, but it's pretty close to a relational database, as far as that goes far as how you handle it. It's optimized for column wide operations like count sums and averages so if those are very important part of your processing, you might consider a column store. Cassandra a big one their H base and hyper table among others. This is good for large amounts of data data that needs compression event logging content management systems, the data model support semi structured data. And like I mentioned before, time series data, the data where you want to keep either the last X minutes or the last X generations of the data and then you don't want anymore. It's like weather data for operations location data of things sensor data if you're grading out the readouts and it's not data that you necessarily want to keep around forever although, although I do find that some organizations are flowing the data from column stores to a data lake for more history I won't say all time history but for more history so that they can apply artificial intelligence to that data, and hopefully improve their operations column stores utilize block compression, using different compression algorithms like gzip and LCO this is best for this is good for a multi model launch I would still say that the document stores are good and even better, but key value stores may not be the best place to launch off into multi model. There are a few reasons for this key value may not offer the best support for storing and querying complex data structures key values designed for high performance and low lazy. So it may not offer the best support for data consistency and transactions. And finally, I'll say key value stores are in memory data stores. So may not offer the best support for data persistence. All things you want in your multi model database is like this is an example of column store. You got a row key. Okay, that's kind of there. And then you have what we're showing you here are column families, giving you some definitions here we've got column keys and column values. Looks like we got a profile we got some orders going on for this particular instance can get all related information using a single record ID. Usually they use a random mechanism for the row ID which gives you faster right. And then you have a slow read, which is usually what you want in this age base does things a little bit differently. I believe this is a Cassandra example, each base has different properties at the column family level like the number of versions the time to live the compression technique, whether it's in memory or not. And always is known and specified definition time so I don't want to say you can't change this, but you do not specify the columns at definition in Cassandra, for example, you can you do that when you are writing the records. And we won't go into it a lot more hopefully I've given you some idea about column stores though now multi model databases that support. I showed you should at least support them to the level that I just showed you and then I'm going to give you some things now to look for in multi model databases I got a couple slides for that. I want to see an excellent implementation of multiple models, not an excellent implementation of one model and a half implementation of the rest, because that can really get you into trouble. So counting on your multi model database for let's just say key value support and it's really not there at an enterprise level. That can get you into trouble. You want a single copy of the data. You don't want the data have to be replicated for each model you want model change propagation you change it one place gets changed all places, you want it to work in the microservices world, and you want some millisecond response time. It should be slow. It's non trivial to cover the features of an excellent implementation of any model, let alone multiple models. We're talking years potentially of development work to go from one to the other in a good way. While it's understandable if a platform has a first or an anchor model, of course, look carefully at the implementation of the second and subsequent models to ensure compliance with the best practices of those models. These include high compression, no failures without service disruption, a cost based optimizer, etc, things like that. The ability to scale a multi model solution from one to multiple is crucial. Since a multi model database will typically be deployed with one model most prominent at a time and then you will work your way through other models at least that's how I've seen it done. Almost all of the models in a multi model implementation, all the ones I'm talking about here have been around a decade or more and consequently have a set of factors that make it work well. Look at those for sure. Here's some more things to look for in multi model globally distributed multi region deployments. If you're a cross model data processing language and optimizer you shouldn't have to change your language that you're using to interface with the data, because you're using a different type of model. You want an edge capable database today because there's a lot of processing we can put at the edge. Jason flattening. Yeah, good old Jason flattening without data explosion as a result, and universal indices. Wow. Yeah. Like I said, not easy globally distributed applications need a database that can distribute can distribute globally and transparently replicate the data anywhere to the center that is closest to its users. There's been distributed multi region deployment, a multi model database attempts to embrace the challenge of cross model optimizer by developing a unified query language to accommodate all the supported data models. And I dare say that the optimizer is a big part of the work at moving into multi model. So if a single model optimizer needs an optimizer, a good multi model optimizer will be more difficult to build than a single model optimizer, but data virtualization vendors have overcome essentially the same problem optimizing queries across data vests. So, there is hope. Finally, here's some other things to look for when it comes to multi model emerging technologies, the use of artificial intelligence. And for this to, I want to see artificial intelligence in the solution. I want to know the strategy that the vendor has deployed because I'm buying in, I'm thinking it's very important, and very important to our future to the future capability of the software, etc. So there's a separation with data catalog platforms, because they're emerging pretty strong a robust user experience, of course, we can take the word robust multiple ways but take a look at the UI for sure in a multi cloud or multi, or excuse me, a cloud native type of application multi model databases should help companies leverage the effort they are putting into populating their data catalog platforms for data sourcing rule enforcement security and so forth. And as far as that robust interface should have a modern updated appearance that helps business users easily accomplish necessary tasks. I hope I've taken you from at least at this level through the various models that make up a multi model database, give you some criteria to look for in each one, maybe scratch the surface a bit about where some of them might be applicable within your organization. Then I gave you some criteria to look for in your multi model databases, if you are counting on a database for this capabilities and I encourage you to do so. This brings me to the end of the formal presentation. Feel free to lob some Q&A Q and some questions in there, and I'm going to turn it back to Shannon and Rick and I will pick up your questions. William, thank you so much for another great presentation. If you have questions for William or Rick, feel free to submit them in the Q&A portion of your screen and just answer the most commonly asked questions. Just a reminder, I will send a follow up email by end of day Monday for this webinar with links to the slides and links to the recording. So diving in here. So for a use case such as a road network to graph, as a road network, a graph database would make a good digital twin. How would this work when existing databases for managing the asset on the network are relational? Wow, that's a specific use case there. I'll take a first pass at it and then bring in Rick on this one. I'm not really familiar with that type of, I think you said a road network, I'm not familiar with that, and what that means so It's very literally a road network. I believe work works for, yeah. So ROW, ROAD. Oh, okay, road. Yeah. Well, I mean, there's a lot of functionality when it comes to transportation and with graph databases. A lot of the points of a lot of the direction setting that happens like with a Google Maps or something that's all about a graph database, where there are various points and it takes to go from point to point. When there's 100 ways to go from point A to point B, it can guide you on the fastest path because of a graph database that adds up all the point to points that can possibly get you there. And so anytime something is in transport, definitely you want strong graph capabilities. I will say though that since the the question or through in the relational component to this. I'm not sure there's a lot of great multi-model graph plus relational capabilities going on. I'm even scratching my head trying to think of one. So that may be something that we still have to do it with multiple databases, polyglot persistence. And keep an eye on what on the space to see what develops in that area that that might help you consolidate. Yeah, for my two cents, graph databases are generally used as for link analysis. So as you mentioned, William, for trying to find the shortest distance between two points, for example, graph databases are good for that. In terms of the relational world, I guess you could do something similar in relational databases with your table link ins. But that would tend to mean that you're linking a table back onto itself because you probably have the location saved in one table. So that might be a little tricky in their relational database world. Yeah, it would be self-referencing tables. And, and that can be problematic from different perspectives. What else was I going to say about that before we move on? Well, and he added that we're developing an assessment asset management data standard. Well, asset management usually that's pretty, pretty much your rows and columns type of need there. So that would be a relational database. I will add that a lot of relational databases, even the real legacy ones have added capabilities for graph. But I think that they are kind of what I said during my talk, which is, okay, they may give you the graph algorithms, but they don't really store the data as a triple store as a graph database would. So you will suffer comparatively with performance and keep in mind that graph databases are yes, they are about the linkages between physical items, but they also can draw out relative importance of various nodes on the network. In this case, maybe various assets that are out there on the road. So I think I think you're the, they're onto something that, you know, graph databases are definitely going to help their application. Yeah, what I could add to that in terms of asset management, that may be a use case that coach base could could work well and meaning you could have a document and then all the related documents are nested within that that parent doc. And then that would be easier to search back from the database and also it'd be a lot faster. So you could have nested objects within a primary object. Very nice and everyone's super quiet today. I don't have any current additional questions. But, you know, Rick as line was going through his presentation anything that you want to add that came to mind. Yeah, just from a coach base perspective I think William did mention this also. There's multiple ways of accessing the data so you can access data coach base from full text search you can access it from the analytics service from the data service you can do key value look ups you can run SQL query look ups. So just, I just like to emphasize the fact that there's multiple ways of accessing your data within our platform. Well that is all the questions that we have thank you both for such a great webinar and event. And as a reminder again to all the attendees I will be sending a follow up you want and a day Monday with links to the slides and links to the recording. Really appreciated everybody thanks to catch base for sponsoring and helping to make these webinars happen. Thanks y'all. Thanks, thanks William thanks Shannon. Bye bye.


An Amtrak train heading to Chicago with 200 passengers derailed after striking an unoccupied vehicle on the tracks in southwestern Michigan, authorities said Friday the engineer and approximately 10 passengers received non-life-threatening injuries and were treated by local ambulance services. The Berrien County Sheriff's Office said the train derailed but remained upright. The crash happened Thursday evening near New Buffalo in Michigan's southwestern corner, about 70 miles east of Chicago. The vehicle was stuck on the tracks and was in the process of being removed when the train hit it, the Sheriff's Office said. Passengers were taken to New Buffalo High School. Some were picked up by family and friends while others continued their trip to Chicago on buses arranged by Amtrak, the Sheriff's Office said.


as we have. Okay. Okay. Before we could begin our class, can I request one of us to lead us in prayer? Who will lead us in prayer today? Let me pray. Father God, I come before Your presence in the name of Jesus. Father God, thank You so much for this time so that we can come together in Your name and learn from Your word. You bless our man as he teaches the word of God. And also, Lord, You open the eyes of our understanding so that our hearts are accepted to Your word. And Lord, through this session also, as we learn from the Old Testament, He will give us the important insight through the power of Your Holy Spirit. In Jesus' mighty name. Amen. Amen. Amen. Thank You so much, Zatholi, for your prayer. And it is very important to start the class with prayer because we all know that, you know, it's the Holy Spirit who teaches us. He leads us and He guides us. Okay. So as we depend on the Holy Spirit, we should also depend, as I depend on the Holy Spirit to teach in Him through me. It's so very important even each of us to depend on Him to give us the understanding, isn't it? It's only He can help us understand. He can help us to understand so that we remember all the things that has been taught in the class when we read through our Bible. You know, each and every word has been returned as inspiration to each of us. So today, we're going to study on the book of, which book? The book of Deuteronomy. The book of Deuteronomy, which is a very important book. Okay. So before we could start, I would like to project the book of Deuteronomy, the notes to us. Do we all have the notes with us? We also keep the notes and the Bible ready. So the book of Deuteronomy, the author of this book is, who's the author of this book? We all know. Who's the author of this book? Moses. Moses is the author of this book. Okay. So, unlike numbers, this book, Deuteronomy, was written approximately in 1406 BC. And it was written in the course of 40 years in the wilderness. So Moses put a final form to this book before you could enter the promised land. The book of Deuteronomy literally means the second law. In Greek, it is called as Deuteronomos, which means the second law. And it is the fifth book in Torah, where it is also in Hebrew. This book is called as Deverem, D-E-V-A-R-I-M. In Hebrews, this book is called as Deverem. Why? Because the very first verse in this book starts with, these are the words of Moses. It starts with these are the words. So Deverem means the words or the words of Moses. So it is named after the very first verse of the first word in Hebrew. And this is the first book in the Christian Old Testament. And it is also the fifth book in the book of Moses or the Pentateuch or it's called as Torah. It is also known as the book of transition because it marks them into a four-fold way. In what way? The first one, it talks about the transition of a new generation with the leadership of new leaders. Who are the two new leaders? Joshua and Caleb are the two new leaders under their leadership. This book is transitioning. The second, yes, Moses passed on the leadership to Joshua, but then he became very prominently active. In leading the new generation of the people. The second, we see the transition to a new possession or to a new land they are going. And third point we see transition to the new way of life, a new experience for them. Where they are living in houses instead of tents, a settled life instead of wandering. All these 40 years they have been wandering all around Mount Sinai, now they are going to settle. And even the food they are going to eat would be something different like milk and honey and the corn and the wine. Instead of the diet food that they had at the wilderness. The fourth transition we see is the new revelation of God.  Because from Genesis to Numbers we see when people rebelled what happened, they had to face their consequences. And in this book we see how God was merciful to them. You know how God was merciful and we see Moses himself stating that to the people. Can we turn to Deuteronomy chapter 4 verse 31 and one of y'all can read verse 37. For the Lord your God is a merciful God. He will not forsake you nor destroy you nor forget the covenant of your fathers which he swore to them. Because he led your forefathers and chose their descendants after them. He brought you out of Egypt by his presence and his great strength. So we see in verse 31 it says God is merciful. See Moses is saying the new picture the people are seeing the revelation of God who actually God is. So Moses is portraying God as God is merciful. And then we also see he is saying in verse 37 God is love. Because he loved father therefore he chooses their descendants after them.  See the love of God that has saved you. That has heard the very cry of your fathers and it brought you out of Egypt. And Moses is showcasing God the real God. Because they had a different mindset of God different revelation of God. Moses is saying God is merciful and God is love. So people are getting the revelation of who God is. This is the fourth translation that people would be going through. And we see the the central message of this book is God's divine faithfulness. See that in chapter 6 verse 4 to 5. Can we turn to chapter 6 verse 4 to 5 please? Can one of us please read? The Lord our God the Lord is one.  Amen. Do you remember this verse is very familiar and we also read the same verse in the New Testament. Can one of us please turn to Mark chapter 12 verse 30 and read please. Mark chapter 12 verse 30.  Yes. So what does it say?  It's the same verse. It's the same verse that has been said here. It's also been noted in the book of Mark loving the Lord our God. That's the basic truth. Here we can we can split this in you know three fold statement of truth. The fact here is he brought us out and we also move on. Okay. Here is the worship of God that we need to love the Lord how we need to worship the Lord.  It is very important with this. We will move on to the same chapter. Chapter 6 verse 23 verse 23. But he brought us out from there to bring us in and give us the land that he promised on oath to our Lord for us. He brought us out from there that he might bring us in to give us the land of which he swore to our fathers. Can we split this in three fold statement of truth? The first is the fact that he brought us out. You see that's the fact. Fact is that God brought us out of the land of Egypt and the very purpose we see that he might bring us in into the promised land. That which he promised Father Abraham. He wants to fulfill that very purpose of promising. So God who promised is bringing us back the very purpose behind the fact. And the reason behind both the fact and the purposes he swore unto our fathers. There's a promise involved and because God is a promise keeper. That he made to his children. So to fulfill that covenant God is keeping that promise. So he says that I swore to your fathers. So you see there are three fold in this statement of truth. In this one verse we see the fact, the very purpose and the reason behind the fact and the purpose is the promise. The covenant that God made with his son. So a God is a covenant keeper. Every promise that he makes, he will see to it that he will fulfill no matter of difficult our circumstance can be. But the promise that God made, he will keep it. He's not a man to lie, but he's a God who keeps the covenant. With this we'll see the essence of the law. We'll move on to chapter 10. Deuteronomy chapter 10 verse 12 to 13. Deuteronomy chapter 10 verse 12 to 13. And now Israel, what does the Lord your God require of you? But to fear the Lord your God, to walk in all his ways and to love him.  And to keep the commandments of the Lord and his statutes which I command you today for your good. Amen. Thank you so much. And the same verse has been repeated in the gospel, all three gospels. Can one of you take out Matthew chapter 22 verse 37? Matthew chapter 22 verse 37. I'll just put it in the chat. And one of you all take Mark chapter 12 verse 30. Matthew chapter 22 verse 37. And another person take Luke chapter 10 verse 27. Yes, we have taken Matthew, please go ahead. Matthew 22 verse 37.  Mark chapter 12 verse 30.  Gospel of Luke. Luke 10 verse 27.  Amen. It talks about love, how we need to worship the Lord. Something that is there in the Old Testament, we see it's been repeated even in the gospel. Stating the same thing, how we need to love with reverence, with all reverence, we need to love the Lord our God. This is what is required, this is the commandment.  It is very important, it is a demand that we need to love, love a Lord with all obedience. This love should flow from our heart, like of a child of God.  If this God is dwelling inside each of us, then we need to worship the Lord with reverence.  Giving Him the first place, there's nothing else. There's no other place, giving God the first place and God delights that worship. God expects His children to be dependent on Him and give Him that first place of honor, first place of reverence. When year we see, the fear we see, the fear of God is not to, you know, it's not the other type of fear, like how we fear when we see something bad. Fear means reverence, giving all our self to God, worship God, saying, God, you are control of everything.  We see obedience in this book of Deuteronomy. The word called obedience is the keynote. Almost in every chapter, this word occurs and it occurs more than 50 times, saying that God, you know, we need to obey God in all our ways. Now, why should we obey God? Why should we obey God? Three things. For what He has done for us. Second, He is God. Third, He is a God of holy. The law that He gave is perfect. We need to worship God. We will just go through our notes. We will go through each chapter, the division of each chapter and after this, the purpose. We will first go through the purpose and the unique feature and then I'll take you all through the chapters. The purpose of this book is to give detailed instruction about God's law and his covenant with Israel. When we went through the book of Genesis, we saw how the Israel was formed. And then in Exodus, we see the redemption. And then in the book of Leviticus, it talks about the sanctification, how we need to be sanctified because our God is a holy God. And numbers tells us the direction of God. And in the book of Deuteronomy, it gives us the instruction, the law of God. And it also exhorts Israel to pay attention to God's instruction, which is very important. And when we keep the word of God, there's blessing. There's blessing in obedience. And also in disobedience, there is curse. Because we see that in the book of Deuteronomy and the consequence of disobedience. Also Moses clearly states in this the reward for obedience and punishment for disobedience. The unique features we see in this book is just as Leviticus Deuteronomy places great emphasis on the word of God, which is very important. And we also see Jesus, when he began his ministry, how we quoted during the 40 days after his fasting, the Bible records a three temptation of Jesus and the wilderness. And each time he quotes the scripture from the book of Deuteronomy to overcome the temptation. If one of us can read the quote from Deuteronomy, Deuteronomy chapter eight verse three, and one of y'all can take up Matthew chapter four verse four. Again, Matthew chapter four verse seven, Deuteronomy chapter six verse 16. Matthew chapter four verse 10 and Deuteronomy six verse 13. We see the same verse has been repeated. Maybe we can read only the book of Deuteronomy so that we know we have read the gospel, right? So we can compare to the verses. First is Deuteronomy chapter eight three. Deuteronomy allowed you to hunger and fed you with manna which you did not know, nor did your fathers know that he might make you know that man shall not live by bread alone, but man lives by every word that proceeds from the mouth of the Lord. Amen. You see the word man shall not live by every man shall not live by word but that proceeds from mouth, but by every word of God. Man shall not live by bread alone but by every word that proceeds from the mouth of the Lord. This is what it says. And the next verse six 16. Deuteronomy chapter six verse 16. Do not test the Lord your God as you did at Massa.  It's so very important. Do not tempt the Lord your God. These are the very quotes that Jesus quoted when he faced the temptation in the wilderness. Next verse 13. Deuteronomy chapter six verse 13. You shall fear the Lord your God and serve him and shall take oath in his name. Amen. You shall fear the Lord your God and serve him and shall take oath in his name. Praise God. These are the words. And also Moses prophesies, prophesies over Israel saying what are the consequences, the victory that they would face and what are the consequences that will happen to the Israelites. And we see that some of the prophesies been also fulfilled. We see victorious entrance into Cana. And we see that in the book of Joshua and the sin while in Cana, in the book of Judges and Second Kings it's been recorded. And again the Israelite will be taken into exile. We see that in Second Kings and also in the book of Ezekiel and Daniel. Then the return from exile in chapter 30, we see that in the book of Ezra and Nehemiah. With this we will move on to the outline. Outline we can go through our own. There are sermons here, sermon topics which we can take. The blessing Deuteronomy 28 is the chapter of blessing and also the curse. Very important. We have heard many testimonies come out of this chapter when people have claimed the blessing of God from this chapter and also they have obeyed by keeping the commands and the statutes of God. They have experienced the blessing. It's not only then, it's even now. And the final words of Moses we will go through chapter wise. I'll just present. There are 34 chapters in this book. The chapter 1 to chapter 11 talks about Moses opening speech. And chapter 12 to chapter 26 we see the collection of laws. And chapter 27 to 34 we see Moses final speech before his death. So we see there are two speeches in this book. Two speeches. The man your speaker is on. Sorry about it. Thank you so much. There are 34 chapters in this book. And this book is divided into three sections. The first is from chapter 1 to chapter 11 which records Moses opening speech. And we see from chapter 12 to chapter 26 we see the collection of laws. From chapter 27 to chapter 34 we see Moses final speech before his death. So we see that there are two speeches recorded in this book of Deuteronomy. Then this book is also divided in two parts. From chapter 1 to chapter 11 we see looking to the past. What happened? What is the background? And from chapter 12 to 34 we see looking to the future. Moses is showing what they have ahead of them. Very important. And the very purpose of this book we went through. So the book of Deuteronomy begins with Moses standing in front of this new generation. People in explaining the Torah. We see in Deuteronomy chapter 1 verse 1 to 5 because of time very few scriptures we will read. But then I will just explain. I will give the summary of each chapter as we explain. So in Deuteronomy chapter 1 verse 1 to 5 we see that from here the design, the very purpose of this book unfolds. Deuteronomy is a series of speeches from Moses where he is calling the next generation of Israel to be faithful to the covenant with their God because it is very important. So he summarizes the story so far and he highlights how rebellious the previous generation that was their fathers was in contrast of God's constant grace and how God provided in the wilderness. It's not that they don't know. They have experienced it but still Moses is reminding them so that they will remember. They will not forget. So Moses had to again and again remind the children of Israel how God was faithful. How God was constant grace saved them, provided them in the wilderness and God did bring his justice on them. But he did not abandon them. But then he kept his covenant promise and rescuing them. Though their parents rebelled against God. Yes, that's the reason that they could not enter the promised land. But then God did not put an end to that generation. He said because you all said you may not enter but your children will enter the promised land. So he was God showed himself so gracious that you know I will bless your children because that was a very promise. I will bless their children's children. So God wants to bless the Israelites. And he keeps that promise and until the older generation pass out other than Joshua and Caleb. Everyone else have died in the wilderness. And after this comes a series of very passionate sermon we see in chapter 4 to chapter 11 where Moses calls the new generation to be more faithful than their parents to the covenant of God to the command of God. Where he reminds them the 10 commandments and then he enters the centerpiece of the section of the 10 commandments. He's saying that listen Israel can we turn to Deuteronomy 6 chapter 4 to 5. We already very important message. Can one of us please read Deuteronomy 6 verse 4 to 5. We read again we can read yes. Chapter 6 4 to 5. Here always pray the Lord our God the Lord is one.  Amen. Moses is asking them to read this section which is called Shema in Jewish language. Shema means listen Israel.  And this became the daily prayer of Judaism the Jewish people. The word called listen here. Listen O Israel. Here O Israel is a word called Shema in Hebrew which means here. Listen listen intently. Includes also to what you hear very important for us to hear and obey listen and obey we need to obey. So this is what the Jewish people started praying this prayer every day every day. And also the word love here in Hebrew it's it means it just not means the emotion or the decision. It does not mean the emotion or the feeling but it means the decision that we need to make wholeheartedly to love our God with all our heart mind and strength. It is a decision that we need to make it's not only to the Jewish people but today even for us we need to make this decision. That Lord I love you with all my heart with all my soul and with all my strength it is very important.  And the other key idea of this world Shema is that the Israel was called to obey and be devoted to the Lord alone. In Hebrew Shema is translated as the Lord is one. We need to obey him. In context of the point that the Lord is one God Israel is to worship and obey this one God. And now as Israel is prepared as Moses is preparing the Israelites to enter into the promised land of Ghana where people is instructing them not to worship any other God. No idols and represent there's only one God the Jehovah God that we need to obey him and worship our Lord our God with all our heart mind and soul. Because he is a redeemer and he reminds them of how God redeemed them from Egypt and how he is leading them again and again he is you know he is again and again retreating the blessings and obedience and the curses in disobedience. And with this we come to a larger portion of the law at the center to chapter 12. Chapter 12 to chapter 26 to chapter 12 to 16 chapter 12 to 16 it covers Israel's worship. So the opening the opening chapter in chapter 12 we see how Israel's worship of the God the way to have one central temple where one God would be worshiped and also God was to be worshiped and Israel's care for its poor. They need to be mindful of people. For an instance where all Israelites were set aside one tenth of the annual income to be given to their temple that's the title we call it. But another tenth they need to keep it aside for every three years and give that to the poor. And these are the kind of laws that was put to Israel and you know of justice and comparing of the ancient neighbors and it was all bound with their worship to God. So worshipping God is not only like with the reverence with all our mind heart and soul but they have to do something by the offering by one tenth of the first fruit of the offering to God. And also to keep certain portion that is one tenth in once in three years to give to the poor as well. You see God is mindful of even the poorest of the poor.  Who are the poor? They are among us. They are neighbors. We need to be mindful of them as well and see to it in their need. You know we are there to help them in their need. And the next section we see from chapter 16, the second half of chapter 16. It gives the Israel leaders so that there are elders, they are priests. It talks about the leaders. There are elders, there are priests, there are kings and these were all placed under the authority of the covenant law which God said that he would enforce by sending prophets to keep the leaders accountable. So in contrast to the Israel neighbors where kings were thought of as a divine and a law in Israel leaders were subordinate to the law and the prophets. We see in many instances as we study each book we see how they follow and they kept the law and how they were subject to the prophets as well. Following this a large portion is from chapter 19 to chapter 26. We see the civil laws and the social justice been enforced. Israel civil law was so to rule about the rules about marriage, family, the business and also about the social justice. You know Moses sets a law for all this and he writes a legal system of how it has to be protected, how we need to protect the widows, the orphans, the migrants. And then these are the concluded by the Moses laws about worship. Now with some tips for reading all these laws for us to remember in two ways. The first we need to remember them as the term of Sanai covenant given specifically to the ancient Israel living in the culture. That's very different from us. And the second we see it's helpful to compare these laws with the modern law from the very different culture. So we need to compare these laws with the Israel's neighbors like the people who were living around them like the Assyrians, the Babylonians. And when we do that we see this law seem to be very harsh but becomes much more clear to see that God is pruning Israel to a higher level of justice that was ever known before. But then we see finally God trying to discern where he's trying to discipline them. He's trying to correct them. He's trying to show them how holy God was. And in the New Testament Paul is quoting in 1 Corinthians chapter 9 verse 9. Can one of us please turn to chapter 9 verse 9? 1 Corinthians chapter 9 verse 9. What is written in the law of Moses, you shall not muzzle an ox while it dreds out the grain. Is it oxen God is concerned about? So Paul is quoting about not to muzzle the ox, muzzle the ox while it dreds out the grain when the same verse is also quoted in Deuteronomy 25 verse 4. Do not muzzle the ox. So while we discern what core principle of wisdom or justice in any particular law we will discover some real profounding things in this book where how to lead our self in the sight of God. With this we will move on to chapter 27 to 34. Moses final speech about his death after Moses goes through all of the laws. He issues a final challenge that Israel should listen and to love their God. And he issues a warning and the challenges that they would be facing if Israel listens and if Israel does not listen and disobey. What are the curses and the warnings? What are the challenges they would go through? He shares it and if they only obey and listen, what are the blessings? How God will bless them greatly and this divine blessing will always rest upon them. On the other hand, he says if you rebel you will come out, you have to face the famine, plague, devastation and ultimately the exile from the land. So he places both front of them, the blessing and the curse. We see in chapter 30, verse 15 to 20, Moses forces a decision. He says today I said before you the life and death, the blessing and curse, goodness and evil. So choose life. See what a leader is. So Moses is not only a leader, he's also been the prophet and he's able to foresee the people because he's been living with them for decades now. So he understands the people's nature, the attitude within emotion. Yes, he's able to understand right now people are saying yes is with the emotion, the gratefulness of possessing the promised land. So they agreeing that they say that they will obey the Lord. But once they acquire the blessing of God and you know how the people's heart would be. They may forget the God who delivered them, they may forget the God who has blessed them. So that's the reason again and again and again Moses as a leader, you know, as he has heart for the people. For then he discerned, he interceded with God to give life. So he's looking at his children, you know, each and every Israelite are like the children of Moses with the father in his heart. He's looking at them and he's telling them listen and obey. And he's also prophesying over them what will happen in future when they rebel. They may have to face the consequences and they may be in exile. But in all that he also gives them the promise saying that God will not leave you.  If when you're a rebel and go into the exile and during that hardship, you will look up to God.  He will lead you back to the true life where it has promised to be. And these are the promises which Moses is sharing with his people before he could die. And this is the promise that he's giving to each of us today. Our God is a God who will never leave us nor forsakers, but he loves us with everlasting love. He loved them so much, that's the reason he gave Jesus to die on the cross to redeem the people. Because our God is a God of love. With this we see in chapter 31 to 34, the passing off of thoughts, the passing over the leadership from Moses to Joshua. We see Moses ending the speech with a poem of warning and then a blessing. And then he walks up on the mountain and he dies. So chapter 31, he hands over the leadership to Joshua and also he gives the instruction to the Levites. And in chapter 31, verse 24 to 30, we see Moses instructs the Levites. And in chapter 33 we see the blessing of the tribe of Israel and in chapter 34 we see the death of Moses. So before he could die, he goes up to the mountain and God shows him the land that he would be giving to his children. And then Moses is 120 years old when he's dying and the Bible records saying that his eyes were not dim. We see that in chapter 34, verse 7, we see that Moses was 120 years old when he died and his eyes were not dim. Nor his natural vigor. He was all in good health when he died. And no one knows where God buried Moses, but no one knows where exactly he died. He went on the Mount of Morab. That is what has been recorded and there he dies and God buried him. And let's see the comparison of Moses' life quickly. The life of Moses with Jesus. We can compare Moses with Jesus. He spent 40 years in Egypt and then he spent 40 years in Median. And he spent 40 years leading the children of Israel. And he was a man of faith because in the book of Hebrews we see he's been recorded in the chapter 11. And he also appeared with Christ and Elijah on the Mount of Transfiguration. We see that in the Gospels, all three Gospels, Gospel Matthew, Mark and Luke. And he was Israel's greatest prophet. And he was like no one I've seen God's glory like Moses did. And now we see his comparison with Christ. Moses is an outstanding type of Christ. Moses was born and was sought to be put to death by Pharaoh. Jesus was born and sought to be put to death by King Herod. Moses appointed by God to deliver Israel out of bondage. And we see here Christ was sent to deliver all Israel and all who believe from the bondage of sin. Moses was sent to lead Israel towards Canna, the Promised Land. And we see Jesus came to lead us to heaven. Moses lead them to see the Promised Land and Jesus takes us into heaven. Moses gave us the law but Jesus fulfilled the law and gave the Gospel to us. We see Moses was the mediator of the first covenant. And in the New Testament we see Jesus as our mediator. Moses did many wonderful miracles. We see Jesus also did many wonderful miracles. Both of them did with the power of God to show God's power and glory. Moses instituted the Passover in the New Testament. Jesus was a Passover. Moses was a faithful servant. Jesus was faithful in all things even unto his death. Moses fasted 40 days and nights in the wilderness before delivering the law. And we also see in the New Testament that Jesus fasted 40 days and nights in the wilderness before he could share the Gospel. The last is, no one knows where Moses' grave is. It should be somewhere in the land of Moab. And in the book of Jude verse 9 we see how the devil and the archangel disputed or contended about his body. Can we quickly do a recap on what we learned from the book of Deuteronomy? Can we do a quick recap on what we learned? Did we learn the unconditional love of God? What he promised with Abraham, God is trying to fulfill, keep that promise despite the rebellion nature of Israel and how God was merciful. God is giving a new revelation that God is love is merciful. All these days the people of Israel never had that revelation of God. They always thought when they rebel they'll be punished. But now God is saying, I'm God of love, I'm God of mercy. You know, Moses is dictating that to people is telling people how merciful and how loving God is and how we need to love God. And we also learn that how we need to worship God. It's again and again the same commandment which Jesus gives us in the New Testament is there in the Old Testament before that itself.  We see that in the Old Testament in the book of Deuteronomy where God is saying, be mindful of the poor who are around you, the neighbors. Be there to help them and offer the first fruit to God. And God is the requirement of Israel to be faithful to God and Him alone because God is a jealous God. We need to be faithful and with all reverence worship Him and Him alone. And we also see Moses repeating the Ten Commandments again to the people even before they could enter the Promised Land. Is there anything else that we learn? Any one point, each one. Life of Moses compared with life of Jesus. Yes. Thank you. Okay. Let's turn to Deuteronomy chapter 30 verse 19 to 20. I'll just take 5 minutes please. Not even 5 minutes. We'll close soon enough. And one of you all please take Ephesians chapter 5 verse 28 to 32. Can one of you all please read Deuteronomy chapter 30 verse 19 to 20. Deuteronomy chapter 30 verse 19 to 20.  Blessings and verses. Now choose life so that you and your children may live. And that you may love the Lord your God. Listen to His words and hold fast to Him for the Lord is your life. And He will give you many years in the land He swore to give you. Your fathers Abraham, Isaac and Sheikah. Thank you. If you all can you'll read Ephesians chapter 5 verse 28 to 32. In this same way husbands ought to love their wives as their own bodies. He who loves his wife loves himself. After all no one ever treated their own body for their, for the feed and care for their body. Just as Christ does the church for we are members of His body. For this reason a man will leave his father and mother and be united to his wife and the two will become one place. This is a profound mystery but I am talking about Christ and the church. Amen. The first verse we see how we need to choose life in order that we may live and our descendants to live. And by loving the Lord our God, by obeying His voice and by holding fast to Him. For this is our life and the length of our days that we can live long.  And in the second verse from the New Testament we see that how we need to obey God and hold fast on Him. And that is the life. Our relationship with God is to be marked as faithful, loyal, love and with devotion. Something and he also illustrates that with the relationship of a marriage. That's a picture of God wants us to cling to God be one with Him. So this is the intimate relationship that God is expecting from each of us today. So I will leave you all with a reflection question. How closely do we cling to God? How closely do you cling to God? Pray and recommit a heart to all that's important in relationship with Him. With this can I request one of you all to please lead us and pray. Dear Heavenly Father, we come to You in the name of Jesus. We thank You for this beautiful day and for the beautiful class that we had. Lord, everything that we learnt in this class, let us praise it in our heart and let us apply it in our life.  This whole life let us cling to You and keep depending on You and keep praising and preaching to You. I place everyone who listen, I bless our man and I thank you for the beautiful teaching that she gave us. So let us apply this and enjoy our life in Jesus name after. Amen. Amen. Thank you. Thank you. God bless you all tomorrow with the next book. Thank you.


You are watching in the studio. My name is Natalie Minya. I'm the director of Tese foundation here in Davis We help students in Zimbabwe to find education and with sanitary packs So our foundation started an event five years ago called hats off to diversity high T and This year we have the African lioness symposium this week Monday November 5th And then the hats off is November 4th So for those events I wanted to invite African women and girls doing amazing things in their fields And we are fortunate to have two of them here today, and I'll let them introduce themselves My name is Sheila Sheldon Chaltz. I Makenyan young artist age nine who fell in love with the art of the tender age of five years Wow, and who is next to you? This is my mom My name is Vivian at the end. Oh, I'm happy to be here We are hosted by Tese foundation and I'm so happy to be here. I am so excited. You're here Thank you for accepting our humble invitation to join us You know, you're an amazing artist as you can see the lion hears your signature Painting piece masterpiece and when I saw your 14 million view video on BBC Africa I knew that I would at least try I know you have a lot of people asking you to be a lot of places But I knew that I really wanted to have you on my show And I know you're an artist a lot of people know you're an artist But some people don't know that you're a designer too So I would love you to stand up and show us one of your pieces you designed and tell me about it this is my favorite piece because I Went with it to the to the president He loved it. That's wonderful. So what inspires you to paint what inspires you to design but mostly I want to hear What what's your inspiration? When I was five years old That's when my mom my teacher noticed my talent and she told my mom about it And I really think my mom for supporting me. She said after that she started having issues in a stomach and She she was the breadwinner of our family we really depend on our father because His work is he's usually called and sometimes is not he's not So I decided that I should stand up for women because my mom had been suffering. She had done six operations Wow and She could not go to work That's why I said I She's my inspiration. Wow That's amazing Vivian. How does it feel?  How does it feel to have a daughter so famous? I feel good, you know We have children and actually you don't know why God gave you that such Child with the such great talent and yeah, I'm so happy for having her cuz She has helped us a lot in the family like we depend on her She really help us like and granted. She's nine years old Yeah, she is what advice do you have for other mothers out there other parents out there that have a child with a Gift and they don't have the gift because I think I've asked you do you draw?  I don't understand. So what advice can you give to to other parents out there to help them nurture their kids talent? to the parents any talent your child might have be it singing like Drawing my girl just started with the sketching and I was like, why are you wasting a lot of time? Sketching you are wasting my ink and the book Yeah, and actually later became something good to me like I was very sick and She could draw and bring food for us like she could bring something on the table So I later noticed that whenever the talent your child have Supporter in everything like in Africa. We used to Tell our children like you should only be a doctor. You should be a yeah like We should do these great great things be an engineer, but I Later came to notice that Any talent your child have please support that's true And look at what's where the talent has brought you here to the u.s. Yeah, I never Been in the u.s. But I'm here because of her. Yeah, what does it feel like Sheila to be in the u.s. For the first time I Cannot believe it Cuz my talent has made me reach far It really has and you know you have a talent you mentioned about painting the president. I couldn't believe it Let tell me how do you come from walking on the streets of Kenya to? Painting at the White House or at the presidential house. I Painted at the streets. So we had been suffering and Then I knew that the president of Kenya really loves children and I decided I should draw for him Well, I was drawing this this girl called Amani. She's a singer. She is she sang Gal on fire and she went Viral on Twitter and Instagram and then I told my mom just decided she'll also put mine And let mine go viral and he found it and he found you And I understand he's even helping you pay pay for your tuition because he wants you to stay in school Yes, that's wonderful. Really. I mean I am so inspired by you. You are such an inspiration to so many People out there. Can you tell me more about your art? And what dreams you have in the future for your art? Where do you see yourself? But I want to know first of all, what's your inspiration for especially something like the lion She has a website and she'll tell you more about it where you can see all the other things. She's painted But what's your inspiration when you see that lion? It's just really Magnificent my art is like no other. Yeah, it's about blend blending and playing with paints and That's why you can see a beautiful lion. It's beautiful. Really. It's beautiful What is your dream five years from now? Where do you see yourself? I will To have a foundation that will help women widows and vulnerable children because they suffer a lot and Just like my mom who is suffering. Yeah had suffered. Mm-hmm. Yeah She has also been dreaming of having a studio like yeah, yeah, she can talk about her studio too like Where I come from many people don't Many children have talents, but they don't have anywhere to practice. That's true My I cannot say I'll teach them outside because many children come to my house and They're not my house cannot accommodate all of them And I cannot also say I'll teach them outside because it the weather of mombasa Right change a lot and my studio will help them I'll help them Practice their talents and also the same studio Will be where I'll put my paints and paint on I can't wait I hope you will give me a spot in that studio one day Will you promise to show me around when I come to Kenya? Okay So you you painted the Kenyan president in a lot of different people you do arts by commission But you painted two famous people here in the u.s. Can you tell me about them? It is allen and opera and they're gorgeous. Yes I've I've been really Longing to meet them because I know if I meet them my life will entirely change That's true. They they have that special talent Yeah, so where will you be this month? I know you're in davis and um, northern california For the whole month, uh, where can people find you? Um, I'll be in tesai foundation. Yes Come and I'll see and you'll see me live.  What inspired you to donate such an amazing piece to our foundation? many children suffer and they don't They don't have anywhere to go to school and I I had experienced that because when my mom was suffering she had six operations and It made me have a heart to give out And I thank you for it our students wait for funds from people like you And you know, there are some ways in which art can change the world My son told me that and she said he said do you know that art can change the world? Look at sheila. She's painting, but her painting is going to be used to change the world Have you ever dreamt that you would be a world changer? No Well, thank you very much. I'm excited that you'll be in the davis sacramental area. She's doing davis art in the bout She's doing a pop-up. She's doing, you know, she'll be at our tea hats off to diversity This sunday two to five at veterans memorial She will be at our first ever african lioness symposium where we'll find out even more about her story At uc davis this coming monday november 5th And uh, you'll be at the brazilian center to november 10 and 11 the brazilian center in sacramental So there are lots of places you can find sheila here in the u.s This month only and of course she has a website and a following quite the following on youtube But I want you to tell them what's your website so they can check out ellen's picture Oprah's picture and all the other things you've painted. You can see me on youtube sheila sheldon facebook instagram twitter At sheila sheldon Yes, or you can promote me through my website page sheila sheldon art dot com Thank you. Sheila. You're so amazing. My name is natalie mania director of tesai foundation You can find us same places. She said and you've been watching in the studio by davis media access. Thank you


US Coast Guard Cutter Healy, Wag 20, conducts a search and rescue exercise in Fugloysen, Norway. Search and rescue exercise build interoperability with allies and partners to respond to emergencies in the challenging Arctic region.