Was Ananias and Sapphira were they Christians? Well, this comes up for two reasons. One, because the consequence of their sin was death. And so the question would be, do we die as a consequence of our sin? Can death be a consequence? Well, obviously, yes. Death can be a consequence of our sin, whether you are saved or unsaved. Was Ananias and Sapphira were they saved? The answer is going to be no. But here's also another reason why this comes up, because some will say that here's an example of someone who was a Christian who also was possessed or demonized or had a demon. And if that's the case, if they indeed were saved and they had a demon, well, then does that mean that we also too can have a demon as believers? However, the scriptures show otherwise that Ananias and Sapphira were not believers. So let's go there first. Acts chapter five verse one, and let's read the story. But a man named Ananias with his wife Sapphira sold a piece of property and kept back some of the price for himself with his wife's full knowledge and bringing a portion of it he laid it at the apostles feet. That's important. So what do they do? They're selling their land and they're bringing there the portions of the proceeds to the apostles and laying it there because at the founding of the church, you've got these people that are coming to Christ, having everything in common, selling their things so that everyone will have everything in common that there will be no one in the community that lacks. That's important because we're going to have to find out a little bit more about this to determine and see conclusively that neither Ananias nor his wife were believers. But Peter said to Ananias in verse three, Why has Satan filled your heart to lie to the Holy Spirit and keep back some of the price of the land? The question is going to be, does this statement mean that he was that the devil entered him that he was possessed or demonized or whatever the lack that you want to use? Does this mean that this person that Ananias had a demon? Well, we don't really have to argue that point. Maybe he did. Maybe he did. Maybe this means that maybe not. Maybe he influenced him, but didn't have a demon. Maybe he was not demonized. That point won't be necessary to prove one way or the other to prove that Ananias was not a believer. I'll show you why just to believe in a minute. He says, while it remained unsold, did it not remain in your own? And after it was sold, was it not under your control? Why is it that you have conceived this deed in your heart? Now, he states that you have conceived, but we'll still go ahead and allow for the belief that this was Satan's doing. This is the devil's doing and that even still maybe he had a demon. You have not lied to men, but to God as he heard these words. Ananias fell dead and breathed his last and a great fear came over all who heard the young man got up, covered him up and carry him out. They buried him without reading further. We know the rest of the story. His wife comes and she goes along with a lie and the same thing happens to her. So again, the question were they saved was Ananias and his wife say the answer is a resounding no. How do we know? Here's how in Acts 432 we see that all of the believers are coming together, the congregation of the believers are coming together selling their properties and having everything in common so that no one can lack anything. I mentioned that earlier and here's why this is important. 1st 32 starts off by saying and the congregation of those who believed were of one heart and one soul. And so who believed the congregation? That's vitally important. The congregation did what they believed and the tense of this is they were believing. So this is a part of simple. So all of them were believing and what is it? What else does it say? They were all of one heart and one soul meaning that they all had the same thing in common. They all believe the same thing. They were together on this. They were all in agreement and those what else it says it says and not one of them claimed anything that belonging to him was his own. So we need to understand this none of those people none of those that were believing not one of them claimed anything that was belonging him was his own. So who's the them that's been referred to here? Let me highlight this point here. Who is the them that's been referred to? Well, the them is the ones that are believing and so he says not one of them not one not one of the believing. This is why it's vitally important that I want to over stress this point not one of the believing ones would sell something or claim that anything belonging to him was his own but all things were common property to them and with great power the apostles were giving testimony to the resurrection of the Lord Jesus and abundant grace was upon them all on them all for there was not a needy person among them for all who were owners of land. Notice this for all who were owners of land or houses would sell them and bring the proceeds of the sale all of who all of the ones that Paul or the writer just says were believing all of them were doing that they would sell them and bring the proceeds of the sales and lay them at the apostle's feet and they would be distributed to each as any had need. Now why is this important? Because if we just move a little further to chapter 5 verse 1 the same thing is being spoken of then we get to chapter 5 and notice how it starts off but a man named Ananias this is in contrast to what was spoken of in chapter 4 the latter part of it Ananias is not one of the ones who were believing he remember the Bible says that not one of them would have anything claiming to be his own and all of them all of who all of the believing ones would sell their proceeds and bring them and later than 50 the possible so Ananias is not called one of the believing ones he could not be one of the believing ones because if he were one of the believing ones within the writer is incorrect now Luke is writing this but Luke was not there at the time and so Luke is being told this maybe by Peter or some of the other apostles but they're being told he's being told this and so they would be incorrect and Luke would be incorrect and here would be a lie and it would be a mistake of the Bible to say that everyone when everyone isn't true when they say not one of them when there is one as a matter of fact there's two Ananias and Sapphira so this is how we know that Ananias neither he nor his wife were believing ones neither he nor his wife were saved and sometimes if we just stop and just go through the scriptures reading context understand what's happening chapter 5 doesn't take place in a vacuum by itself it takes place after chapter 4 specifically the latter part of for and we can see that all of those that were truly believing they were the ones that sold their properties and brought them to the apostles but the one guy who we know who did sell his property and lied about the proceeds he's not included as a believing one amen.


Live from Las Vegas. It's theCUBE. Covering VMworld 2017. Brought to you by VMware and its ecosystem partner. Hi, welcome back to theCUBE. Live from VMworld, day one. Really exciting day that we're having so far. I'm Lisa Martin with my co-host, Dave Vellante. We're joined by a CUBE alumni and a new CUBE guest. Welcome back to theCUBE. Rhea Barrett, Senior Director of Product Marketing at Dell EMC. Thank you, thanks for having me. Good to have you here. And we also want to welcome Mark Wisely, the CIO of Palmer Chiropractic College. Welcome to theCUBE. Thank you, it's great to be here. It's great to have you guys. So, one of the things that we were talking about before we went live is backup. Is backup back? Is backup sexy again? It's hot. Why is backup so hot, Rhea? Oh my God. Yeah, it is. I started years ago and I was in data protection and go forward 20 years, it's back in data protection. It's hotter than ever. In the last six years, I think there's been over five billion dollars invested in this space, whether from venture capital or big companies. And it's hot because of what's happening in the customer's environment. We see a huge restructuring of data centers. So, before data used to be in a couple of locations that we called data center. And now it's really much more about centers of data, data is moving out of the four walls, moving closer to where decision making is, which is with the business, out in the geos. So it's moving to the edge and also just cloud. Cloud is really, and cloud deployments are really reshaping where customer's data is. So now that data is no longer in a building, how do you secure it? How do you protect it? Where is it? Who owns it? Those are becoming more and more prevalent questions. So that's why backup is sexier than ever. So what are the drivers for you in terms of your backup? What keeps you up at night when you wake up in the morning? What are you thinking about in the backup context? Well, for us, it's really about not having to think about it. Making sure you've got a solid solution that's there to back up that data and make sure that it's available when you need it and where you need it. And the Dell EMC product we put in place gave us that opportunity where we can back up our servers, our desktops, our laptops. It doesn't matter whether they're off-site or on-site, they can be anywhere. It gets backed up quickly. And it doesn't interfere with what they're doing. Users don't want to be interrupted with a backup and have to sit there and wait for it. So it's been a great solution for us. So Mark, you've been, you've got over 20 years experience in the industry. You've been a CIO at Palmer for nearly two years now. And one of the things that I read about you is that you were attracted to neglected IT systems. I imagine you saw a tremendous amount of opportunity, but we talked about kind of bringing sexy back with state of protection. You were instrumental in kind of changing the IT direction at Palmer back to Dell EMC. Tell us a little bit about that and why that was so important to you as the leader of IT there. Well, when I came into Palmer, we had a number of different issues, everything from performance to backup windows that we couldn't hit. We're still using tape backups. There was a number of different issues. And so we really needed a platform that would be able to come in and solve all those issues and also do it as quickly as possible. So we put in a Dell EMC VX block, which allowed us to kind of look at it as like a data center in a box type thing. I mean, it solved our networking issues and our backup issues. And then because we have multiple sites, we were able to actually back up our data and replicate it to some of our other data centers across the US. So it was just a perfect solution for us. And then one of the real nice things is when we actually put that product in, Dell EMC came in and helped us to implement it. And within three days of them arriving, we were actually running production workloads on that. So it worked out great for us. You know, that reminds me. So I've asked this of some of your colleagues and it's backup forever has been a bolt-on. And the VX block triggered something in my mind. I remember the original V block. I remember it said, serves up 5,000 VMs. And my first thought was, how do you back that up? Right. And there wasn't an integrated answer. This is a long, long time ago. There is today. Yeah, absolutely. Maybe talk about the philosophy of backup as a core component of a deployment and what you guys specifically have done there. Absolutely. We actually today had a really exciting announcement that really would be under what I call more of a transformational approach to data protection. And really the move that we see is it used to be that backup used to be kind of an afterthought. Something that you roll out your applications and you're like, oh yeah, we have to protect them and figure out what you're going to do and you'd implement what you need from an infrastructure standpoint. We're really seeing a much more of a move towards a source-based data protection. So we're building data protection capabilities and directly to the applications. So today we announced Data Protection Suite for Applications and a whole new version of it which really enables the native UIs that the database administrators are using to be able to protect their own workloads. And this source-based data protection is going to be more and more critical, especially as data is moving closer and closer to where it's getting created. So you need to protect it at the source, not in the background, not as an afterthought. We also are seeing convergence, which is your question around VxRail. We have integrated data protection now built into VxRail deployments and we've had it for a couple of years now. And this year at Dell EMC World, we introduced IDPA, Integrated Data Protection Appliance. Again, bringing all the components that a customer would need, Integrated Data Protection Storage, Integrated Data Protection Software into an appliance model. So it's all about simplicity, just making it easier for customers to be able to deploy. So Mark, you're obviously a VMware customer. And as a VMware customer, your backup has sort of been subservient to the VMware momentum. You remember the ascendancy of VMware totally changed your backup requirement. You get less physical servers and backup was very consumptive of resources. So you had to think about that. Fast forward now, this whole cloud world. What are you doing in cloud? How is it affecting your backup strategy specifically? So we're looking at, you know, the cloud is one of the areas where obviously we're exploring opportunities. You know, one of the reasons that we put in the VxBlock and the data domain and Avamar and the data protection suite was really to set us up to be able to make that transition to the cloud simpler. You know, now we have the tools in place so we can decide when we need to move it to the cloud. What data do we need to move in the cloud? Where do we need that data to be? And it just gives us lots of opportunities and lots of options, so. So let me take that one step further. And so let's define cloud a little differently. Not just as a place you put data, but as I want to bring a model to the data, wherever the data lives. So it's, you know, self-service and it's automation and all those things associated with cloud, maybe bringing that on-prem or putting it in the cloud. Is that something that as an IT practitioner, you see as viable or is the cloud? No, no, it's in Amazon or Google or some other external location. Are you trying to bring that cloud model to the business? Yeah, I think, you know, as we look at the cloud, I think a lot of it is just options. You know, figuring out which model or which provider you're going to utilize both from a cost perspective as well as regulatory compliance pieces come into play. So, you know, as we look at cloud, you know, we look at kind of what we've put on site as kind of a private cloud or cloud in a box type thing. And it just opens up lots of different opportunities for utilizing, you know, Amazon or Azure or whatever that is, so. So one of the things that I wanted to ask you, Mark, is really about, you know, Palmer School of Chiropractic was chartered in 1907. 1897. Right. And then I think I saw that it was chartered maybe different name in the early 1900s, but it's been around for a very long time. So, you know, as we see people moving from virtualization to cloud, we're seeing certifications change. You've seen a lot of evolution in data protection, as you said. What's the evolution from an education perspective or maybe even a cultural perspective at Palmer? An organization that's been around for well over a hundred years. What's that shift that you have maybe driven within your IT experts to improve their education, to remain, you know, at Palmer and to help you attract new talent as technologies evolve? Well, I think, you know, one of the reasons that Palmer decided to really look at IT is, you know, we're kind of the trusted leader in chiropractic, the founder of chiropractic, and they really wanted to, you know, up their game. You know, we're a higher ed institution, so most of our students come from, you know, large universities and they're used to a lot of technology and Instant On and all of these different things, and so we really wanted to make sure that we could provide an experience for them that gave them that, you know, the Instant On as well as there's a lot of online experiences after you graduate, you know, there's a lot of CEUs and things that they need to come back for, and so we're starting to build some of our online programs to give them the opportunities without having to come onsite for everything, so it just opens up a whole world of opportunity. I had one last question for you, Mark. I mean, it's the why Dell EMC question. I mean, you got a lot of options out there. We talked about all this investment going in. Why Dell EMC, what's attractive to them and two-part question is kind of what's on there to do list in your view? Well, I think the thing with the Dell EMC is it really was the one company that gave us everything that we needed.  It just gave us everything that we needed, and it was one solution from one vendor, so if we do have support issues, we have one vendor to reach out to. We don't have three different vendors or having vendors fighting with each other. It's one solution, one vendor for support, and it just gave us everything that we needed. Excellent. I heard you say it at Dell EMC World on theCUBE, moving from data centers to centers of data. Pat Gelsinger may have got that from you. We said it on stage this morning. I don't know. So, you're the first. As things are evolving, we thank you for sharing your insights. Sounds like there's a lot of opportunity. Same thing at Palmer. Congratulations on the evolution that you have helped to charter there, and we want to thank you both for taking time to chat with Dave and myself this afternoon. Thank you so much. Thank you guys, thanks. They've seen you guys. And for our guest and my co-host, Dave Vellante, I'm Lisa Martin. You're watching theCUBE live from VMworld 2017 Day One. Stick around, we'll be right back.


Hi, I'm Dodger Browneacore, Technology Analyst with ID Tech X and today I'm interviewing Mr. Spielberg from PV Nanosel. Hi, so Mr. Spielberg, could you tell me a little bit more about what your products that you're manufacturing at Nanosel? Okay, so we are basically an ink manufacturer and formulator. I think the highlight for the show from our point of view is this system that was introduced by Ferro. Ferro launched a printer that prints on glass that is as big as six meters and they chose to use our ink, our conductive ink, in this product. Excellent. Okay. So, what kinds of applications are you looking to meet with that? Okay, if you look at this piece of glass that shows the bus bars, the eater lines and some pattern that can be in antenna, we have already one customer in Europe that is working with this system is producing glass for trains and yacht and a few more customers are coming soon. Excellent. So, what kind of industries do you think would be most interested in these products? So, glass, mainly automotive, yachts, trains or transportation I would say, so this is for this application. After printing the glass is formed and if you know your windshield is not flat, so it's formed after printing. Okay, alright. Okay, and I notice you have a 3D printed lamp over there as well. Yeah, so this is a 3D lamp that was printed with our inks and as you may see it is already working. This is part of a European R&D cooperation and I think that the site talks to itself. Yes. Yeah. So, were the electronics printed separately? In this case, yes, but in the future it will be all together. Maybe I can show you another exciting product. If you can see, the antenna was printed on the rim of the case, okay. This is today being done by attaching manually printed circuit boards with double-sided adhesive. We are allowing incorporation with Optomec to print it, you see on the rim. So was that using the air-rojects? Yes, the Optomec air-roject system. Yeah. Interesting to see a real-life application of that. Yeah. These are antennas too that were manufactured with or incorporation with Optomec, again 3D. So you can see that it's conformal onto the curved surface of the plastic component. Excellent. Well, thank you very much Mr. Spielberg for your time and one last question. What do you think of the ID Tech X show? Great. Very well-organised, a lot of people. Exciting. Fabulous. Well thank you very much. I hope you enjoy the show. Thank you so much. Thank you.


That said, let's get into the word in Mark chapter 16. I'll begin reading at verse 15. I read verse 18. He said to them, Go into all the world and preach the gospel to every creature. He who believes and is baptized will be saved, but he who does not believe will be condemned. These signs will follow those who believe. In my name, they will cast out demons, they will speak with new tongues, they will take up serpents and if they drink anything deadly, it will by no means hurt them.  Now as I've been doing throughout our journey through Mark is I've been alluding to other portions of Scripture, which is what I'm going to do today. I'm going to be reading out of and sharing about this commission that's being given to the apostles. I'll be alluding to that out of Matthew 28. But what we have here in Mark's gospel is Jesus giving marching orders to his men. Everything in this gospel has been leading to this, to this final action. Now as we've been going through the gospel of Mark, we've seen that the apostle had been commanded to go to Galilee. We saw that in Mark 16 verses 6 and 7 where it says that an angel commanded the women to go tell his disciples that he's risen from the dead and going before them to Galilee and there they would see him. Well after the angel commanded them to tell his disciples, Jesus appeared to them. Matthew 2810 says that Jesus said to them, do not be afraid, go and tell my brethren to go to Galilee and there they will see me. So in obedience to Jesus as men had left Jerusalem they went up north into the Galilee. So they were waiting to meet with him even as the Lord had commanded them to do. Now we already saw how that while awaiting him Jesus had met with seven of the men. He met with them on the northern shore of the Sea of Galilee as they were fishing. We looked at that recently and it was at that time that Peter was restored to ministry. So what we're looking at today took place after Jesus restored Peter to his ministry. So at this point the remaining faithful men have come to meet with Jesus. Matthew 2816 says the eleven disciples went away into Galilee to the mountain which Jesus had appointed for them to the mountain. Now Jesus often in the gospels is recorded as ministering to his men on a mountain. It was on a mountain for example that he gave what we call the sermon on the mount in Matthew 5 through 7. It was while on a mountain he chose the twelve according to Mark 313. The feeding of the five thousand took place at the foot of a mountain in John 6. The transfiguration occurred on a mountain in Matthew 17. We know all the Mount of Olives discourse that you find in 24 and 25 of Matthew chapter 24 and 25. It was on the Mount of Olives that he wept over Jerusalem according to Luke 19 and ultimately he ascended to heaven from the Mount of Olives. So this is also a place that is a mountain. Yet notice with me it's unnamed but it's on this this unnamed mountain that he gives the great commission. Now just so that you know some believe that this particular commission was being given to him to them rather from the same place that he gave the sermon on the mount but there's no biblical evidence of that but many suppose that that may very well be the same place he's doing that. But it's here on this particular spot that the apostles as well as we the church are receiving marching orders. So they as well as we are to be witnesses who share the gospel with other people. Now it seems to me and it's very clear to most of us that there are many professing Christians who have misunderstood this particular mandate. They they've not realized that the command was given not just the apostles but they were given to us too. For many of the church for many in the church well they'll attend occasionally church services because that may meet some of their particular needs and it escapes them that they have been given a mission and this mission that that people who attend church have have failed to understand is the greatest mission. It's a supreme urgency. We are to share the message of salvation and we're to live as if we received it ourselves and have been saved. And we're to proclaim the message but the message is to be proclaimed with a goal and the goal is not just to preach a message the goal is to make disciples. The commission is to go into the whole world and that's important to note because we are to go into the whole world the apostles were to go into the whole world not just to the nation of Israel. You see when Jesus originally trained them they were first sent only to the Jews. In Matthew 10 5 and 6 it says these 12 Jesus sent out and commanded them saying do not go into the way of the Gentiles and do not enter a city of the Samaritans but go rather to the last sheep of the house of Israel. In Luke chapter 10 when he had appointed 70 others he sent them two by two before his face into every city and place where he himself was about to go so they would go out but they would go out to the house of Israel and so now according to verse 15 they're to go into all the world and to preach the gospel to everybody. Why? Because God doesn't desire any to perish but that all should come to repentance. When Isaiah was writing in Isaiah 45 verse 22 it reads there turn to me and be saved all you ends of the earth where I am God and there is no other and so they're to go the church by application but they are to go into all the world and preach the gospel to herald the good news. Psalm 96 verse 3 says declare his glory among the nations his wonders among all peoples so they're to go forth and they do so with the authority and the intent of being listened to and to be obeyed so what we do is we proclaim the message of salvation and what we also do is we encourage people to turn to the Lord we point people to Jesus Christ we reveal to them that that he came to die that we might live that's what we just celebrated recently when we gathered together for for Easter services that Jesus Christ came he lived he performed works he died on a cross and he was raised from the dead and we proclaim that that's the the core of the gospel we talk about the death of Christ so that he might purchase us redeem us ransom us out of sin to take us out of the power and sway of the enemy to no longer live as if we're still in the world and and just being tossed to and fro by every wind of doctrine what we are called by God to do is to be transformed we can be so through the gospel of Jesus Christ and so that message has come to us because we know that salvation is in Christ alone in Acts 4 12 salvation is found in no one else or there is no other name under heaven given to mankind by which we must be saved so the gospel the gospel is the greatest message that could ever be proclaimed we proclaim in that message that God has so loved the world that he gave his son we proclaim in that message that that God provides forgiveness for our sins through Jesus Christ we're just in Romans 5 just this last week in chapter 5 verses 8 through 10 and I was teaching out of these verses God demonstrates his own love toward us in that while we were still sinners Christ died for us much more than having now been justified by his blood we shall be saved from the wrath through from wrath through him for if when we were enemies we were reconciled to God through the death of his son much more having been reconciled we shall be saved by his life and so Mark tells us go into all the world now the command and I want you to see this in verse 15 he simply says go into all the world and to preach the gospel that's Mark's abbreviation of the commission Matthew gives us more Matthew tells us what we are to do as we go into all the world in Matthew 28 19 and 20 go therefore make disciples of all the nations baptizing them in the name of the Father and of the Son and of the Holy Spirit teaching them to observe all things that I've commanded you and low I am with you always even to the end of the age now I want to take a moment to develop this with you I've said this on various occasions how that the emphasis in the verse when he says go into all the world and make disciples the emphasis of the verse is not simply the go it's the making disciples and as I was preparing the study I was refreshing myself and going to other commentaries and other comments and all and and I wanted to share a couple of thoughts about this again in Matthew 28 19 it says go therefore and make disciples of all the nations so I looked this up because one commentator said this so I checked other sources and Greek sources and all to see whether or not he was accurate and indeed he was the Greek word that is translated through the English word go in Matthew 28 19 the Greek word can be translated go in an ongoing way go in an ongoing way in other words you are to continually be going is what Jesus is saying so the disciples were to go and they were to take the gospel out even out of Israel that's the whole point that's being made it's not just to the Jewish people now you go into the world so you're to take this out even beyond the borders of Israel and it's an ongoing thing it's something he's telling his men and by application us it's something they were to never stop doing the word go can carry with it the inference of being compelled compelled to continually go now what would compel them to continually go if he's saying go with the sense of compelling them to go what would it be that would compel them from the inside to go well one it would be God's love for them and God's love for them to a world that is lost and that would serve to compel them they have been loved by God and because God has loved them they're compelled to tell others you don't keep things to yourself that are good when I got saved I didn't keep it to myself when I met the girl I married I didn't keep that to myself she wasn't my secret kind of side thing everybody knew and everybody to this day knows that I have a love for this particular woman my wife Marie I didn't keep it to myself I'm compelled in many ways to share that which is most dear to me and so the gospel you're a compelled from the inside why because God has so loved you and God has saved you why wouldn't you talk about him why isn't it natural for you to talk about him why wouldn't you we talk about so many things talk about for me it's the Dodgers for you it's a losing team but we talk about sports we talk about our jobs we talk about relationships as mentioned we talk about our families and it's natural right you don't kind of like have to make yourself talk about those things those are things that are spontaneous why is that because at the top of your list because those are the things that matter why wouldn't I talk about Jesus Christ why would I keep unto myself why would he be the best kept secret of my life there's something that compels you he loved you he sent he laid his life down for you he forgave you he blessed you he's with you he never leaves you why wouldn't I speak about him see so there's a compelling and Paul speaks about that himself he said in 2nd Corinthians 514 the love of Christ compels us it's not my love for him it's love for me his love for me and that compels us and so one of the things that causes us to to speak is simply God's love God's love that has has been taken in if you will God's love that has been revealed in the sacrifice of Jesus that has internally driven us to speak about him and to go but there's also something very practical that you find in scripture what else would compel them to go well it's interesting because one of the things that actually compelled them was persecution you might find that interesting but it's true persecution would arise and would be used by the Lord to compel them you see when the church was birthed at Pentecost at first the people who saw the church actually respected these believers in Acts 2 46 and 47 it says with with one accord they continued to meet daily in the temple courts and to break bread from house to house sharing their meals with gladness and sincerity of heart praising God and enjoying the favor of all the people and the Lord added to their number daily those who were being saved so at first they enjoyed the favor of the people they actually spoke well of them but a short time after the church was birthed the disciples began to be persecuted now up until that time they had remained in Jerusalem but when the church began to be persecuted they were actually compelled to leave in Acts chapter 8 verse 1 that verse tells us that after Stephen was martyred a great persecution arose against the church which was at Jerusalem and they all were scattered throughout the regions of Judea and Samaria except the apostles and so one is the love of Christ compels us but two they actually through persecution were forced to leave Jerusalem and take the gospel out so Jesus commanded them he commanded them to go and he even compelled them to do so for them the love of God would be the driving the compelling force but the persecution they experienced also drove them out of their comfort zone to preach and so in mark 16 verse 15 again it says go into all the world and preach the gospel to every creature so they were to leave Jerusalem in order that they might preach the gospel everywhere they were to take God's word and communicate the word of God clearly now listen they weren't to appeal to listeners emotions they were to appeal to their understanding God working in them and through them was going to establish their credentials to be able to speak on his behalf and so with this in mind the commission Jesus gave them is one of making disciples not just going but going with a purpose they have a purpose a purpose is to leave and make disciples it's not just going out it's laboring in ministry to produce disciples what's a disciple a disciple is someone who believes in Jesus as their lord and savior intentionally learns from him and strives to live more like him so Jesus wasn't only sending them out but sending them out with a purpose they were to go into the world to make lifelong learners of Jesus Christ they were to go into the world and produce lifetime pupils of Jesus and his message now why is that important it's important because making disciples is the most effective way to evangelize and to thrive so as they go when they go where they go they are to make disciples and they're to make disciples not deciders that's an important point sometimes we speak about making a decision for Christ I understand the terminology I've used it but the emphasis is not making deciders because I've seen over the course of many years that sometimes people will raise a hand or come forward at an invitation who have no intent at all of following the Lord they just through an emotional reason or perhaps a going through a crisis of some sort and they think well I'm going to try God doesn't work that way it doesn't work that way it only only become a disciple of the Lord Jesus Christ when you completely give up die to yourself and receive him as Lord and Savior when you say I can't make it I will not make it I need you you don't add God to the to the hodgepodge of beliefs he becomes the center of everything you see and so when when we go out to make a disciple it's not so that we can have spiritual scalps that we count and say oh 65 people got saved today because they gave an invitation it's when they go on and produce disciples themselves that you know that the seed actually took that's how that works and so these are men who are supposed to go out and they're supposed to encourage people to become disciples a lot of times I I'll read I'll I'll say this I don't have it in my notes but it comes to mind when our church first began I began to read several books you know I wanted to get some insight from other people who have planted churches and do evangelism and one of the people that I used was an expert on on evangelism and church growth and so I thought I could learn from him so I read his material and book and he pointed out now this was again 40 plus years ago he he pointed out that he said in the Billy Graham organization which by the way I highly regard Billy Graham and and and and also this is not in any way a discredit to him but I found it interesting and it's what helped to form my my mentality this this fella did a lot of research on the invitations and the amount of people who quote-unquote made decisions because that's the way it's made it's it's stated there's even a magazine called decision magazine so he was saying we did a lot of follow-up and and they pointed out that in evangelistic crusades out of the hundred percent who come forward 90 percent of those are actually Christians who are simply going forward to rededicate themselves 90 percent he said within that 100 percent there's 10 percent the 10 percent that you see going up to receive Christ out of that a smaller percentage actually are being saved so in fact if you have a hundred people who went forward 90 of them were already Christians and then out of the 10 left almost half of them will walk away we in the united states because we're production oriented like to say well look at all the people who went forward I as a pastor say but how many of them continued to go see making a disciple is more than having someone make a decision making a disciple is to teach them I'll show you this in a minute in the commission so that they go forward and you know when they're a disciple when they begin to multiply by bringing other people to faith in Christ that's when they become a disciple and that's the most evangelistic thing that you can do that's the most edifying thing that can happen now these men had been with Jesus and spent years with Jesus being mentored by him they were called by him they were taught by him they served with him they heard his words they received his explanations they they watched how he ministered they spent quite a bit of time with him they were witnesses of his amazing thing the amazing things that he did they saw him turn water into wine multiply fish and loaves they saw him cleanse lepers forgive sins heal the paralyzed they saw him restore sight to the blind heal the deaf enable the mute to speak calm the storms cast out demons walk on water and and even read raise the dead to life and they also knew that he himself had been raised from the dead so they'd been prepared for this by Christ and now they're being commissioned there to go both by internal compelling even outside persecution so again as they went while they went where they went they were to make disciples and it isn't just the going it's the fruit that they are to produce which is disciples they were to teach people to love Christ and to make disciples of all the nations and that's that's why even as I mentioned a moment ago that's why these kinds of things in this particular portion of scripture has has been the foundation that we as a church have built on where to teach the word to make disciples and that's what makes up what we call our four pillars the word worship witness and witness everything is centered on making disciples and everything is is centered on those four particular pillars and so we're to go out and do that now notice in verse 16 he says he who believes in his baptized will be saved but he who does not believe will be condemned so he says he who believes and is baptized he didn't say he who is baptized this is where a lot of people have an argument he didn't say the one who's baptized he said the one who believes believers are followers of the Lord in baptism because they believe and are saved the outer emblem of regeneration the outer emblem of that hidden faith is is baptism baptism is a symbol of what is called regeneration or being born again water baptism symbolizes our death and resurrection in Jesus Christ how do we know that well roman 6 verses 3 through 5 paul said don't you know that all of us who were baptized into Christ Jesus were baptized into his death we were therefore buried with him through baptism into death in order that just as christ was raised from the dead through the glory of the father we too may live a new life if we've been united with him like this in his death we will certainly also be united with him in his resurrection so when water baptism takes place it's actually an illustration of death burial and resurrection and i share this every time we perform baptism the water symbolizes a grave when you go down into it it symbolizes death and burial when you come out of it it symbolizes life and resurrection and so when your water baptized when you were water baptized if you were you went down into the water death and burial you did that through faith that's why we don't baptize infants because infants only believe one thing they're hungry or the wet they don't believe in christ and my faith doesn't save somebody else there's no such thing as proxy faith my faith can't save my wife i only have enough faith for myself and so there's no proxy faith at all you have to be water baptized by faith in christ so when you were water baptized when you went down into the water you were symbolizing as a an outer testimony to the world you were saying to them i believe in jesus christ i am dead and buried in him now there's something about burial that is so final you can have a hope especially in the early days before they were practicing universally embalming at all you could have a hope that somehow life would once again you know that person would actually not be dead but would be alive in in earlier days in american history i believe was american history in earlier days there were there were people who actually were drinking water out of lead cups most of you probably already know this but and they would get lead poisoning and people didn't know that at that time so they buried them and sometimes the the the place that they were buried sometimes they would reuse that and so they would open the lid or whatever of the coffin and they would find fingernails that were torn off of hands and they would find scratch marks against this is true story i don't mean to be morbid but it's true they would find scratch marks and they discovered that they were burying living people so they drilled a hole and they would put a wire and it had a bell and that's where the term saved by the bell came from did you know that it's not a boxing term they would pull the bell and you had somebody who was in another room waiting to see if the bell was rung and he was pulling graveyard that's where that came from just a little bit not from the bible but interesting right raining cats and dogs no i can go on you know what that was raining cats and dogs people used to make on their on their houses they were low and they had mud and they had hay when cats and dogs would climb on top of it when it rained it turned to mud the cats and dogs would fall off and people said it's raining cats and dogs i can go on i won't i'm just trying to make a point why'd i do that i forgot what i was saying oh yeah water baptism doesn't save you it's well in first peter 321 it says the baptism that now saves you also not the removal of dirt from body but the pledge of a clear conscience toward god it saves you by the resurrection of jesus christ first peter again chapter 3 verse 21 baptism doesn't save you you are baptized because you are saved so jesus is not saying you have to be baptized to be saved because i want you to notice what he says and i'll say it again notice verse 16 first it says he who believes and is baptized it doesn't say he who is baptized and believes he who believes and is baptized why because faith saves you faith in jesus christ now in matthew 28 19 we we have a command he says to baptize in the name of the father and of the son and of the holy spirit now when it speaks of the name that speaks of the name of god which is a a revelation to us of who he is so baptism is to reveal that through regeneration we have a new relationship with god and the union of these three names father son and holy spirit three names for the one god is a proof of equality of the godhead you see in 2nd Corinthians 13 14 where paul says it like this he said may the grace of the lord jesus christ the love of god and the fellowship of the holy spirit be with you all so it's showing us the unity of the godhead and you baptize in the name of the father son and holy spirit in the new testament because the apostles were going into gentile lands they would baptize not with certain formula but with they'd say they were baptized in the name of jesus that's not saying that it was jesus only it's saying that they were baptized in his name because they came to be believe in him and were saved by him that's what that point is being made in that particular way that it says it especially through the book of acts and so how do converts become disciples what keeps the church from being a crowd well it's the teaching and the observing of all things that jesus commanded observing he said all things because in matthew 28 verse 20 it says teaching them to observe all things that i have commanded you so the observing of all things is another way of saying a systematic knowledge and teaching of the word of god and so believers are to be taught the gospel and about the ministry of christ and they're to know the word of god and to be encouraged to obey it it's through the proper teaching the correct teaching of scripture that believers will grow and that's why again our philosophy here is to teach two books of the bible in acts 20 verse 27 paul said it like this he was speaking to some elders from a church the church of Ephesus he's in a port city called my leaders and and he said to them i have not shun to declare unto you all the counsel of god i've taught you that a to z you know it all and that's what it's all about we're we're supposed to know the word so teaching god's word is intended to protect believers and encourage believers to grow protect them from deception and encourage their growth in christ teaching god's word is intended to instill biblical understanding in the believer and that's why in second peter chapter 1 verse 12 the apostle said i will always remind you of these things even though you know them and are established in the truth you now have can't you tell me something new can't you tell me something fresh can't you give no he said i'm gonna give you the essentials why because it's on the essentials that you build your faith and from there you learn to communicate it and understand how it works properly in the world that you live in deception is the earmark of the last days it's spoken of often in scripture in second timothy i'll give you an example chapter 3 verses 13 and 14 evil men and apostles will grow worse and worse deceiving and being deceived but you must continue in the things that you've learned and been assured of knowing from whom you have learned them you must continue in these things why because deception is rampant even in the earlier days of the church there were people who were preaching false things about god and christ and the work of the spirit so jesus intended his followers to become fully mature again their faith is not based on their instincts their opinions or their desires their faith is built on the foundation of the word of god their faith is to be built on the rock of his word a word that strengthens us and it's the word of god that develops our faith again in acts 20 verse 32 paul was saying to these same elders i commit you to god and to the word of his grace which can build you up and give you an inheritance among all those who are sanctified again there's a bit of an interest in the jesus movement through greg's movie and all and things of that nature that's what made this jesus movement in my lifetime in my experience powerful revival but it was undermined i'm hoping and praying that god will do the work that he's done not the same word but do a work i'm praying that he'll do that built on the word of god by the power of the holy spirit but it got undermined and let me tell you one thing that bit controversy to say controversial to say for some people but i think it's true and i might as well say it um i won't say it second service i'll just say it to you now what what is it and i don't want to give you a history lesson but i will say this and i got saved in 1970 i was 20 years old within around six years those who do church history research you can find this anywhere if you're interested in but those who have chronicled the works of the spirit in the church from ancient church history to the present will tell you that the jesus quote unquote jesus movement many many of these who are of that scholarly sort will say that it it began in like 68 69 they'll say and then it it came to its end they'll say which i don't believe it's come to its end jesus hasn't stopped moving but they'll say the height of it stopped in around 76 77 what happened in that day you know what happened and i'll tell you the truth there was a brother whom i highly regard highly regard his memory highly regarded him as a minister of the of the gospel i i regarded and respected him very much jerry fall well some of some people hated him i saw him as as a strong leader and i appreciated his ministry so this is no a negative towards him at all but i'll tell you what happened he got involved he got he got the church involved in a political message and when he did that the power of the spirit began to diminish why because we started preaching politics and not the gospel i saw that happen i have strong political opinions i'll bring them up once in a while of course i should i should but i've never lost sight of the fact that that politics don't change your life jesus does i've never forgotten that i i i just haven't and so with that said we have to be aware of that and a second thing was the proliferation of of of tv ministries radio ministries and now we have proliferation of quote unquote ministries on on the internet and and in in the past somebody could have an odd belief that he was teaching from his pulpit but it was pretty much localized it would stay within the confines of his city or perhaps perhaps his region but now that person can get on tv or that person can get on on radio or that person can go on social network and and the proliferation of those things now is just exponential whereas before it could be dealt with now it's just out there it's like letting it out and that's what's taking place too and what happened in that is false doctrine began to expand nationwide is that something we shouldn't have been prepared for no we are prepared acts 2029 and 30 i know this that after my departure savage wolves will come in among you not sparing the flock also from among yourselves men will rise up speaking perverse things to draw away disciples after themselves so it's the teaching of the whole council of god that produces disciples and finally i'll close with verses 17 and 18 what these signs will follow those who believe in my name they'll cast out demons they'll speak in new tongues with new tongues they'll take up serpents and if they drink anything deadly it will by no means hurt them they will lay hands on the sick and they will recover verse 17 these signs will follow that's important it doesn't say believers will follow these signs it says these signs will follow believers keep that in mind please because there are a lot of christians who follow the signs and sometimes the signs are taking them where they're not supposed to go so these signs will follow the believers it doesn't say these believers will follow those signs it's a very simple thing i just told you but if you take that to heart you'll be safeguarded because there's a lot of people how come you don't this and how come you don't do that because that's not scriptural that's why we don't do that and so he speaks concerning these things believers he said will cast out demons believers will speak with new tongues he saw that at pentecost they're going to pick up or take up serpents and that finds in i find that interesting because some of you have seen these snake handlers they're out there with a snake in this and that then they die in math through 28 3 through 6 paul gathered a pile of brushwood and as he put it on fire a viper driven out of the heat fastened itself on his hand when the when the islanders saw the snake hanging from his hand they said to each other this man must be a murderer for though he escaped from the sea the goddess justice has not allowed him to live but paul shook the snake off into the fire and suffered no ill effects and the people expected to him to swell up or suddenly fall dead but after waiting a long time and seeing nothing unusual happened to him they changed the minds and said he's a god that's interesting fickle minded people he's a demon oh he's a god you know that's the way people think but it actually happened in the ministry and that's like a portent or a prophecy that that thing and we see it in scripture well if they drink anything deadly that speaks of supernatural protection they'll lay hands on the sick and they'll recover you see that often in the book of acts and by the way that's why we do pray for the sick and the point that he's making is take this gospel and proclaim it to all the nations in luke 2448 it says beginning in the city of jerusalem take the gospel out to the world now one last thought and we'll close there are those who say what useless information what childish mythology why do you teach fables it does you no good the gospel is out of out of a sink with modern culture it has nothing that it does that's any good that we haven't already done i remember the story so i just wrote it down so i could say it right in what was once called french indonesia a commentator was viewing sites that at one time were used for cannibal rights as he did so he made a comment he made a comment to one of the inhabitants that it was just too bad that missionaries had come and messed up their culture so the native pointed to a rock and asked him if he knew what that rock was and this commentator said no i don't so the native said well that's the rock that prisoners were executed on we would lay their heads on the rock and we would crush it with a hammer and then we'd eat their brains and then he went on to say if the missionaries had not come you'd be my dinner and so i think the gospel has done a lot of good in the world and i'm pretty sure this commentator would be grateful that these people messed up their culture because their culture was eating human brains why did i tell you that just felt like the gospel does a lot of good may we make sure we take it out take the gospel out not your opinions not your political persuasion but jesus christ let's make sure we do that


Item Number- SCP-3693 Level 2 Restricted Containment Class- Euclid Disruption Class- Dark Risk Class- Notice Special Containment Procedures- SCP-3693 is contained within a secure storage vault at Site-19 due to the uncertain behavior of SCP-3693 and the inability of visual recording devices to perceive SCP-3693. The object is to be monitored at all times by a human observer through a windowed viewing station directly adjacent to its containment vault. Any changes in this behavior are to be reported to SCP-3693's containment specialist. Description- SCP-3693 is a 1.6-meter-tall ceramic sculpture of a young woman of indeterminate age. SCP-3693 can only be seen by observers when their eyes are closed. Despite being visible through closed eyelids, other barriers, such as walls or doors, will obstruct it either in part or whole. It is typically observed hovering several centimeters above ground, but will occasionally come to rest if it has not moved in some time. When observed, SCP-3693 will quickly approach the observer, entering the nearest unobstructed space up to several centimeters away, while turning to face them. Depending on the observer's height, SCP-3693 will move to hover at eye level. If the observer moves from their original position with their eyes still closed, SCP-3693 will follow in front of them, maintaining the same distance at all times. Once the observer opens their eyes, SCP-3693 ceases all movement. Even when not seen, SCP-3693 occupies space and can be acted upon physically. It does not appear capable of moving through walls or interacting with doors. Subjects who observe SCP-3693 often report the feeling of being watched. Long-term exposure typically leads to moderate unease. SCP-3693 has taken no hostile action while in Foundation custody. Addendum 3693-1 Discovery SCP-3693 was discovered in 1995 on Hashima Island, Japan, by Foundation personnel investigating local legends regarding the ghosts of a woman killed there by a jilted lover. While investigating the basement level of an abandoned warehouse, agents observed SCP-3693 pressed against a glass divider, following them when their eyes were closed. Another investigation of the site discovered an abundance of crushed concrete debris and twisted rebar, as well as several floor drains clogged with blood and fecal matter. The corpse of a woman with a broken neck was recovered nearby. After securing SCP-3693 and moving it off site, Foundation agents returned to the warehouse to continue their examination of the site. The basement could no longer be located. An investigation into the identity of the recovered corpse is underway. SCP-3693 was discovered in 1995 on Hashima Island, Japan, by Foundation personnel investigating local legends regarding the ghost of a woman killed there by a jilted lover. The remains of SCP-3693 were found in the basement of the basement. The remains of SCP-3693 were found in the basement of the basement. The remains of SCP-3693 were found in the basement of the basement.


No matter where we live, how old we are, what we look like, health researchers have discovered that 90% of having a first heart attack can be attributed to nine modifiable risk factors. The nine factors that are threatening our lives include smoking, too much bed cholesterol, high blood pressure, diabetes, abdominal obesity, stress, a lack of daily fruit and vegetable consumption, as well as a lack of daily exercise. But Dr. William Clifford Roberts, executive director of the Baylor Heart and Vascular Institute, and longtime editor-in-chief of the American Journal of Cardiology, is convinced that atherosclerosis has a single cause, namely the cholesterol, and that the other so-called atherosclerotic risk factors are only contributory at most. In other words, we can be stressed over weight-smoking diabetic couch potatoes, but if our cholesterol is low enough, there may be just not enough cholesterol in our bloodstream to infiltrate our artery walls and trigger the disease, suggesting only absolute prerequisite for a fatal or non-fatal atherosclerotic event like a heart attack is an elevated cholesterol level. It was not appreciated until recently that the average blood cholesterol level in the United States, the so-called normal level, was actually abnormal, accelerating the blockages in our arteries and putting a large fraction of the normal population at risk. It's our number one killer. That's cited as one of the reasons that cholesterol controversy lasted for so long. An unwillingness to accept the notion that a very large fraction of our population actually has an unhealthily high cholesterol level. Normal cholesterol levels may be terminal cholesterol levels. The optimal cholesterol level, the optimal bad cholesterol LDL level, is 50 to 70. Accumulating data from multiple lines of evidence consistently demonstrate that that's where a physiologically normal LDL level would be. That appears to be the threshold above which atherosclerosis and heart attacks develop. That's what we start out at birth with. That's what our fellow primates have. That's the level seen in populations free of the heart disease epidemic. But we can also look at all the big randomized controlled cholesterol lowering trials. This is graphing the progression of atherosclerosis versus LDL cholesterol. More cholesterol, more atherosclerosis. But if you draw a line down through the points, you can estimate that the LDL level at which there is zero progression is down around an LDL cholesterol of 70. You can do the same with studies preventing heart attacks in the first place. Zero coronary heart disease events might be reached down around 55, and those who've already had a heart attack in trying to prevent a second one might need to push their LDL levels even lower. Atherosclerosis is endemic in our population in part, because the average person's LDL cholesterol is up around 130, approximately twice the normal physiologic level. The reason the federal government doesn't recommend everyone shoot for at least even just under 100 is that despite the lower risk accompanying more optimal cholesterol levels, the intensity of clinical intervention required to achieve such levels for everyone in the population would financially overload the healthcare system. Drug usage would rise enormously, but they're assuming drugs are the only way to get our LDL that low. But those eating really plant-based diets may hit the optimal cholesterol target without even trying, just naturally nailing under 70. The reason given by the federal government for not advocating what the science shows is best was that it might frustrate the public, who would have difficulty maintaining a lower level. But maybe the public's greatest frustration would come from not being informed of the optimal diet for health.


I am Shantanu and I am an architect at Flipkart and they are basically architects get to do a lot of different kind of things. So one of the things that I do is take care of a few of the analytics sections at play. So most of the things that I work on are face towards the developers versus matrix and data for business. So Hyperion is primarily a system which is used mostly by developers and options yes etc. There is one more system which is called Bigfoot and that is used for business level analytics. So mostly I will concentrate on this guy today. So what is it? It is basically an event processing system which is used by dev teams to get insights into what is happening in a deployed system or on apps it is used by on call for debugging customer service issues for some cases specially issues arising on apps are on the web not the main website but we have a web reader which is used to read the books on the website. So any kind of issues which is actually pretty JavaScript heavy. So it has to work on a lot of different kind of platforms like couple of days back we got one guy who was using Firefox 3 on Windows NT ok. So debugging those kind of issues is very difficult because we do not even have all of those items locally all of those environments locally so and it is used by business teams for certain use cases. So we will look at a few of the use cases. So this is one of the screens it is like showing so we have a in house storage system which we built it is a distributed file system and this guy showing events that are happening on that and like 24 hours and resource gate is the highest number of events from this particular application. So this is basically a monitoring screen and we have a trend graph also like over a month how many of different kind of events happened from a particular system and there is also search and a few other functionality. So why did we need this thing so this guy actually came up from our digital team which I was a part of for some time I recently moved to a different team. So there we were actually developing apps to read the books on different platforms windows iOS Android web ok and we were also building the back end infrastructure to support those apps ok for example download systems right like some download system which are about samples they are cached some which actually send out the books they are obviously not cached they are DRM etc etc right so they actually go so we needed to monitor all of those systems right and we needed to know like how many people are reading books how many books were downloaded ok and if the app crashed what was the state of the system before the app crashed or the app before the app crashed ok and CS issues like somebody comes and says ok I am not able to download the book I already paid for it ok what what what are we supposed to do now so that right JavaScript error I mentioned it is like a big problem to debug remotely especially you do not expect your customers to be a lot savvy about like what is happening on their index DB inside the browser etc etc right so yeah besides that there are few small business use cases like we have ebooks which we get from multiple sublet say penguin or random house etc so they upload the book right after they upload they come back and ask ok I uploaded this book what happened to it ok I need to know what happened to the book it was supposed to go live I did not go live right and besides that we have this guy is now also integrated with our retail app so retail app is it has about I don't know about a couple of million installs I think ok and so we send out some marketing notifications etc etc so it is about when was this notification sent why was this sent it it came from which downstream system etc etc so these are like some of the major use cases for Hyperion and there are also other use cases which we as developers use like if I pushed some new code and there are certain matrix I want to see if that some section of the code is actually getting it right if there are errors what kind of errors are happening and I want to be alerted in those situations right so all of this kind of requirements came up so at that time we were starting off with our some some internship program so we started this guy up as one of the things that in as one of the projects ok so and we came up with a sort of expensive problem statement list it was like so first requirement was everybody that wanted to use this gave us the primary condition ok we will send data but we should not slow us down right so that was the primary this thing because somebody click download it should immediately start downloading it you cannot slow down downloads because you want to purchase some of the download information somewhere in your system right and we have a lot of different kind of technologies that use ok so some people some guy will use kala that will use ruby others will use java somebody will use python so this guy needs to work with all of that at least the event push part onboarding should be simple and there are many teams and if it is complicated to push an event nobody is going to use it and click so that is not something that you would want and there are also some basic guarantees that you need to give if you are planning to build this kind of a system the minimal part of that is that once an event once you accept an event you cannot say that you have not been able to purchase the event due to some reason ok that is a guarantee that you have to give that if you accept an event you have to push it out ok how well the database is written there is only one truth about it is that it will go down for some reason or the other ok so that is reality of life ok if anything else a couple of your boxes will go down in your cluster you cannot stop that from happening ok so the system that you are writing should be resilient to that resilient to that in the sense that you can have a slow down in the message that is coming say if your processing latency was 20 milliseconds it can go up to say 100 milliseconds but the system should not go down and even if it goes down you can still take messages and basically when you are back up you should be able to process that very very fast and get up to speed ok and if you have certain critical functionality based on your event stream you should plan in such a way that even in case your database or something goes down you should still be able to not like able to support those critical use cases for example alerts ok let us say if you have a critical alert on say for example your checkout one of your machines which is doing user checkouts being down it cannot that particular event cannot get blocked because you are not able to purchase to the database ok some more so there is a lot of different kind of analytics that you can do on your event stream but we decided to go with a small and mostly used subset ok which was querying so you can query an event based on the fields that you are sending one sending through it second is grouping like group by different component a group by a publisher and a book and the different components that it went through ok so group by count right and trends right and of course histograms that I showed you like histograms are important because they give you a visual representation of the state of your system ok if it is 0 you know something has gone wrong you do not even need alerts for that so visual representation is very very important most of our people most of the people who wanted to on board hypogems they said ok we will make our own consoles we do not want generic this thing we know what fields we will query on we know what graphs etcetera we want so we will make our own console so we had to have a set of API's that simple API's that those guys could use right and back in so the data model that we are storing we knew upfront that the all the different kind of use cases that people are going to do on this guy probably we will not be able to code it up as a platform team ok so individual teams will probably write their own custom analytics so the storage system needed to be somewhat friendly to that so this is the base architecture that we came up with so these are the guys who will push events and there will be an API which like this guy is just a API to ingest events ok it takes single events and it will take batch events it has no other function ok so from there we had to put it in some messaging system which will work as our which will work as our staging area right so from there we will use some kind of a stream processor and put it to two different stores ok one is the short term query store which will be used for the base functionality that I said graphs like histograms queries like simple search queries and groups and trends right and there would be a long term store where which which people will run their own custom jobs of ok and the query store will expose API on the query store and people can write their consoles on top of that or they can pull data from the backend store and into their own storage and create their own APIs so with that we started our design this thing and now so basic architecture was fixed now we had to fix the text stack right so first was the messaging system what to choose so here we wanted replication we wanted parallel read capabilities and we wanted the system to be resilient to downstream failures that means that if you are reading once from the database and so if you are reading once from the queue and you are trying to write to something if it fails I can come back again to write again to read from it ok first second is this is valuable data so others might want to write others some other system which will use the same data stream right so that guy should also get the same functionality ok so there we chose Apache Kafka at the time ok so the problem with this was when we started off with this the stable version of Kafka was 0.7 ok which did not have replication per say at least not inside the system but that is something that we needed because of the base guarantee right that if we take an acknowledge a message we cannot go back and say that we could not persist it so we wanted replication on the queue which was not present there so we decided to go ahead with Kafka 0.8 which was beta 1 at the corner frame ok so the good thing is yeah it's open source it's extremely fast way it's very very fast so the base philosophy of Kafka is that if you are writing sequentially to a particular file or you are reading sequentially to a particular file from a particular file your reads and writes are almost as fast as reading from a traditional memory ok so since our use cases mapped very much with that and we were never planning to do any kind of random six other than in failure scenarios we decided to go with this ok so now if you are starting off with something like this I had RG to take a look at a project called Luxon LUXUN ok I have not used it but it looked pretty promising I have used their other projects it's the source is available on GitHub you can take a look I think it's from a Chinese company anyways so yeah as I said it was beta and the other part of Kafka is the server has practically no control so if you guys have used something like travidian queue etc where you actually attach a queue to a consumer to the queue and the server will send you messages ok here it's a little bit different you have to specify which offset you are going to read from ok so every queue or topic as it is called in Kafka is broken up into partitions you use a single thread to read from a particular partition and you specify an offset so you say ok from this partition I will start reading from partition offset 20 say and it has metadata calls that you can make to the server to get what are the valid start and end offsets on the system ok so one of the major things that you have to do if you are working with Kafka is to figure out how to store your offsets so Kafka has two sets of consumers which is one is called a high level consumer another is actually the low level consumer so if you are using the high level consumer it has no act kind of mechanism ok so if you ask for a message it will write the offset to zookeeper and then give you the message ok what we wanted to use was the low level consumer where you have absolute control you can read from any particular offset but in that case you have to maintain your own offset so ingestion API because of the multi platform thing we did not want to go with anything fancy and we actually wanted to see how much latency this guy was adding at the same time we decided that we will go with the fastest available framework so we decided to go with the rest express which was which we saw after evaluating a couple of them which like drop wizard and rest express and few others we found that this was the fastest guy ok honestly speaking we would have tried out spray at the time which we did not because but yeah this guy is pretty damn fast actually so and it's also very lightweight ok and as I said in our API server which in our ingestion API we basically wanted to do almost nothing other than just writing to the queue so storage as I said it was broken up in two parts so the query store where you keep stuff indexed and your data will get TTL doubt ok so in query store we you don't actually store all your data you store a relevant amount of data and for certain time like that depended on the team and when somebody wants to onboard this guy we ask him like how much variable data do you want say some guy will say one month others will say two month some other guy will say ok I can do with one week etc etc right so we work with that and the long term store where we keep all data ok so and that is also our golden source in case our query store goes down we have scripts and code ready to pull data from the golden store back into the query store so at the time when we started basically what we decided to go with was the short term store was going to be MongoDB and long term store was going to be edge based in the long term store basically we wanted no features it was just a key value dump for us and we have a centralized cluster across flipkart like we have two three clusters so we decided to go with the fast right cluster that has off support and all of that so we decided to go with edge based for that but we could have gone with any other storage for the back end which works well with key values right and the query part we went with MongoDB not an not I don't know like how many people would do that if you are talking about a real time system but we did some tests and it was it it's actually pretty good ok talking from speed and why we went with this was it has a good set of functions that you can actually use for example aggregates and groups right and trains and in aggregates basically you can create pipelines of different things for example in which you can do fairly complicated so few days back I wrote a eight segment pipeline which can actually create a funnel of all the events across the a particular app ok this many people started reading this many people of that finished etc etc right so it comes with its own quirks of course like every database but we saw that most of our use cases were getting supported with this right and it was it's pretty easy enough to maintain ok and the storage architecture that we use from MongoDB is basically we have shards so we are we were till now using only one shard so basically we had three machines and it's critical ok so three machines is something that we felt was the optimal size to use a shard ok so you need one master and two replicas for that ok any in a in a particular replica set you need three machines so one of them will go down or you might have to take one note down voluntarily for certain things for example what MongoDB does is it will not it will not release space ok so let's say you have an app which was pushing a lot of events due to some spike for sometime which took about 100 gigs of data right and that guy got TTL the way right that spike all the data what TTL the way but that place is not released ok so after sometime what will happen if you have not taken this into account you might have to take one note down delete its data and rebind it from the other notes which is fast but it is you cannot live with that kind of latency ok because our architecture is such that our queries never hit the primary ok they always hit the secondary and primaries are only for rights ok so these are certain things that we knew and some of them we learnt along the way while we were using Mongo like it's pretty good we are currently in the process of moving away from it but I'll discuss the reasons later on so processing pipeline we wanted something that was good with retries and it was storm without a question ok so storm there is a seminal talk by Nathan Mars who is actually the creator of storm very describes the philosophy behind storm ok and the base philosophy is that your systems will go down ok even storm itself will go down storm has supervisors and members which is basically the central server all of them will go down your GUI client will go down for storm ok but the thing is your everything should be come back should be able to recover once the other dependent components are up ok so storm is basically built on the philosophy of being very fast obviously and secondly recoverability ok so we were using storm we decided to use some obviously at that point of time Kafka was so one of the most complicated pieces that you might ever have to write on storm is basically the spout so spout on a storm topology which is basically a computing basically a representation of the computation that you want to execute on a storm cluster is called a topology so inside a topology you have something called as a spout spout is the guy who actually reads data into the cluster ok and bolts are guys who actually process the process the data right and there are commuters etc etc so you can go through the storm documentation to understand all of that but the writing a spout is fairly complicated stuff ok and the good part about storm is there is a good community of people who keep writing spouts for different kind of data sources you have spouts for HBS you have Kafka you have rabbit in queue and lot of different kind of spouts interesting ones Twitter firehose etc etc so when we started obviously there was no spout for Kafka pointing and Kafka pointed the protocol is actually fairly different from 0.7 like 60 70% different ok so there was no question of being able to use a lot of the code that they were doing but still we decided to go ahead with it right so now with so basically the major parts we have covered we have the queue system which we decided to be Kafka which was going to act as our which is going to act as our staging area right then the processing part which was this which we decided to be storm and two data segments one was the query store which was going to be MongoDB and the long term store which was HBS right now what what what do we do actually in the storm cluster so we decided to go with HBS as the offset store right because we knew exactly what we are going to write so it was never going to with exactly what we were going to write as well as to read so it was never going to be a scan it was always going to be a get or a put which is extremely fast on HBS okay so offset decided was going to be in HBS right and MongoDB we did not want to hit MongoDB for frequently used queries so for example histograms so if you open the Hyperion console the first thing that comes up is your histograms and if you visit Flipkart you see many people who have using Hyperion I have actually that console open on one of their screens or on some monitor etc right so that is quite a quite a bit of place which did not want to put MongoDB through that so basically what we decided was to do certain kind of pre-computations at least for the matrix like how many events are coming in etc okay other thing was we did not want to expose all of the functionality given by MongoDB because of several reasons first is not every database is optimized to do everything okay secondly we wanted to keep our options open when we were talking about the query store okay so that is why we wanted to expose only a few functionality even on search say for example you are searching on an integer field we wanted to give you all the normal operators like less than greater than greater than equal to etc etc but some not something like for example module actually that's a bad bad example so string search we are probably going to give you equals not equals etc but we are not very keen on giving you contents because MongoDB is not very good at doing content queries even on indexed fields okay they have done certain improvements in that field but at that point of time that was not an option so what we wanted to do was in the cluster while we were processing the events we wanted to do certain amount of metadata analysis on the events that came in so once we get an event and that has different kind of fields and we wanted to see which field was integer which field was flow testing etc blah blah and stored all that metadata information somewhere right when you are carrying from the front end and even from the API is you could hit a API to get to the metadata for a particular event or event set and use those but operations only to query other things will raise an exception and if you are doing it from the console they want even visible so our failure recovery is pretty simple in storm either we write to both or we fail okay if there is an outage on say H base or MongoDB it will fail it will retry there is no asynchronous write okay we in the bolt so bolt basically a topology is arranged like a series of operations think of it as write to H base write to MongoDB and then commit the offsets to H base right if any of these three fail the event will get processed again okay one more thing that was important was since this was going to hold a fairly large amount of data we wanted to divide the query space okay so dividing the query space was simple enough we decided to come up with the concept of apps okay so an app is basically a logical separation so for example ebooks ebook reader is an app that and ebook delivery is an app okay like that so it's like a logical separation of the whole event space so what does an event look like so event looks like this we have a mandatory header part where you give a few things like app event type is for the user only like reader crashed book downloaded error book download rejected due to ip conflict etc etc right so this is something that makes logical sense to you platform is since this was one of the major use cases was to be able to use it with apps platform is a component in the header itself where you say it's like Android or iOS etc etc and then we have timestamp instances some id to identify where this guy is coming from for example if this is coming from a particular machine not a app not a handle device this white content the IP address of the machine okay and event ID is just an ID for the event you can just generate and put some you ID or some other string that you want so the key for an event of our system is actually a hash of all of these fields and all of these fields are mandatory okay the interesting part is actually the data so in data you can basically send any type of field any valid JSON object so once you send it you can also have nested JSON etc etc and through our metadata analysis we come up with a list of fields that you have created and what are the different types for that as I said we have API from which you can actually retrieve the data so for hyperion actually instead of one we have two topologies okay so the first topology I described fairly in depth like what we do we do metadata analysis we write to both stores we commit the offset and then return the other guy actually writes to a secondary Kafka cluster okay and we have a small library which has a sort of a predicate system predicate language which you can use to read a subset of events right so this helps other guys to build systems say a alerting system you want to push some new code you just want to see monitor it for a day to see if there are certain sections of the code that are failing so you hook into the secondary cluster with the subscription system and you pull events from that and only error events from that so you write a small amount of code which will send your mail if that kind of event comes so those kinds of use cases and as you see these are use cases mostly these will be cases which cannot fail due to a data store failure so this guy is written to by a separate topology okay so the status currently is takes around 35 40 million events a day we have a 3 node Kafka cluster to worker nodes on storm 3 MongoDB node cluster around 900 gigs of data on the cluster and about 5 6 terabytes of data on HBS we are doing a fairly large amount of upscaling on this so all of this will at least double the events will actually go up like 5 6 times so Kafka is becoming a 7 node cluster and workers are like 2 2 4 2 8 MongoDB is increasing to 6 7 and this guy the query data will go to 3 terabytes HBS will also work accordingly at certain things we found out while doing it is that in the ingestion API basically don't do anything okay basic amount of checks which let you keep the system functional just do that for example if you are dependent on the field of your header just make sure that all the requisite fields are present and just push okay don't do anything else batching is mostly a no brainer but this actually made a fairly different fairly good performance impact for example if you are writing to Kafka writing a single event and a reasonable size batch takes almost the same time okay so in the Kafka protocol itself they have support for batching where they compress multiple events into one one particular message and then forward so that speeds up writing very very fast similarly MongoDB writes are fast HBS if you are doing a put list instead of a put where you put like 20 30 events at the same time it will get very very fast one more caveat about MongoDB you should not call update all anything a lot okay so call update it will become a problem if you use it as long as it use it as some kind of a app and only store is very good okay one more thing about Mongo which we are not using but in case you plan to use it is that if you are writing to Mongo try to get the object ID as the ID for the document okay that's very fast so Mongo has a system where it can generate an ID for your document that key is well the key generation actually is very fast okay and it contains certain other information also which you can leverage but that was not an option for us due to various reasons another thing is if you are planning to use Tom it has a nifty feature which is not very well documented where where actually your processing units get a context object where you can save your connections and other frequently use things so once it spawned on a cluster node that guy actually lives okay it doesn't die for every batch so that code is persistent so if you save something in your topology object in your topology context you can retrieve that it's like a map okay so you just save it with a map and object and type first and use it later on so it's actually very fast very fast in the sense our processing for an event came down from 2000 millisecond to 45 milliseconds right after we started even context okay even when we were batching inside this guy right so yeah so that some one important part is basically how to set up your expectations about what you are going to do right and the major part that I try to explain to everybody is that the system will only facilitate getting and seeing your data if you are putting garbage into it it is completely useless so the point is to get a good balance okay you should put enough data that lets you analyze systems but not so much that you are actually for example don't send a 1MV message okay there is I can think of almost no event level data that can have 1MV of context okay anyways that might happen in some case but my point is that what I ask everybody when they are planning to onboard Hyperion or any other this kind of system is do you know what you are going to push so coming up with a schema of events is very important okay before you are writing from this kind of a system analytics what you are going to build on the what you are going to build on the real time set should be minimal and that should of course follow like cover whatever you want to do with the data but it should be minimal like it should be the minimal set like any other fancy stuff that you want to build on top of it you can do it offline you can have a pseudo real time kind of thing where you are processing a delta of the data in the back end right from your permanent data store using some table scan or some timestamp based scan right and keep generating that data and store it in a cache and when people ask just send it out from the cache right do not put too much unnecessary analytics pressure on the query store if you keep it simple as was said in the last presentation okay your focus should be on simplicity if all like so comes basically of all things that you can do always go for the simplest thing especially if you are looking for speed that should be a primary focus speed speed and nothing else right and you have to consider scalability as an integral part of your system so every component that you choose for this kind of a system you should consider scalability as a primary requirement okay Kafka add a few nodes you can add partitions it will get balanced so some balancing will happen and you can distribute the load right same for MongoDB you can add one more shard and it should be okay right and same for HBIS of course I mean so scalability should be an integral part of your system so besides hyperion we have a lot of other things couple of other systems that we are working on okay one which I am actually very proud of is what we call as a pre-cog as the pre-cog system okay so this actually started up as a hack dev project as a hack dev project and so what this guy does is it creates a computational cluster so there is a devian package you install it somewhere it becomes a part of the execution cluster it has a server component so what and what we can do is basically write small primitives that take a message do something and then release the message okay or not release the message at which point of time the message execution stops so what you can do is so a problem with storm is the deployment of a computation is actually some sort of a code deployment okay so it's not like you can do it from the console it's not like that okay it's code deployment actually this guy what you can do is it gives you a tool sort of a toolbox okay and like storm it has a source you can take a source attach a few computations to it and just deploy it click click click right this one to create a computation and deploy okay on your cluster and you have control like on how many nodes this is going to execute etc etc right so we are working on this hopefully this will get open sourced some part of time so that's one system other part is actually let me come back to the data storage so the problem with MongoDB is and I think you must have understood by now indexing is a huge problem in databases okay like you can have indexes for your computations but with time as the number of indexes increase it will start to affect okay problem with Hyperion now is it's fairly popular so a lot of teams want to use it they want to create indexes and we don't have a lot of control so sometimes from the console they'll fire queries on fields that are not indexed okay which will affect everything across the cluster so so we wanted to have something which is built on indexing okay and we knew about that at that point of time also that was elastic set okay the problem that elastic search at that part of time was there was only one type of thing that you could do on it from an analytics point of view which was aggregation which was basically faceting so now in the new version they have come up with the aggregations framework which is actually quite powerful okay I urge you to take a look at that actually very very powerful so what we are doing is we are writing a data access layer you can call it a data access layer which looks like a database where the data files are actually data files is actually edge base and the indexing is actually elastic set okay so you query data on elastic search and you get it back from the data actual data comes from the edge base cluster so we are working on that that's called hockstrat again that that might be open source fairly soon it will go into production soon the other pre-cog right now is being used as a log aggregation system by multiple teams it does more than a hundred million events every day so these are the resources of custom rest express questions yeah so yeah actually we did take a look so far as distribution and replica where primary yeah so what is asking is basically did we look at other kind of queuing systems when we were looking for when we decided to go with Kafka so the point is actually we did and at that point of time with our use cases that was mostly the only guy which was fairly stable and matching but as I said that looks in project it looks promising so probably you should anybody who is planning to do it now should probably take a look at that spout spout it's also written by Nathan was so the question is did we consider using Kestrel while we were going well we were using while we decided to use Tom Kestrel yes we considered but even Kestrel was not so stable at that point of time and there are some of our other teams were using Kafka and they had only good things to say about it so we decided to go with Kafka we wrote the spout in case you want to know now Kafka 8 is stable and there is an official spout for Kafka 8 that you can use ready made stop because the long term storage we were one of so the question was why did we not go with MongoDB as our long term storage so the point is for long term storage we were expecting large amount of long running jobs on this guy and to be hit way more than how the query storage it like scans the number of scans would be high so most of the teams are comfortable using Hadoop for that okay so pulling the data using scoop etc it will make a sense a lot of sense and so we decided to do it actually it amounts to one-fifth if you look at it it yeah it contents index and secondly the data is not evenly balanced some guys have more data than others so yeah yeah so multi DC yeah so we are it's not yet multi DC we are planning to do multi DC we should be fairly simple if you are planning to do multi DC with this you should take a look at so Kafka has a component that is used exactly for this purpose you can copy from one system to another across data centers okay yeah so yeah you should not at least the way I have seen when connections go I think it's a bad idea to write directly to database from one system to another one DC to another it should be content you should transport the data from one system to the other from the queue it's staging right you have backup so so there's one more reason okay cross DC rights will be slow right and on Kafka basically there is a TTL like in MongoDB right so what you're doing is as you do slow rights your events will for sure come faster than you are writing right so you'll develop a lag irrespective of how many number of partitions you are so after some point of time say seven days or eight days you'll start losing messages so that's probably not a distance better to copy Kafka Kafka and then write from that thanks