You, my friend, career high in tackles 17 is insane.  So when I saw the staff after the game, I was astonished myself. Logan Wilson, 14 solo tackles. You had a sack too. That was a, I was happy to see that one on Watson. Run a stunt when Logan Wilson inside. Watson never had a chance. Yeah, that was a good one. Finally get that first one of the season under about late in the year. You were mic'd up in this game.  The butt is on fire. Taddy! Tackles, man. It is what it is. Take it easy, y'all. What is that like knowing you're getting mic'd up? I can't imagine.   And now you've got what, like five straight wins for your team? Yeah, yeah, five straight right now. Big one this week, obviously going to Tampa. Yeah, and Tampa brings you Tom Brady. So Greenlaw picks him off last week and then after the game comes up to him and asks him to sign his picked ball. Yeah. So what do you make of that? I mean, we were talking about in the locker room with some of those guys and we're like, if that ever happened, it's be like, we would want to get signed too.  Of course. So if you pick off Tom Brady, are you taking the ball to him after the game and saying, hey, man, will you sign this? I don't know. I just don't know if I would actually do it. It's one of those things where you like talk about it and then you're actually in a situation to do it. You're like, I don't know if I would actually do it, but it would be, it'd be a good time to get a turnover from him. Tannehill steps forward, hooked up in the air, intercepted. Logan Wilson's got it. Do you want to talk Monday night football? Welcoming the Bills to town. And that's a guy, Josh Allen, you've played a game or two with at Wyoming. That'll be fun for sure. I mean, I haven't, we played together, I think for three years when we were at Wyoming. So I had a lot of good times there. And, you know, he's still doing what he's doing in this league and, you know, his development from when he was at Wyoming to where he's at now is unbelievable. We knew he had the ability to, but he was just so raw coming out that, you know, he got in a good position with the coaching staff there in Buffalo and they developed him.  So when you're inevitably in a situation, Logan, where Josh is barreling towards you in the open field, what's going to go through your mind? One, not to get hurtled. He's been known to hurtle some guys. Yeah. He's a freak athlete, truthfully.    So let me ask you, who on this Bengals team on offense would be the biggest headache for you to personally play against? Probably Jamar. He's so crazy good.  He's, you know, I think he's like a receiver in a running backs body.  He's just a force to be reckoned with. He catches the ball so easy, too. I mean, it makes hard catches look easy when they shouldn't be. But the Rams were built to win the Super Bowl and they have shielded the deal. Does this team ever talk about last year's Super Bowl when you're in the locker room? No. I mean, we're just, we have a fire, burning fire within us that, you know, we obviously want to get back and win it, but, you know, we've got really good guys in the locker room and I understand that the past is the past. There's nothing we can do about it. It's kind of like a tease to get there, make it lose and then see what it's like, you know, with the Rams to be able to win that on the opposing field and it sucked at the same time, but also there's a lot of positives, you know, from last year, like you were even supposed to, you know, originally even make it that far, let alone be in that game and it's just, it was a unique experience and now that we have a taste of it, we understand what it takes to get there. What is the ingredient in a team that takes you to the Super Bowl, the most important thing? I would say the biggest thing is unselfishness, as hard as it is, like in the NFL, to have guys that are unselfish. You gotta have guys that are just willing to do their job. When stuff bad happens, we don't point fingers at guys like we, you learn from that mistake and you don't let that mistake happen again. Who's responsible for that unselfishness? I think it starts with Zach, Coach Taylor. He always, you know, emphasizes that. We love playing for him and he's a, he's a player as coach for sure. What do we say, though? I gotta play! Why is it better to be under-rated? Which I think you are. I think you as an entire defense are. I think you as a team that made it to the Super Bowl are being overlooked. I think that last year we were the team that no one believed in, you know, we were the, really kind of the hunters, you know, and now we're kind of the hunted team. And, you know, we've, people have kind of, I would say, fallen asleep on us a little bit, but we don't really care, you know? It's just about us in the locker room and, you know, what we're doing and controlling what we can to get as many victories as we can. All right, it's holiday season. Let's do some brainstorming for gifts. It's not easy to do, well, let's see what we can do together. Let's say we're at the mall. Where are we going and what are we buying for Joe Burrow? For Joe Burrow? Yeah. Oh. That's... Probably to some designer store. Get him a, maybe Cartier and get him some new glasses or something. Whoa! New Cartier glasses. Yeah. I haven't seen him rock those. He had a sharp outfit last Sunday. He's always got sharp outfits. Who picks him out? Him or Olivia? That's a good question. I don't not know. I would have to ask my wife to see what she knows.  You guys just got married over the summer, correct? Yeah, we did. But we got married July 9th. And then camped like two, three weeks after that.  Morgan's the best. Now you're on the Pro Bowl ballot. Politicians ask for votes. Do you want to talk to your Bengals fans here? I mean, I would. I appreciate all the votes that they would be willing to give me. But we have bigger fish to fry. That's right. You have Super Bowl fish to fry in the desert. A desert NFC fish to fry. And we're wishing you all the best luck, Logan. I appreciate you. I hope she can hear me. Morgan through the wall! And good luck down the stretch. You've got Brady. Then you've got your old teammate, Josh Allen. And then hopefully a road to the Super Bowl. Yep. Thanks, camp. Thank you. You're too humble. Logan, you're too humble.


I'm from Los Angeles, California. I'm part of golf company second battalion 5th Marines We're waiting on the flight deck and To get he loaded in by ospreys Well with all our packs and stuff. It's it's extremely cramped like the seats aren't even Really made for somebody to sit on your legs start to fall asleep, and they're trying to stay awake and you hear all the shuttering and all this Noises coming from the aircraft and they're just like what's going on just waiting to get off and then finally about a couple hours later. We finally hit the deck and started the operation. So we just started a movement and patrolled to our next destination, our next checkpoint. We had tanks roll up with us as well, and we have several assets helping us out Air support and such eyes in the sky and When we started taking contact from around six hundred meters off and A couple of my buddies were on the roof and some of the other guys were on the roof as well Tanks were on each side of our building as we're taking contact We all heard like cracks over our heads and impacts around us and stuff like that just taking cover and trying to find a better spot to engage and after my buddies put a couple of tracer rounds in that area the tank started opening up with their 240 coaxial guns and their main guns But when the main main gun opens up a thing is insanity It's just it shakes everything.


So the way that I would do that, one of the ways would be included in our family unit would be to send something home for the children to do with their parents at home. So beforehand you would need to get some paper bags and this is a little note that I've made up that just and you can pick your own items to go to, but this one just says dear family we would like to you to join our family scavenger hunt. Below is a list of categories, help your child find an inexpensive item for each category that he or she can find or can bring to school. Place the items in the bag and we will show the items to the class, then you will send them back home. Have fun searching. So the things that I asked them to bring were a baby item from a family member, a hat from a family member, some junk mail that has their family name on it, a shoe from a family member and a family photo and then I put a date that I wanted them to return these. The good thing about and then you can just glue this little note I ran it off on some colored paper she wouldn't need to and the good thing about this activity is it gets the family involved with them too. So you send that home and then they bring back the items and during a group time you would do what we call the family scavenger hunt and you would let the children share the items that they brought. So and talk about them and talk about the fan how they got the items. So I brought one of my shoes from my mom. So this is my mom's shoe and you can talk a little bit the kids can talk a little bit about their mom and then from the baby item I happen to have a granddaughter so I brought her little pacifier but the children might bring something sometimes their parents have something from when they were a baby or they might have something that they're young enough that they might still have something of their own. The junk mail just has their address on it so that you can talk about where they live and who all lives in that house with them and then I had a hat just a hat that I found in my closet but they would could have one that maybe have some more meaning and a family photo which would show their family as a picture of their family that they can pass around and talk. This is great because it helps the children see like I said in the beginning that there is that every family is different some families have brothers some of the children have brothers and sisters some of them have grandmas and grandpas living in their house every family is unique and different.


Okay, I guess we are ready to go. Camera seems to be on, it's blinking red, so let's get started. Yeah, welcome to our talk, which is gonna be about ArangoDB running on MISOS. So maybe just as a background information for the history of ArangoDB and MISOS, it's been like a really long relationship and those guys have been really, really helpful in helping us to develop stateful frameworks because they were basically the first framework who were really running on those stateful primitives in MISOS, and you'll also see more about that throughout the presentation, but this is kind of like, we have a really close relationship between MISOSphere, DCOS and MISOS and the Arango guys, and this is actually also why I'm here. I'm Yerk with MISOSphere, you might have seen me this morning already, and I'll give this presentation together with Kunal and Claudius from ArangoDB, and I would actually, do you wanna get started? Sure. Thank you, Yerk. Hello everyone and good afternoon. My name is Kunal Kusurkar, I'm a director of solutions engineering at ArangoDB. I joined pretty recently, but I have a history of working in the NoSQL big data events, processing, messaging, ESBs over my career over the last 12 years. So with that, let me quickly give it to Claudius for his introduction, we can start. Sure. Yes, my name is Claudius Weinberger, I'm the CEO of ArangoDB. I founded the company together with my co-founder four years ago, but we started the project, let's say, five and a half years ago, and we're building databases now for 18 years, so we did a lot of different stuff, customer, customized solutions and so on. In 2012, we sit together and thought about should we build another database, there are already a few in the market, but you will see later that we found something, what we call the native multimodal approach, but from our perspective, adds something new to the market and gives us more possibilities. Thank you, Claudius. So let me start off by asking a question, why distributed data to begin with? Can anybody? Good? Hi, am I soft? Okay, perfect. So why distributed data? That's a question I really want to start this conversation off with. Of course, the topic of today is distributed data and distributed infrastructure, so I'm taking the first part and starting off there. The question really stems from the challenge that what we saw over the last decade or so, if you see in track history, what you would see is we have seen a significant amount of growth in global web, cloud deployments and mobile applications, and that brought with it over a period of next, I would say over the last decade plus, it brought an unprecedented amount of data with it. In terms of volume, in terms of velocity, and in terms of variety, and a combination of those together brought in a certain level of combination pressure that really pressured our existing database systems. In other words, the database systems that we know, the relational databases that we know and have worked well, loyally for us for a long time were just not suited because they were not made for it. The new applications that we were building had a completely different requirements in terms of these three Vs and any and all combinations thereof. So what was the frustration? And then what happened overall was the attempts, as it always happens, is to figure out, how are we going to solve that problem? What do we do to solve the three Vs problems that we have? No matter how much hardware you give or how much you optimize it, the monolithic back ends just wouldn't scale up to that challenge to solve it. They were made for a different era with a different purpose for different systems that were siloed at that time and to work on a limited dataset overall. They were really not made for voluminous data. They were not made for a variety of data. They were not made for data with high throughput and high amount of reads. That is essentially, then at that point, what was realized, well, the solution really lies in a way to think different, to think what is really the missing part to solve that problem? And distribution was that answer and following that distributed data. Fundamentally, what solved that problem or what really attempts to solve that problem now in the modern world is a database, is a native multi-model database that will provide a solution in three ways. One, be able to store and serve a variety of data. That's the word, multi-model, meaning you should be able to store any kind of data, the new applications, the web applications, mobile applications. They're not really just working on relational data. They're working on documents. They're working on key value stores. They're working on graph data. And all of that data needs to be used continuously as the applications are being built and as they evolve. And also between them, which means you, at one given day, your application might want to just use a lot of document stores on a given month or after a few cycles of development where you realize, well, my data is more connected. It's more relationship. I'm trying to analyze relationships more than query entities. Well, I need to switch to a graph data model. The existing databases just don't allow you to do that. You need a fundamentally new database that's at the core designed for it organically. And that's the word. That is what makes it an organic, multi-model, native, multi-model database which will support documents, which will support key value stores, which will support graph data structures to begin with. That is the first way to solve the variety of data problem. Now once we attack that, the second is the ability to scale out across multiple machines to handle the velocity needed, to handle the generally great amount of throughput that's asked of you to solve the number of write operations and number of read operations in a given day. You need to be able to be up for that challenge of solving. Third one is the ability to spread out across machines when you need to handle volumes. Your data set is not going to stay the same when you start your mobile business or a web business and two years down, four years down, you're going to see exponential growth in the amount of data you're handling. And you cannot solve that by scaling up machines, giving more memory to make by bigger machines and absorb a higher cost of ownership. You need to spread that data out over commodity hardware on multiple machines and tackle the volume problem as well. And this database exactly attempts to do that by attacking the very need of distributed data. With that, let me introduce RangoDB. So as I spoke, those were the characteristics, the challenges, the realizations upon frustrations and the solution approach. A database like RangoDB defines it. We start off with that value proposition, attacking that problem, a native multimodal database that will provide a unified declarative query language, a simple word, a single query language to query graph information, to query document information, to query key value information, whatever information you store in the database. Scalable and highly available with configurable consistency. At times you need acidity, you need strong consistency. Other times you're probably okay with asynchronous replication. You're okay with getting a dirty read back because that's what your application needs at that time and you should be able to tune and change it as you need. Extensibility and then lastly, I would say, ability to expose your database operations over a microservice framework. The ability, your mobile applications, web applications, they need, they're essentially built with the idea of microservices. Your data tier over these years have not evolved as much. RangoDB solves that. We expose the database operations using an HTTP REST API and that API is also extensible using the Fox microservice framework and you can write service manifest that will go and push directly the information you write and read from the database exposed as microservices. All together really becomes a modern database that you can use to service your microservices based applications. I'll take a brief pause here before I go a little bit deeper and explain each of these features to you. Any questions I can answer in the meanwhile? Any quick questions? All right, so multi-model, I'll go ahead and explain what I mean by that. As I was talking about different kinds, the V, the variety of data, these are all the different types that we have in the market right now. There are point solutions to solve point problems historically like we have seen the relational world, right? Relational tables that were built to solve order systems, catalog systems, but there were other data types that evolved. There were documents, there were graphs, there were columnar stores, time series, key value databases, all of these different kinds of model. RangoDB is an attempt to solve that problem really well and we have taken the approach to solve be a native multi-model database to do two, three things really well. Absorb graph-like information and serve it back really well, absorb documents, absorb key value stores, all in a single deployment artifact. And what I mean by that is a single engine, a single demon that will encapsulate all this functionality and also provide you the freedom to run on all of this on a scale-out infrastructure which mesos can handle. So what do you get with it?  What's the value that you're going to get out of it? A significantly reduced operational moving part overhead, right? There is not much of an operational trouble that you will have to deal with unlike systems that you have seen. Probably there is Hadoop, ZooKeeper, most of these if you're familiar with these technologies bring in a lot of operational clutter, even databases like Cassandra and others, they will bring a lot of operational pain for you to deal with over a period of time. We attempt to solve that with it, with the simplified artifact that you can deploy and deploy across multiple machines and still serve the same workloads without you having to create a new point solution every single time. Faster development cycles. With the unified query language, a single query language, you can query all the information stored in all these different types and even join them with a simple pseudocode-like language. That's a huge advantage from a development cycle, from a time-to-development perspective. And lastly, richer quality applications. With multi-model, with attacking three Vs that we spoke about, you will definitely get an overall advantage in term of building a high-quality mobile application because you have a microservices layer that's really at a data tier. You don't have to deal with it, have to work with it at an application or a front-end side. It's really done at a data tier site for it, scaled accordingly as we will scale the data for you. A significant advantage you'll get out. This is a slightly expanded picture of how things will get deployed from a distribution standpoint. These are the different roles, how we will deploy a RangoDB. The data itself is kept on DB servers, whether primary or secondary, distributed across machines. The microservices can be exposed using the Fox microservice framework, which will run on the coordinator nodes as well. Coordinator nodes can be scaled independently from the DB server nodes, which means you get computational scalability, as well as you get data scalability based on what your application needs are to service your requests. And lastly, the agency is really the consensus mechanism that we have, which will do the job of stepping out of the cluster and overlooking it like a hawk and figuring out how are my coordinators working, how are my machines doing, how are my DB servers doing, and how is the health of everyone? If anybody goes down, it will make sure that it gets automatically started on different machines, or that is a process that you can automate in the way you feel best as well. It is essentially a very hardened way of figuring out what your cluster state is and tackling it as your needs grow. Oh, that is one more second. So, this is actually where Missus is coming in. As you can see, this is like already complex architecture, which I have to deploy and actually also maintain because we're talking distributed systems, there are failures. Each of those instances might fail at any time because the underlying node is crashing, because there is a network partition. So, this is why we actually have to do something about how we're deploying it. And as we all know, we're at MissusCon. Missus is really built for that, but seemingly the HDMI connection isn't really built for it. For, we see already like network partitions happening here, between the laptop and beamer. So, it's gonna happen even more in this big cluster over here. Yeah, so, and this is actually why the Arango guy started out pretty early talking to us in developing like a Missus framework for it. And developing such kind of Missus framework is actually, it's really, really hard, especially we're talking here about a database, developing something, I don't wanna say even like Marathon because Marathon also has like a lot of moving parts by now, but in the beginning it was actually quite simple because it had very little state. But here we're actually talking about a stateful framework which has to be resilient. And so, in the end, you don't have to read all of this, but kind of like the outcome was that we wrote about 5,000 lines of C++ code just to maintain all states. And I think this picture is even symbolizing it better because this actually shows the state diagram we had for all those components. So in Missus itself, they're like low-level primitives for those of you who might have looked at it. It's reservations and then dynamic volumes and so on and so persistent volumes. So it was actually, it was a rather a lot of code we needed to write here and maintain, but now it's actually, it's a pretty good framework. And maybe this is also like one of those key takeaways from writing it. If you really dare to write a framework yourself, I'll tell you on the next slide why you shouldn't, you should actually start out with like state diagram like this, how you want to deal with your persistent volumes next slide. But as said, you actually, you shouldn't be writing your own framework in most cases. Just quick raise of hands, how many of you have either been to the SDK talk or have been to the SDK workshop even? So yeah, you know all of this. So the basic idea is that we don't want people to actually have to write frameworks. We want to generate it for them and this is what the SDK is actually about. So the simple thing we also did, for example, in the workshop, we don't have to do anything. We just have a very simple YAML configuration and we can deploy it. So we don't need any deep knowledge about DCS. We don't need any deep knowledge about the framework we want to run. We simple say run these commands and then the framework will auto-generate such kind of framework scheduler for us. In most cases, also if we're dealing with like a database where we have certain startup constraints or certain recovery operations, it might happen that we actually have to write some code.  But all of those up here, this is actually, this is something I can probably, the highest uppest layer, the default, I can do that within a week. This is probably somewhere within months and how long did it take us to develop the entire framework? Like nine months or so? Yeah, rough, yeah. So that's actually a whole lot different time scale of developing such kind of code. But thank you again for doing it. It was really, really helpful because it actually helped us build the SDK with all the experience we got from this. Next slide. And now that's actually, we talked about the replicated data part. Now let's just talk about like the replicated infrastructure part. Once the slide is not black anymore, next slide. Yes. So we're talking about data center replication and actually we have multiple options for that. So maybe we should first clarify what we're talking about. So we can either use replication or our goal could be to use replication this is like an off-site backup from where I might be able to restore my data. So this is option number one. Option number two is a little stricter requirements. This is like disaster recovery where I actually want to switch over to my backup. So my backup has to be something which can run and also serve queries in the end. And the latest and probably strictest goal or option could be to offer geolocal services and distribution of data. The Beamer is really fun. So in that case that I can actually serve queries from both data centers in parallel, which is good for example, if I have customers around the world, but it's of course, it's also a lot harder because all of a sudden I'm really dealing with hot master, master replication. So basically like the basic idea here is we have a cluster one, a cluster two and some other zone. And now we want to see how we can actually get that going in which different scenarios up there. Next slide. Yeah, so and for the first iteration, a RangoDB after also discussing with us, we decided to go for just to solve the first two options because for many people that's actually sufficient. I don't necessarily have that much load that I need multiple sites serving requests. So actually just being able to recover my data is something very useful if a data center is going down if an Amazon region isn't available anymore for example. Next slide. And so what we decided as like the goals for this first iteration is to run a database clusters in all data centers involved in this replication procedure and then replicate data automatically. This is nothing what I want to do as an operator. This is something which should happen out of the box and then also be prepared to actually switch over to the other data center. So at time point one, all requests are going into data center one, then a hurricane is coming as unfortunately it's happening too often in recent days. That data center is offline, power is cut and I can actually switch over the request to the second data center and then I can still keep on serving queries from the second data center. So the first implementation we are currently implementing or they are currently implementing is to have this replicated Arango DB cluster which includes basically all user settings. So the user settings there also replicated between both clusters and Arango already has a replication API. So we can, we will utilize that together with a newly written tool called Arango sync and then we actually, we looked into different options and what we can use to ship the data over and we looked at different implementations or how much effort it would be to do it ourselves and our decision was actually to use Kafka or more particular called Kafka mirror maker which allows me to run like a distributed replicated Kafka cluster across two data centers. And that decision is actually it's kind of if you looked at all the other talks and this is also why this talk is actually in the smack stack because of a lot of those architectures are starting to use other tools. As for example, Kafka, here we have if you're talking about the smack stack here we would replace the storage part with Arango DB but it's basically we not necessarily have to write all the tools ourselves because we have now 2017 a really great toolbox available of tools to use. And so we use that and this helps us to write load spikes in one data center because Kafka can also queue them so it can just accumulate events as well and it can then distribute them across data centers and even if there's a network outage we might lose some of the events in there but it's still gonna be running and Kafka can also reconnect. And that was a nice thing is that we can actually or natively implement we don't have to do anything to very little to get that is to implement back pressure meaning if the second database is getting too slow the second data center and just can't handle all the requests Kafka can just buffer that and we have automatic back pressure and we can even then pass it on to the tooling around Arango sync to have further back pressure and not overload the Kafka cluster. The TLS protection, we're shipping that across data centers so probably across some communication line where someone else might be listening so we need to make sure that all of this is encrypted. Next slide. And so this is then basically this is similar to the picture before so just these lines there are basically this is the Kafka connection and so Arango sync is just making sure at which time point we are or how much we have replicated and then basically the Kafka is sending us over the data we are still missing as events. And that allows us if that data center, data center A is failing we might lose some of the events which have not been replicated yet by Kafka so which might be in the DB server but have not been written yet in Kafka slash might have even been written to Kafka but haven't been mirrored yet to the second Kafka instance. For most use cases this isn't a too big issue but it's just something you should be aware of in the first implementation. Next slide please. So and this is actually also the limitation and it's basically that it's asynchronous. So as said in the beginning this is targeting the first two goals of just having a backup and having a data center to which I can switch over but it also has the advantages that we quickly get an implementation which helps to solve those first two use cases but it can help in unplanned outages to losing some of the events in the queue. I say unplanned because actually if we plan our outages if we plan to take one data center offline because we wanna migrate nodes we wanna I don't know create a new cluster then we can actually just wait until the Kafka queue is entirely depleted and then switch over. So in that case we can actually do without data loss and yes it's asynchronous as said in the beginning we don't have any load balancing of query so no master master we can't query both clusters in parallel. Next slide. And yeah that's actually it's a good topic to just talk about what are like the current ways and plans for DCS replication across data centers because the same problem you actually have will have for many clusters that you want to distribute that across different data centers or across different Amazon availability zones, Amazon regions. And you have some options. So the first one could be that you actually start spreading out your masters across those different data centers across those different zones and that actually works rather well if you're staying in the same availability if you're spreading out across different availability zones but stay within the same region. Once you start, so this is like Amazon talk if you're thinking about your own data center or Azure or GCE you just have to translate it to the respective names there. It basically tells you you can't spread them out across low latency links but not across high latency links. And why is this case? This is mainly ZooKeeper. Once you start spreading out a ZooKeeper cluster across high latency links you'll end up in some issues. So you should be very careful with that. And that's actually also one of the reasons why Ben in his keynote yesterday mentioned that we want to get rid of ZooKeeper is just to make that more scalable across high latency links. The easiest thing to spread us is actually agents. So we have a lot of users who are spreading out either MISOs agents or DCS agents across, for example, there were at least one talk today about using spot instances and they don't matter too much whether they have a high latency in between or not. So there are even people running their on-prem data center and then extending that with spot instances for spiky workloads because there isn't any synchronous communication required that's all asynchronous so latency doesn't impact it too severely at least. The plans for the future are also to actually be able to link two clusters together. In the beginning it's just gonna be UI, CLI, so most of that control, it's gonna make it easy to control two clusters in parallel but so there are people working on a linker module it's called which makes it like those clusters aware of each other that it actually makes it very easy to support use cases like that. Next slide which I guess is a demo. Yes, this is a demo. So we can talk a lot about it. I'll spin up the cluster for you and then you can take over, okay? So we can talk a lot but let's actually just see also what ErangoDB can do. We obviously for time reasons we won't spin up two clusters and have the replication in between also as this is not quite working yet. So we'll just show it to you on a single distributed cluster instance but already distributed within one data center. So installing ErangoDB is quite easy. The only thing we have to look out for is that there are actually two instances. So ErangoDB is actually the old one we should add a prefix to that probably but we want a new version ErangoDB 3 so we are installing that and let's just have a look what's happening in the background because for those of you who might not be that familiar we see here is the first thing spinning up. If we look at it, this is actually the framework scheduler. So the framework scheduler is a thing which will deploy afterwards all the other tasks and this is running now so rather soonish we should actually see the other tasks spinning up. This is also why it's still unhealthy because the other tasks are still staging and so these are now the actual task which you're doing the work. The first one is kind of like the controller who's controlling all the other tasks in missiles terms, the framework scheduler and then the other tasks they'll be the DB service and controllers starting up. While they slowly come up we could actually check whether we can already access UI.  All right. Service unavailable because the coordinators are not quite there yet. Just wait for one more second. Distributed systems take time but it's still deploying. Let's just wait. Now you need to click on that little icon. I know. Thanks. Just switch back. Do you wanna tell more about the demo you'll be running? No. Now we are coming up. Ah, perfect. Thanks, Jack, for all the stuff you told us about our asynchronous multi-data center application. But what I want to show you a little bit is what would be cluster running on DCS. So first of all, we spin up with two clicks, a cluster on three nodes, DCS cluster. Per default, you're getting two DB servers, two coordinators. And if you just want to add a new one it's really one click. Let's say, and you start another coordinator in the cluster. And what I can already do in the same times maybe start a collection. A collection in a rowing would be the same as a table in a relational database. And you can really define for every collection, first of all, the number of charts. So that's at the end limited scaling. At the end you need one chart at every DB server. And the other thing is the replication factor. And that is also configurable on every collection. So let's start with two for the demo. It's funny. So now we have this collection. This is empty yet. So we can just put in some information. Let's say some by own key in that case. And then just adding some JSON code here. So I'm not used for English to use an English key word. You just want to tell me what I should type? Adjust the name, adjust the shot JSON document. Yes, there's another value, just save. Okay, that's funny. Wow, sorry. So if you go back to the cluster overview then we can also directly have a look at the nodes and also on the charts. So we created this collection. We see now all the potential charts and now I can also move the charts around in the cluster. For example, if I want out of some reason, manually clean up one of the server to maybe do some maintenance on that. I can easily do that on the web interface but also we are a wasteful API. That's all possible against the framework and so on. And what is also possible then if I want to have three nodes of the DB server, let me also show that as the last short thing in the demo. That maybe takes now a little bit more because the DB server is already a little bit more to start than just a coordinator. Maybe also to explain that on the coordinators. The coordinators are completely stateless. They only do the first phase of the query optimization, the query handling in the direction of the application and also do this fox, the Microsoft frameworks. This is something at the end, complete stateless. You can have 10 of them, hundreds of them. It really depends how much you use these features and if you lose one of them, it makes no difference at all. So now we have three DB servers. Let's go also on them in another collection and make a web application factor now three because I have the possibilities for that. Oh, sorry, test is over. Now if you go back to the nodes, now we have the two collections and you see we have a replication factor of two that means we have now spread it over the cluster, the leader and the two followers over all the three nodes. And now it's from, for example, it's not possible to scale down the cluster into one node. You should think about it. Normally it would be not possible but it's something where we say it's up to you if you want to do that or not because it's mean that the end in a situation where you have the leader and the two followers only on two nodes. So in the sense of a high availability, it makes maybe not so much sense but it's something, even if you need that for maybe scaling up the machines or use bigger machines for your cluster, it's still possible. Maybe also give you a short example of the query language. So that is also very simple. At the end it's very similar to SQL. You can do something like a loop in some sense or a collection with documents. Then you filter on some stuff and then you make the projection of the result at the end of the query. So maybe that is also the main difference between SQL and SQL at the end. But what you can also do with SQL is to combine different stuff what we're offering. We can do graph queries and joins and document lookups really in one query. So we have really use cases where people start with a graph database and then the optimization at the end, if you use a runway to be, is to use the combination from joins and graph queries at the same times. So it's a sample of what we're always saying is if you have a fixed length in your path, if you make a query or a graph traversal, it's more efficient to use a join instead of a graph traversal. If you really can combine it in one query, then you get really new possibilities in the direction what is the performance, what you're getting out of the stuff. So once we're offering sub-queries, it's a really complex query language but you can really combine the different stuff. So maybe let's go back to, so we're still trying to bring down the number of charts and to be honest, I missed something to tell you at the beginning. We change that, you cannot scale down the cluster until you have to free a replication factor. So let's abort that, go back to the collections, just delete the collection of the replication factor of three, go back to the nodes, then let's have a look at the charts. We have only the one collection with the replication factor of two and try the same again. And now it's possible to get out one of the DB servers of the cluster. So that is the different of why we choose our own framework in D2S. We really can take care of all the stuff. If you want to take out one server, it's no problem, the framework will move the data if possible to the other nodes. If it's not possible, it will protect you that you don't come in the situation that makes not so much sense. And now let's maybe take a little bit before it's the agency recognize that you have moved the data and so on. It's just what York already mentioned also with the agency that this is a rough based key value store where we really hold the state of the cluster. If you change something, it's more or less like a changing of a plan in the agency. And then we have a supervision code, what really then makes sure that all the things happens. And that's also once on the leader of this roughed based key value cluster. So it's sure that it's only once, once a time. So now you see we have getting out one of the DB server of our cluster and the data are still in the way of how we need it. So it's only on DB server one and three we take out number two. So some questions on that. So that's maybe for now for a short demonstration should be good. Especially as we were running out of time. Especially that, yes. How many of you have used either graph database or document database before? How many of those databases were Orango DB? Okay, half, half, okay. So for me it's actually it's really so my background is actually databases like my PhD was understood with the databases back in Germany.  And so I think this is a really interesting space. And just from what I see when talking to customers and users, make sure that you choose the right database, the right data model for your application because it actually it matters a lot how you model your data and how you get your data into those different systems. So just seeing so many customers doing that mistake please think about which database to choose and then also how you to fit your data into that specific database, into this specific data model. Thank you very much for listening.


Being an entrepreneur is rewarding.  But at the same time, people won't always tell you some of the scary truths of being an entrepreneur. Like the headless hot dog. But seriously, sometimes we don't always tell you the whole story. We always talk about the great stuff, like working whenever you want to work, no bosses, no one to tell you when to go to the bathroom. I get it. But there are some scary sides of being an entrepreneur. Like the first one with organization, being an entrepreneur means like you have to be organized or else it's just chaos all around you.  Many entrepreneurs say that they lose four hours a week of free time because lack of organization. 41% of those entrepreneurs that are on vacation, they'll take time away from that to work on work stuff. The key is not to schedule your priorities, but to prioritize your schedule. Right. And 36% of the people polled say they have a general work-life balance, which is tough. You know I like to watch movies, right? Yeah. Did you hear about the movie with the hot dog? What movie? I won an Oscar wiener. So it's so important to take care of yourself. I understand. You want to make sure that your business is growing and it's going well. At the same time, you need to have a good balance between work and life. 63% of entrepreneurs say that they specifically take time off so they can do self-care. Yeah, that number was actually surprising. I thought it was going to be a lot lower because I talked to a lot of small business owners that they just work, work, work. Most people think that when you become a small business owner, you can work whenever you want. If you're afraid of 40-hour work weeks right now, chances are when you're not sure, especially just starting out, that workload is going to be 60, 70, 80 hours a week getting started. So that work-life balance is crucial. So, hey, Jeannie, when you're chilling on a lamp, what do you like to do just to kind of unwind and relax? Well, good question, Weenie. I wish I had enough time to watch movies, but I keep getting asked by all these people for wishes. So another scary truth about being an entrepreneur is you have to be a part-time accountant. I get it. It's another hat you have to wear on top of running your business on top of your head. But we sometimes forget that that's vital. We have our normal paychecks when we're working 9-5. Those taxes get taken out. If you don't plan ahead for this, come tax season, you're talking about thousands and thousands of dollars that you have to come up out of nowhere. So if you don't plan ahead for this, you're planning for disaster. And, honestly, don't want to go up against that other three scary truths. IRS. And you want to make sure you're getting paid on time. Any outstanding invoices, you want to make sure that you're getting those when you need them because the consistent cash flow can make you make sure you're staying afloat. Yeah, I know. It was super tough for me when I freelanced in web design. That was sometimes hard when I relied on that money coming in and I sent those invoices and then those reminders and the client still hasn't paid.  So plan ahead for that. Make sure you set really good expectations with your clients, the money schedule and the payment so that you're protected with your business. And the next scary truth is you want to make sure you're in it for the long haul. Now, if you're not a foot long or a genie that lives for 10,000 years and you have instant gratification syndrome, you may not want to go into business for yourself. Yes, it's gratifying. Yes, you want to make sure that, you know, you have all of these creative outlets for you in building this business, but it's going to take some time. So be patient and know it's longevity that you're after. So we're not always going to be able to work on the fun stuff, the thing that really got you into the business itself. Sometimes you got to work on the not so fun stuff, the accounting, the invoicing, the late nights, the admin, all these things that essentially makes your business run. But it's something we have to do and we'll persevere if we have a very strong why. And those nights are like, I'm about to throw in the towel. I'm about to give up. Remember what got you started? Why did you start this business? Because that's going to push you through to grow it and just follow your passion. And you're not going to want to do all these not so fun things all the time, but you have to. Or else you'll fall short. Hey, was that a short joke? Have you been here the whole time? So the next scary truth is you're probably going to want to give up at times, but just channel your inner Smurf because Smurfs never give up. When the going gets tough, the tough gets smurfing. But don't throw in the towel, you know, just focus on the end game. There's a lot to look forward to and all your accomplishments that are soon to come. Yeah, and it's going to feel like you're just wanting to work till 2am in the morning trying to get all this stuff done, but it's like cooking a hot dog. You got to only cook it so long before it's that perfect temperature, right? Same thing with your business. Only work to that perfect temperature. Don't overexert yourself.  Special delivery. My favorite. All right, so here's the other scary truth.  I know, hard to believe, right? But I think my boss is pretty awesome. I mean, she lets me work in pizza costumes. Sometimes my pajamas. Hey, if I didn't get enough sleep the night before, she's cool if they taking a little nap. If you're feeling a little blue, exactly I get to take some time for myself. Throw in a midday yoga class. You call it. Also, she lets me blast my music. I want to get into that creative zone. In fact, you know what a pizza maker's favorite song is? What is that? Slice, slice, baby. Boom, boom, boom, boom. But you know, sometimes my boss, she screws up and it's pretty frustrating. It causes more work for everybody, including me. Sometimes I want to ring her neck. But at the end of the day, every day, I know she's trying her best. What are you saying, Emma? Aren't you your own boss? That is correct. So I got to deal with all of it. The good, the bad, the ugly, but it's worth it at the end of the day. I get to be the boss. That's a wrap. Be sure to comment, like, subscribe, and ring that bell. This is The Journey. We'll see you next time.


Next question is from Brady Sims 3. When should you use and not use a lifting belt? Well, first of all, it's up to you. So you can use one or not. Not that big of a deal, but I'll put these people in the category of people that probably should use a lifting belt. Number one, people who compete in strength events that use lifting belts.  They always wear belts or it's allowed in competition. Then you're going to want to wear a belt when you lift because there's a technique and a skill to using a belt. You don't just put one on and then voila, you feel stronger and more stable. There's actually a skill and technique to learning how to use one properly and how to maximize the leverage and the stability that a belt provides. The other person is the person that likes to have fun with their lifts and wants to learn the difference between lifting with a belt and not with a belt. Most people probably, you probably never need to pick up a belt. It probably doesn't really make a big difference. I use a belt because years ago, I trained with one and I had fun with it. Until this day, I have fun using a belt, especially if I'm going really heavy. But truth be told, I probably would be better off not using a belt and just getting my core to be really good and stable and strong without a belt because it's a totally different muscle recruitment pattern. Stabilizing without a belt is different than stabilizing with a belt. Yeah, I would also throw in there, if you're in a competitive athletic environment, mainly because a lot of times, like, and this is my experience and a lot of other athletes' experience when you're working out with the team and you're in the gym and everybody's in there together, it's just like, you're always trying to do more. You're trying to load more.  So to have that as an extra insurance, I could see that being valuable in that environment. But for your average person, for me, I like to go for a long time without it. You can experiment, have fun with it and whatnot. But to find out what you can truly stabilize and what you can truly control means that you actually own that weight. And that's just something I've always stuck with because my body is going to give me the indication whether or not I don't feel like I can brace that amount of weight properly. So that's an indication to me that I need to go down a bit in load. Do you guys remember the last time you used a belt? It's a long time ago. I used one at least once a week. Oh, okay. You're that? Oh, you're more than me then. I thought you were less actually. I went off for a while and then, I mean, I have fun with it. Again, I learned, remember the story I talked about, those power lifters that taught me how to squat and deadlift. They also taught me how to use a belt. And so since I was 16, I've been using a belt on and off. In fact, I had the old belt I wore when I was 16, up until about six years ago. And I gave it to one of my clients when I stopped personal training. But to me, there's a different feel around it, maybe some nostalgia. But I mean, training clients, I had Doug wear one sometimes. I had another guy wear one sometimes. But I never had anybody else wear a belt. Yeah, that's interesting. I didn't know you were using it even that much because I know you're obviously, you don't talk about using it that often. I would say I was probably, I thought I was using it the most. I mean, I haven't used it in months just because it's where I'm at right now in my lifting. Where I saw the most value is like, when I was competing and, you know, I would just, I was doing so much volume that my low back a lot of times would be fried. And then I'm getting ready to go do some exercise and I just want to take it out of it. I don't want, I don't want my low back to be the first thing to get fatigued and give out. I'd trained myself to use a belt long enough. And so me being able to stabilize and have some external existence with that made it nice when I was lifting. Similar to how I use straps. Straps are the same way too. I just didn't, I didn't see a lot of value in using them for overall strength and what like what Justin like tins the train for. Doesn't make sense to me for somebody like that unless you're competing. But when you're sculpting and you're a bodybuilder and you're trying to isolate parts of the body all the time, to me, I understand where someone like that uses tools like that more frequently than the average person. Otherwise, it can end up being a crutch and the people that tend to gravitate towards using a belt think that they because they have low back issues or problems that they should use a belt and that's the safer way to go when in reality that person would probably be better off not using a belt. Yeah, that makes a lot of sense actually because you know in that, in that frame of thought there's a lot of benches and positions and things that they specifically use to give you relief from fatigue so you can just isolate the muscles. So to me that seems like a natural fit. Bodybuilders wear belts differently than powerlifters do too. So powerlifters will put on a belt heavy lifts. Bodybuilders put on a belt because they think it shrinks their waist and so you'll see them wearing a belt. Like all day long. Yes, they're hitting arms and they'll wear a belt. They're hitting chest and they wear a belt. But you know bodybuilding is an aesthetic sport so everything revolves around aesthetic and especially at that level. Look, here's a deal. If you're the average person and you want to build muscle and you like to follow a bodybuilding routine, that doesn't mean you do the stuff that the advanced bodybuilders do. That's a whole different level. Like, are you going to wear a belt to make sure your waist doesn't grow or something? It's not going to help you at that level.  It's turned into an accessory, like a clothing accessory. You have your name on the back.  I love you. Yeah, I'm announcing I'm a bodybuilder. You know what I'm saying? That's just rules. It's become that.  Yeah, 100% in my stringer, right? Underneath my leggings. Super thick oversize sweater. You've got to get a pump first. Yeah, yeah, that's all right. And then scare everybody afterwards. Look at that dude over there, right? No, no, no. I mean, there's... To me, it's a tool, right? I mean, I think you're alluding to that, Sal, that it's a tool and it has value. But for most people, you should be training with it as little or as never, or never. There's no reason for you to do it unless you're spore. It changes recruitment patterns. When you wear a belt, your core pushes out against the belt to stabilize. When you don't have a belt, your core braces. Totally different. If you get really good with the belt and all you ever do is wear a belt, when you go out to brace your core in the real world, you might find yourself having problems. Exactly.


While a Bemidji shop primarily sells local goods, their work reaches beyond city limits. The least of these is a fair trade boutique, promoting area artisans while donating to various causes. Mel Myer has more for This Week's In Focus. And then that's why I have quite a collection of them and then I just paint them. Heather Herrim is a born and raised Bemidji artist. She's been making her jewelry and mixed media art on and off for the last 10 years. I work with fiber arts, I work with painting, I work with jewelry and I really try to explore every media I can. In 2014, she began to sell her work in town at the least of these. They really supported me with my artwork and helped me grow as an artist as well and gave me the opportunity to sell my work here. She says pricing is a challenge for her, balancing what consumers are willing to pay versus the hour and money she has put into her pieces. Some of my creations take hours upon hours and I really can't put a monetary value to that either. Depending on the item, a piece like her wire wraps could take anywhere from 4 to 30 hours to make. That probably took me like 15 hours maybe, maybe more. So you know I do decrease my prices just to get it out there as well and just to keep doing what I'm doing. The price point at this store also reflects a philanthropic aspect. In 2016, part of her proceeds from her art went to the Village of Hope, a homeless shelter in Bemidji. The store owners even started a non-profit in Uganda and directly trade with artisans in the country twice a year to be featured in the shop. We order fair trade items from all over the world. Parham says it makes her feel good to know that other artisans like herself are getting a fair share. I know people around the world know many different trades and they should be supported ethically all across the board no matter where they're located. Heather is looking to use a portion of her profits to help fund her mission trip to Uganda. In Bemidji with this week's In Focus, I'm Mal Meyer, Lakeland News. If you've enjoyed this segment of Lakeland News, please consider making a tax deductible contribution to Lakeland Public Television.


I'm here in downtown Northampton in front of the Unitarian Society building, and I picked this spot to tell this story because of the incredible role that Unitarians and over a thousand clergy in Massachusetts played in the battle to keep discrimination out of the Massachusetts Constitution. In 2006, 10 couples, same-sex couples, went to their city and town halls across the commonwealth and asked for a license so that they could marry, and each of the clerks said that they were unable to issue them a license under the Massachusetts laws. They took that issue to the Massachusetts State Supreme Judicial Court, and by a vote of five to four, the justices voted that under the Massachusetts Constitution, same-sex couples had the right to marry the same as heterosexual couples, that under the Constitution, equal opportunity meant gender could play no role in the decision as to whether or not people could secure a marriage license. It started a three-and-a-half year battle with those forces that sought to insert into the Massachusetts Constitution language that would define marriages between only one man and one woman. That three-and-a-half year battle was a battle that many of us saw as necessary to keep discrimination out of the Massachusetts Constitution. After three-and-a-half years of debate and meetings of the Constitutional Convention, we finally secured enough votes to defeat that proposed amendment. The beginnings of that battle were in those 10 city and town halls with those 10 couples and the act of the Supreme Court, but once the court made the decision, they said the legislature had 90 days in which to do whatever changes in the law were necessary in order to secure the rights of these couples. It turned out that the governor, the speaker, and the senate president were all opposed to the idea of same-sex marriage and all were in favor of putting some kind of discriminatory language into the Massachusetts Constitution. From a group of about eight members of the legislature organizing for these conventions, we grew from 8 to 50 and then 60 and 70 and 80 and finally on the final vote three-and-a-half years after the convention began, 158 members of the 200-member state legislature voted against writing this language into the Constitution, thereby supporting the rights of same-sex couples. The Unitarian Church was the space that we used as organizers in Boston to meet, to plan our strategies, to educate members in the legislature about the importance of this civil right and so the Unitarian Church played a very significant role in a very quiet way in helping us to succeed at our constitutional convention. Even as we were organizing and convincing our colleagues one at a time to view this not as a religious issue but as a civil issue and that we as elected officials had a responsibility to write civil law, not to write religious law or not to advance religious law. We can carry our beliefs and our faith into the debate but ultimately our responsibility and decisions as elected officials was in this instance to write civil law and in this country in order to be married you have to have a license from the government to get married and then you can choose to be married in a religious ceremony or in a civil ceremony or both. In fact you know many of the clergy who conduct marriages are the folks who end up signing the legal papers indicating that they conducted the marriage ceremony and this is perfectly legitimate under our laws but it is at its core a civil exercise in our society not a religious exercise. That a thousand priests and rabbis and ministers and pastors chose to join the fight and to speak out publicly in support of diversity and respecting the uniqueness of each individual as a person created in the image of God as is believed in most religions was a great strength to the people who were fighting this battle. And so standing in front of the Unitarian society gives honor and homage to the religious leaders and to the specific and special role that the Unitarians played but also doing so here in Northampton in a place that has among the largest number of same sex married couples in the Commonwealth on a per capita basis and anywhere in the country on a per capita basis also signifies and communicates how wonderful and unique this place is in which we live that respects and honors the diversity of its people and seeks to create a welcoming place where all people of good will can live and work and play and participate in life together. And so one of the proudest moments I think for all 158 members of the legislature who voted to keep discrimination out of the Constitution was that we knew that we had gone from a core of about eight members to 158 members who were convinced by their constituents and by their own consciences and by their own commitment to their duty to ensure that they upheld their responsibility to write civil law in conformity with the Constitution and protect equal opportunity for every citizen. And that is in the nature and the values of the place in which we live. And I think we can take great pride that the communities of Hampshire and Franklin County this valley provide a welcoming environment so that people from all walks of life all faiths all faiths who have many different ways of living can live together peacefully and enjoy one another's company.


This study examined the safety of saffron consumption by pregnant mice and their offspring. The results showed that saffron had no significant effects on the livers and kidneys of the offspring, but did increase levels of urea nitrogen in the blood of the offspring. Therefore, it is recommended that pregnant women limit their intake of saffron to avoid potential harm to their unborn children. This article was authored by Mahmood Bamani, Morteza Ruffian, Azar Baradaran, and others.


going to be more than just a city building. This is going to be a place where the entire community can gather with your children and your entire family and feel really proud about your community and what it really means to be at Fort Worth City Hall. Oh, this is big. Yeah, I think you see smiles on everybody's faces today. This is the people's house and the idea that we'll have parking available, we'll have access available. I'm very excited about this because this will be the people's house. So everything you see that's going to happen, demo-wise, renovation-wise, the site here today is going to be focused on making sure that everyone in the city of Fort Worth is welcome here and feels welcome here.


The kids here today do get a bit of insight into the emergency services and the different organisations. We've got CFA, VicPol, the Federal Police, SES. It's a great way of breaking barriers down. Hopefully they get a bit of insight of what we actually do in the emergency services, give an understanding on how we operate and hopefully maybe plant a seed in their minds that they can do this in the future. Since I was younger I've always wanted to become a police officer, to be able to help people, but as I got older I've always like, oh I don't know, I discover more things and then I was like, social work seems pretty good because it's also helping things, but then also fibre gates like for like fitness and it seems pretty good. It's an option. The best part I think has been so far the virtual reality and the smoke room because the smoke room went in there and it was pretty funny everyone had a laugh and everything and then when we went into the virtual reality it was more like a cool thing.