Most people when they think of spreadsheets, they think of Microsoft Excel and Google Sheets is very similar to Excel. A lot of the functions carry straight over. But there are some differences, part of it's because it's actually a web sheet that gives it a lot more functionality in that respect. But some things don't operate quite the way you would think. If you want to make a bar chart and make one of the bars a different color in Excel, all you got to do is click on that bar and manually change its color. But in Google Sheets, you have to do it differently. Say, for instance, I have my data here on social media followers, and I want to draw attention to Instagram. Well, it turns out that the way to make Instagram's bar a different color than the others is to actually make a grouped bar chart.  And then I'm going to take Instagram's value, and I'm going to move it over. So this is kind of a funny data because no platform has values in both of these columns, they're in either one or the other. But watch how this works. I come to social media followers, and I click insert chart, and it makes by default a grouped bar chart, but it's a really funny looking one because everything's half width, it's expecting information from each of the columns. But if we come over here to stacking, and we change it to standard, then we suddenly have what we want. There's a couple of things I want to change, however, that I think are important. Number one is I want to get rid of this legend, it's actually creates confusion. So we get rid of that. And we need a real title. Social media followers by platform. And then I can delete this one here on the bottom, by just deleting this text over here. And now we've got a simple bar chart column chart actually, where we're able to draw attention to one particular category Instagram, by putting it to value in a different column and making a stacked bar chart. It's a funny way to have to go about it, but it still lets you get to the same goal of making a clear visualization and drawing attention to the important values.


I'm a staff engineer at VMware. And in this presentation, I'll talk about our experience of implementing a configuration time series store using Foundation DV and the things we learned in this process. But first, I want to thank the Foundation DV team and all the sponsors for organizing this event and having me here to give this talk. So to give a little bit of context, Network Insider is VMware's security and network management platform to help large enterprises manage the data centers. It works by periodically collecting configuration state from entities inside the data center and then transform it to create an entity-relation graph of the data center. One can go back in time and look up the snapshot of this data center entity graph at any arbitrary point in time and then have more use cases that work against this graph, like search or analytics. There are many different use cases that we support on this graph. And they access this data in very different ways. One thing to note is that the system is hosted both on cloud as a hosted service, as well as given out as installs for customers to deploy it in their own data centers. It's important to note that when this is installed within the customer's data center, we don't have any access to the system. And so it has to deal with any failures that arise there and be able to come up out of it. So it was a previously modeled on Postgres as a set of tables and multiple indexes. We did not require foreign keys and just somehow flipped. OK, we're here. And we have thousands of such deployments. Each of those deployment is a cluster of size ranging from 1 node to 30 node so far. And we are growing the cluster size as we scale out more. The layer that stores this configuration graph is called object store that I'll be talking about today. It maintains time series of state changes for every object in the data center. And there could be large number of such objects, like virtual machines, access rules, ports, routes, and network flows. Different use cases access this layer in different ways. Some doing bulk scans using some specific attributes, like object type, version start, and end time. And there are others that want fast point access to this data. So it was modeled on Postgres, as I was saying earlier, using multiple tables and indexes on it. We did not require foreign key constraints and joins between the tables, but we extensively use indexes, grouping, and ordering features. But we face a lot of issues in large cluster deployments with this model. Firstly, there is no inbuilt HA or redundancy. So there is always a risk of us losing the data if the node goes down. Due to data base being hosted on a single node, it starts to become bottleneck in terms of both IO and disk size, as well as the compute in terms of number of transactions that we can run on it. And this load increases linearly with larger cluster sizes, where your database still is hosted on just one node. I do not know why it's going ahead. And periodic maintenance jobs like data deletion and vacuum worsen the problem by eating up into already scarce resources. So we explored different database replication options to resolve the problem of HA and redundancy. There are many tools that help with replicating the wall logs or with replicating the statements in conjunction with some orchestrator tools that detect failures and then promote a slave or a standby to master. We found these approaches to be very brittle and requiring a lot of manual supervision. We ran into issues like wall filling up the disk because wall slots are not being cleared fast enough. Diverse transaction timelines because of mistiming of promotion of some standby to master and need for manual rollbacks and thereby incurring data loss. So we gave up on it after spending quite a bit of time and still not being able to make it robust enough for us. We then evaluated some of the more popular natively distributed stores. And over time, we found that they were not sufficiently mature yet. We had a lot of edge cases around performance and stability. We worked with the community and the developers of these systems to discuss the issues we found. And we realized that these are non-trivial implementation problems that had not been encountered yet. And with time, I'm sure they will get ironed out. But it gave us a pause that if you are still finding such issues or more fundamental issues with database layer or store layer, we cannot risk deploying these in unmanaged environments. There's also a lot of confusion about what kind of guarantees these systems provide and how proven are those. The guarantees themselves come with a lot of caveats and knobs, and it makes it difficult to reason about. You don't know what you're really getting once you are too far into using the system. Many of these stores have a lot of moving components and external dependencies that make them difficult to harden for unpredictable environments. Finally, almost all of these systems depend on accuracy of system clocks. And they have serious consequences on correctness guarantees if the clock accuracy is not met. And we cannot guarantee this accuracy because the environments are totally out of control. And yeah, I mean, NTP can go out of sync by a few hundreds or milliseconds or even more, and we can't control it. So once the Foundation DB was open source, sometime last year, we had a discussion with devs on Wavefront team who are in the same organization as specifically Clement, to get the feedback of how the store would play out if we actually went ahead and tried implementing a layer on it. We took our time after it to understand the architecture and the transaction guarantees to evaluate if a non-trivial layer could build on top of a key value schema. We determined that to build our object store layer on a key value store, we required three important rates. High throughput, audit scans, low latency, point rates, and writes. Like by low latency, I mean met single digit milliseconds. And this is more of a short term constraint. Our current layer user are used to getting this kind of latency from Postgres system. And I'm sure with time, we can bring in more concurrency and batching to offset some of the latency, but at least to begin with, we could not go back too much on the latency. Otherwise, it becomes a non-starter. And finally, we needed multi-row transactions with a strong serializable isolation to ensure the validity of the data at all times. We cannot afford to corrupt the data by doing some partial updates to it and not leaving it in consistent state. So FDV seemed to satisfy all these. The transaction throughput rate that it provides was already much higher than what we presently expect. So yeah, I mean, it looked good. Finally, we did some specific workload performance test and failure test to ensure that the desired resiliency is met. It specifically concerns about auto role migration, no data loss, and no manual intervention for recovery. These are important things for us, because as I mentioned, these systems run in dark environments, and it is very important that they are healthy all the time, even in face of failures. So the initial modeling work started with mapping our data access patterns and tables onto the key value schema using the very flexible set of constructs that FDV provides. Some of these are key selectors that can be used to efficiently locate keys within certain offset, within certain distance of an offset. Version stamps are extremely useful. They can be used as pointers to connect rows, as proxy for time to create ordered logs to generate unique IDs, and so on. Conflict ranges and snapshot isolation provide much finer control over conflict management. And there are a lot more features that probably I'll go into more detail in the next talk later, but just gives a flavor here. We had to address some challenges around change log induced hotspots. So change log is a feature in our store where every change needs to generate an event or a log that someone else can listen to. But this creates hotspots into the system. And the second problem is FDV, due to the transaction limits, cannot handle large records. So again, these are some things that we addressed, and I will go into more details in the next talk that I have today. We had to create a CLI tools for layer users to access and manipulate the records. This was not a problem with Postgres because Table Schema had enough context. And using the PCQL CLI, people were able to use the existing CLI to access the data. But we had to create it. So this was something we realized later on that it took some time for us. So early on, we realized that there are a lot of important functions that are being repeated throughout the layer and should be centralized. First of them was global key value space management. Unlike RDBMS, which gives you concept of tables, where each new layer can start with new tables and work its way through, we had to carefully plan the global key value space in order to support things like multi-tenancy or any future extensions of introducing more layers on a common FDV cluster. We also route all the transactions through some common shims that handle some important aspects, the most important one being health check, back off, and throttling. So we do have notions of a lot of background activity to take care of the store. And we constantly monitor the health of the FDV cluster and then back off these periodic activity so as to not saturate the cluster too much. We have realized that FDV runs pretty OK if you're not saturating it. If you saturate it, then things start to back off one after the other.  Secondly, we do our own retries in case of transaction errors. For instance, we use retrieval transactions for supporting long scans where the transactions repeatedly fail and restart from the last point in five second batches until they make all the way to the end of the key range that we wanted to scan. So here are the exceptions or errors by design. We don't want to put additional sleep in between transaction retries. So we do not put any in case of two old transaction error that we recover. But if we get something more serious like a future version error, which indicates that storage servers are not able to keep up with the load, then we put extra delay between the retries to give FDV time to recover. There's another interesting aspect of throttling or limiting the number of outstanding transactions that we have on the client side. We notice that if we don't control it, then we could accidentally put millions of outstanding transactions within the FDV client library that gets run along with the layer code base. And that puts a lot of memory pressure on it. It allocates a lot of memory to hold those outstanding requests and then to get the data back from FDV server before delivering it to the binding. So this causes the memory to go up, memory utilization in the FDVC client library, and it never returns it back to us. So we have to be very careful about how many outstanding transactions can we keep and still have manageable amount of memory used by it. So I think there is some pending request on GitHub that the client library should periodically release the memory. But yeah, that is what it is right now. So this layer also provides some other functions like version caching for reducing transaction latency. Again, I'll talk more of it in the next one. We took some inspiration from FoundationDB testing, and this layer injects random failures in the transactions so that the layer code can be sure that it is handling the errors in correct way. I think, again, this is a feature already in 6.2 where the client library itself will introduce these errors. But we took it on early, and we have it in a code. Finally, we am a detailed metrics to capture transaction failure rates, latency, counts, and sizes. And I'll go over it in a minute.  So this is one of the screenshots from Wavefront dashboards that we have. So here, you can see that we are capturing a lot of statistics about individual transactions. How many of them are we doing? What is the total time they have taken? What is the size of those? And if we are seeing any errors, then what kind of errors are being noticed on each transaction? And this gives us a lot of information about what to prioritize. If you are seeing a lot of conflicts on particular kinds of transactions, we can go look into it and optimize them. This is, again, a sample dashboard that we have for FDB cluster monitoring itself. So Wavefront gives us pre-built plugins, using which you can go and integrate your FDB cluster. And it will put a lot of interesting things on screen. I mean, the ones that are highlighted here are the T-Log and storage server queue sizes, which are probably a few of the most important things that we go and monitor. We also wrote some command line tools for parsing FDB JSON output that we get. And we put it in a watch utility. So it refreshes every second or so and gives you real-time information about what's going on. And together, using this and the Wavefront dashboard, we get both kinds of information. Long-term patterns to correlate problems, and also short-time, like, live state of the cluster as we are doing things into it. So as a quick example, I'll take one of the problems that we are still working through. We noticed that our storage server periodically, so the storage server is on the left side, and on the right side is one of our operations from the layer which I'll be talking about. So we noticed that our storage server starts to stall periodically, where it is not able to retire the data that is coming into the queue, and thereby, the system then throttles and backs off. So we spent some time looking through these dashboards and noticed that one of our periodic operations of deleting the older data just directly coincides with the storage server back queue growths. And I mean, we tried to then think through it, like, what could be causing it? There were a lot of possibilities. It could be that the deletion is causing extra mutation overhead and just tipping over the amount of throughput that the given size FDB cluster can handle. It could be that the IO is stalling somewhere, causing storage server to stall. Or it could be some problem with the foundation TV delete path itself, or lastly, some problem in the layer. And we then rejected one hypothesis after the other, and we were left with that there has to be something wrong with the layer because other things would be noticed by a lot more people a lot quicker. And we realized that the only thing we are doing in the delete path differently is that we are packing a lot of individual row mutations in a single transaction. They are not large range clears, but they are single keys, like about 500 to 1,000 within a single transaction. And we experimented with and make that smaller to about 10, and you don't know what's going on. And you can see like the green line is where the change was deployed, and suddenly the worst queue size stabilized from quite a bit. And we still don't know what within FDB is causing this. I'm still in discussions with the FDB team on this. I'll get back to it once I have a little bit of more time. But yeah, I mean, it shows that there are certain non-obvious and ambiguous troubleshooting to be done when you are dealing with FDB clusters, and it takes time to work through those, but having these integrations at least gives you a good starting point and then make informed troubleshooting branches in the debugging. Finally, just to recap what worked for us. Efficient multi-row transactions with strong consistency, the very, very powerful guarantee. This is sufficient to solve a large class of problems that were traditionally solved using RDBMS. FDB gives us a very rich set of constructs and low-level data placement controls, using which you can develop a lot of different kind of layers. It is easy to operate, doesn't have any external dependency, very, very resilient, no dependency on time, which is quite a bit of a bonus. And a very strong community, and they are happy to help at any time. What we found challenging was we spent a lot of time on modeling and fine-tuning the storage layer. So for more conventional tables, I would still recommend go with a record layer or something that is maintained by a strong team so that you don't have to repeat the whole thing again. FDB gives us detailed status of the cluster in form of the JSON, but it took a lot of time to figure out what to monitor. I mean, it was through community interactions and maybe we can start contributing back what we learned, but I think this is going to be a big hurdle for anyone onboarding onto FDB. Transaction limits are kind of mixed back. Like, they bound your worst case behavior, and so things will not at any time go very bad, but then layer development on top of these limits becomes slightly more tricky. We found that FDB has slightly higher transaction latencies, about 25 to 30% higher than our Postgres store that was running, under whatever workload conditions that we had, and it is more sensitive to slow IO compared to, again, Postgres that we were using. All filtering and transformations that are done using FDB are done at the layer level, and if some of them could be pushed down into the key value store of FDB, that would be a big help, especially some sort of user-defined functions, like HBASCO processor kind of things, that would open up a lot more things that we could do. And finally, we realized as we were hardening the system more and more that it is difficult to control and limit the memory used by the client side of the FDB that runs alongside your layer, and I mentioned how we do it, but you have to be careful. Otherwise, if you're running a binding like Java, you would really have no control over how much of memory it has taken, and then if you have given XMX kind of limit, then the process won't even go down, and finally, some Linux OOM killer will come and kill your process. So, yeah, we need to be careful with it. And that's all I have. Thank you. Thank you.


So, ladies and gentlemen, very more welcome to the module 112, where I am going to discuss about the theory of E. E. Hagen. E. E. Hagen introduced the theory of the social change as an endeavour to explain how individual change their social status in order to gain a social respect. Very important. Here, you see a new endeavour of social change. Social change, as I told you, you must have heard the name of Mehman Biradri. I met a snake, it doesn't take its name just because of the copyrights issue. But they said that I came from Sakhar, and first of all I worked as a mehndi. Then I sold bangles. And after that, I found out that there was something about Pink Salt. It kept going on and on. Today, the biggest range of the Himalayan salt is there. And that means that after that, they also worked on that Mehman Biradri. You must have heard that chenotes and mehmans are a special culture for them. Do they support each other? Do they do better to come forward? Do they help each other financially? Do they create space for each other? Does Mehman make a difference to Mehman? Does Ismaili make a difference to Ismaili? Does Chanyoti benefit Chanyoti? Does he create space in that area? Yes. These are the questions I am leaving you with. Remember that I did not comment on it. But when people take care of each other in some special groups, they take social change. And certainly, a special cluster is prominent to you. Because they gain respect in the secrets of success. I will think well for myself. Definitely, I have done well. It will be good for me too. Remember that social respect has become a minus from our culture. The people you see in bad situations, they don't keep themselves well and pull each other's legs. That is why they are out of the social culture.  You can see them in India or Pakistan. The people who are becoming stronger, they take social change which gives them respect. Mr. Hagan is talking about western philosophy. The core notion that drives the sociological theory is that when the individual feels that they are no longer respected by the society, they tend to implement innovative way to buy mean of which the social status can get positive. It is transformed. I have told you that you need to take social change and social respect. The second idea is the social respect for the entrepreneur. There are many ideas in which in recent times, I wanted to recommend a movie to you. But I will give you an example of Sahara group. You have seen that a person is the smallest person according to his personality. But he takes such a big social change and develops a public financial market.  You can see that Sahara becomes an airline, Sahara becomes an industry, Sahara becomes cotton mills and I don't know what it becomes. In the same way, you can see that from where the Dharbhai Ambani comes out and such a big and today's Reliance group has a very big name. The one who runs Gujarat, the one who runs India, the one who runs the government. So, this social respect transforms. I will give you an example. There was a man according to his personality. He was one of many people who had no respect in the society. But his job was to wear a suit and then he would sit in other educated people's seats. He had a better car than a 2TB bike and with no time, he would do any property business for 5 years and then he would print and do whatever he wanted. He reached the Range Rover and then there are complexities that we have to minus. I am also telling you, you don't have to go to the complex. You have to remove it but some people have complexity. Ultimately, he reached the Range Rover on land cruisers, came to big houses and DHHM. I am telling you my personal observation. His social status and status also changed but from his table, his way of speaking, he could not change from where. Then he put a lot of money on his car. When he put a lot of money, I said you are not good. How do you put more money? He said after all the amount, money and financial level, who will not consider me as a good person? And my son, my son and my son's son, all these will be good. So, like in Punjabi, the tradition is that first of all, jeem is jula. It is called dharzi. It is called saiyad. So, this is what I told you about Punjabi. So, you can change even zaat path and transform into the biggest zaat. So, you can do all this but instead of going into complexities, let's understand this further. How do they regain their lost status? You can regain your lost status. You can change your entrepreneurial activities. Then it says that entrepreneurs are sometimes referred to as a public entrepreneur. Civic entrepreneurs are social innovators. I have given you three examples and also my own observation. These parameters have been changed. Civic entrepreneurs, civic innovators are public entrepreneurs. They don't let people come from the gate. They sit on those places so that people can't start meetings without them. That is, their status comes so far. So, how we can do that? Adopting mission to create a sustained social value, not just private value. One, then is a recognizing and relentlessly pursuing new opportunity to serve that mission. Second, your target should be very clear and you are going consistently on the mission. Reengaging in the process of a continuous innovation, adapting and learning. I give you an example of that. He is a peer-to-peer. If I give him a fictitious character or if he finds out, it's a good thing. So, you see that there was a very good thing about him. He always used to say that I should be taught in English. When we said that you don't have the potential and he said that you don't have it, then I have worn the suit. Now, if I remain silent, people will think that I am an Englishman. I said that it is a better idea. So, you have to adapt, learn and go ahead. Now, exciting, boldly without being limited by the resource, currently in hand and exhibiting heightened accountability to the consequences served and for the outcome created. Now, here you see that we have to reach that outcome and according to Mr. Hegan, the status of the culture and the social culture and the status of the culture where the required self-respect or social respect or societal respect is available to you but you have to go on these parameters. If you say that you will gain something, it is impossible. Thank you very much.


Ideas are at the heart of what we do at Fingers 50. Our mission is to identify, rank and scan the very best management ideas. We're celebrating the publication of the Transformation Playbook, a new book we've published in conjunction with Brightline. We appreciate their partnership and support. Copies of the book and many other books are available outside. Please help yourself take as many books as possible. So, without further ado, please welcome to the stage Ricardo Vargas of Brightline to kick off Fingers 50 2019. Brightline Initiative was created to try to understand why there is a massive gap between ideas and results. That concludes the day's activities. We now have two hours for tonight's celebrations, when we will be handing out some awards, announcing the new Fingers 50 ranking. Welcome back to those of you who spent the day with us, and a heartfelt hello to those of you who joined us for this evening's celebrations. Fingers 50, I think, is a fabulous organization. It's an explosion of ideas from all the people that we read about and talk about and hear about. I'd also like to thank the Brightline team that work so closely with you all. Thank you for giving them the opportunity to share the work that they do. And the winner is Chris Clearfield and Andreas Tuzzi. Thank you very much.


Okay, it's 5 15 and we'll call a meeting to order and certify that What I see we have a quorum if everyone could stand for the pledge of legions. I pledge a legions Little feedback there Okay First of all first thing any correspondence Sarah. Okay. Oh, yeah, can we Can everyone not like either Put on their mic or whatever and take attendance here Trent are you there? Yeah, I'm unmuted. Okay Patrick's here Tom you're there, right? Mike and Julie are there Alexandria is there. I'm here rich can hear me. Yes. I do We're here Sharon Mike, I mean Sharon mark are you both there? Yes, we are okay Ruth is here Trent, are you there yet? Okay? I think we're all Okay, we're all accounted for Yeah, I don't see any renaissance Who's caller one is Cole. Are you caller one? Take it a guess. Don't know Cole, are you there Cole? Are you caller one? I don't know. Okay? Well, we'll just so the people that I have is not present are Alderperson Ackley Cole Phillips Anna Shane and Henry Shane Okay, okay. Okay. Correspondent Sarah Yes on October 28th Katrin from Esslingen emailed myself and Bob quashus and John Keckinen with re With a proposal to begin a project called Coffee with the German to assist Esslingen's fire department staff with getting the opportunity To utilize and refresh their English language skills This would consist of weekly 30-minute meetings via zoom and Between that would be between up to five Esslingen firefighters and then volunteers from the city of Shebaughan Carly Campbell who is the administrative coordinator for Shebaughan's fire department is going to serve as our representative in this project and She's going to be working on getting the plans in place. So this is all just happened over the last several days She will keep me posted about the status of the project going forward If there's anyone else who is interested in participating To do these These weekly meetings. I don't know that you would have to be committed to being the same person every single week Please let myself or rich know and we'll get you connected with the group that's working on the project Yeah, they'd like to Learn more conversational English because most of them just learn book English I'm like imagine you people and over in your countries and also because they're finding More and more of their what we would call 9-1-1 calls are coming from people and because It English is one of the languages that a lot of the callers have been using over there. They they'd like to Be able to pick up more of the language skills. So anyone's interested just as he said, let's air higher No Okay We're looking for approval of the minutes from April of no October fifth. I mean October 8. Oh October 8, excuse me Move by Yolanda is there second Carolyn second or Patrick had his hand up to um, so any discussion All in favor Hi, hi. Okay. Hi Okay, if I Minutes are approved for filing. Okay. Thank you. Okay our first Item of business very exciting As you know usually about this time every year have a dinner for all our Exchange students. Well, that's not here and we have a very limited number But we'd like to honor our two students from one from South Korea one from Germany that are over here And we're excited about it. So at this time If they would like to stand up, we'll start with you know Scott is that microphone turned on we're working on Scott. It's showing right on the screen, but it's not Turning it on. Thank you Okay, you know Would you be willing to introduce your host parents for us? So these are my host parents or its family. I go to a Sheboygan Lutheran high and I'm a senior there It's actually my third year in Sheboygan. I mean, I'm to go to college in the States, but not necessarily Not necessarily decided in Wisconsin. Yeah And our next is Felix and Felix you're from Essington. Oh We have a It's a favorite spot in our hearts here. We're disappointed that we couldn't be visiting this coming May but we're gonna put off our visits on May 22. So hopefully everything would be good with that So if you could introduce your host parents So these are my host parents Lynn and Todd Ryan footer. Yeah, I'm a great time To know Yeah, it's kind of hard right now It's it is difficult. I think in person school is way better than on a school about I Have to do with it. So Yeah Yeah, thank you. We're very happy to have you here in Sheboygan both of you and Once you're once you're here you're your part your Sheboygan night in heart. So Please speak well of Sheboygan when you get home. So congratulations. Thanks showing up. If you need to leave you may okay That was exciting a little little different than we normally do but so our second Item is I think remember last month that we got a donation of coins from Shoreline Metro Evans received and we kind of got it. We need to know what we want to do with them We have them here. There's various there from various countries. So we need to know is it something we want to Cash in and use it use it for donation for somewhere Or do we want to make a display somewhere like at the library or the art center or something to display? This one you know our relationship with coins But these are pretty much any country you can positively imagine. It's big variety Yeah, so I'm I'm open to suggestions what we want to do I had no idea what the monetary value would be of them. We'd have to have that checked out or Some artistic person can put together a nice display So thoughts hand or the microphone should be on it's on I Was that we could but then You know if we I know there's a few banks that do it, but then you know off they I don't know if they just do that for us or without us putting the money in there or not So we'd have to find out Rich we didn't hear what Yolanda said She said the microphone is not on she said should we Find a monetary value first to see what It may be But then I said we'd have to find a place that'd be willing to do at a bank or something without having to deposit it Or exchange it rich Julie Maybe we could use them as a raffle item at our next ethnic infest Pardon, I didn't understand you sorry What Maybe we could use them as a raffle item at our next ethnic infest Okay, there's a that's an idea Mean just thought don't hold it the whole bucket of them Okay, whatever we can decide We can find out though too with what the value is I mean Last time I went I had an account that can open another one and deposit the coins or ask the value Okay, I gave it a relative a relative. I Mean how we're gonna raffle it off and people don't know what it's worth. Oh, yeah, right? Same as us look good luck of the drawing, you know Yeah, you can do it in silence or you can do a basket Okay, okay, but it's good to find out the price. I agree. I mean, yeah, I mean, and that's not we can't First of all what it's all coin correct, right? Yes, and then Each coin we can figure out what the the domination or where it's from And the Euro if it's a Euro or if it's whatever and you know, and that's gonna change with exchangers Well, I think maybe firstly You gave me a good idea. You'll maybe we first need to identify each one of the coins You know from where they're from and make a list of what the denomination in there in the country's money is so can I can I say something sure? I've been to Europe a couple times. I'm always leaving money there coins And the coins aren't worth anything It was worth 50 cents or they're worth a quarter of penny and nickel dime Unless they've got a date on them. That's from 1800. They're not worth anything But what what would be interesting? I have coins in my basement I've got two two coin collections. We spent a small fortune on the cabinet and put them in and After that when I did the third one, I just took a standard frame And I had you know some cardboard or whatever and I just took a hot gun and I glued them Onto the cardboard and then I put them in the frame They look pretty cool on I probably have two dollars tied up in the frame So but these coins some of the coins I have are They're from all over the world actually and I got them from my dad and he's been gone for 40 years So I think what we should do for starters don't do anything with the coins until we can all Give everybody a hug We'll be able to make a better decision And but I think that's when you invest is a great idea But but not as a monetary not saying we think these coins are worth 50 bucks But I mean I'd be more than happy to Somebody wanted to help when it when we get to that point a year or two from now and take a hot gun And the glue some of these coins and put them in a in a 8 by 11 frame Little What's that a little montage? Yeah, you know and like You know like some of these you can tell are from Asia some of them are gonna be from Europe Some might be from South America some might be from Africa to do a couple different frames Let's just sit on these coins for the time being let's just not do anything with them right now. I think I Think that if we glue them if they didn't have any monetary value or collectors value wouldn't that collector's value for somebody If you're gonna use a hot glue gun It's not like you're taking a Small box or something. I've already Yeah, you just take your finger you pull them off the paper And then you take your finger now and you pull the hot glue off of them So you're not gonna devalue any of them if something's got a date from 1950 or 1925 But these are tourists that came from sheboygan and just for the fun of it They've left their their money their coins in our city. So the coins They're not really worth anything and you won't find anybody to give you an appraisal on them because They want to appraise queens that are 75 years old. Yeah, you're gonna be getting face value on those points Yeah, if you're lucky if you and you won't get that because try to when you come back from Europe some time You got euros try to cash those in They don't want to work with They're not you have a pick that accepts heroes, but I like the idea as well as not Like spending about I mean none else they like set a collage or a montage and maybe like the John Kohler Michael arts center I would like to display it. I don't know Yeah, but right right now everything is pretty much dead. I'm just saying for starters Let's just sit on these things for a year.  I already know it so let's sit on this for a year or so and Let's not be in a big hurry to do something with it. It's what I'm saying if that's a case Nobody's gonna see it anyway Can I move that we take Mark's idea and sit on these for a year Who's good at that? Okay, we second it, but who who's gonna store them? Mayor's office I say they've already been here. They've already been in my office for a while. Okay Okay, we'll have a man. Okay, the motion made to keep them on hold and Look at Closer to Essling and fest to look at to do something with them Second today. Well, no, I think do we? We already got that we always got that so I'm just repeating so any further discussion Hearing none all in favor of the motion Signify saying aye. Aye Okay, any opposition same sign, okay motion carried. Okay, thanks That's the next one promoting others should plug in it is more or less informational but I did send Sarah and today she put on the first Facebook cost so it'd be I'd like to see you if you can go to like the mayor's International Committee page and Share it and start getting some Spreading out in a community and also if you know anyone any groups non-profits I'm not looking at businesses, but non-profits or churches or whatever that know they have a relationship with Countries around the world this one is st. Peter Lutheran Church, and they have been for over 20 years Educate helping educate the kids of El Salvador and it's been an exchange program back and forth So it's a long-standing program. So I thought that was a good one to start with As you'll see on there what they do they're trying to work with the kids down there to keep them out of the gangs Because El Salvador has a quite a gang problem. So and they've had students over the years They finally got one in graduate school now that they're helping support So it's a great program, and I'd like to maybe do that I know Rotary and Qantas and a bunch of others have Programs and because I think I'd like to show that we may be mayor's International Committee for Essing in and Vami, but we have relationships with all over the world so and and Mayor Mike I Kind of like you to write up something for on That Great Lakes thing because you have Canadian friends and if you could put something on there about that program Because that's something we do You're welcome so Anyone I Cole was gonna be I said he might be here, but do we have any information on this? Sister so by me. I know we got a letter. I I've sent the email over to the last known contact that I had Okay, was the person that Grazia had been emailing with that that was two years ago, right? That's the only contact person I have via email. So Hopefully I will hear back from that person. Okay, that's that's all I have to go So an email has been sent of welcome and asking how everyone's doing over in Sabami, so that's For us a very giant step Cole Kind of put that together so I appreciate that so any other comments I know last time Alexandra we're gonna work together on and getting some more connections Okay, any other any other questions on that or comments Okay, hearing none. Uh, it's been a tradition except last year to decorate the Christmas tree here at City Hall Sorry, that's some information on that Yeah, typically we would do that at our December 3rd committee meeting But seeing is how many are attending virtually Just wanted to get the sense as to if there was perhaps some other thoughts as to how go about how to go about Doing the tree decoration if assuming we're still wanting to do it That if we had you know if certain people came on certain days or or something I mean any of those types of options that you could say okay Well, this person will come on Tuesday at three o'clock and you just you set a certain time And as we know it doesn't take that long to put up all the ornaments So just wanted to put it out there for discussion as to what the thoughts were Do we have some ornaments left because I know a few for break every year Yeah, whatever was yeah, whatever was taken down has been boxed up and you know, this is this is year two back in City Hall So everything should be We're gonna go in the entrance in the same spot as last year. Okay. Yeah So what's the I mean Sarah's idea what we still want to do the tree and just come in shifts or Or have a few volunteers and Do it what's the what's the feeling in a group Sarah Do you think there might be some individuals at City Hall that would want to do it instead this one here? Like during their lunch hour or something It's it's possible But I wanted to put it to this group first because it's always been a traditional international committee Project so I would say if if no one is interested in Doing that then that's probably the route that we would go But we just need to make what make that decision Hard can you hear me? Yes, Mark. We can hear you You know I One of the reasons we currently don't go to the meetings star and I is we don't have Too much going on at the meetings normally we would go just for the camaraderie of the meeting but for the December meeting or Otherwise I I will volunteer to help on the tree out, you know, I walk into a grocery store I don't like it, but I have a mask on and I would conceivably walk into the December Third Meeting with my mask on and I'm not gonna be giving anybody a hug But I I guess I I conceivably would do this now, obviously if she wagon really takes a crapper as far as COVID goes but you know We've really gone slid downhill in the last few months Okay, but it is Christmas and well somebody got an idea I'm up for it. I agree with you mark. I think that You know, I don't nobody's there like I would come down and I to help decorate the tree. Okay good, and you're And we need you we need you a pack because you're tall Well, I yeah, the tree is two stories tall And I think I might have rolled over to my room last year So you might not want me having that having to decorate the tree. Okay Okay, well, I get it looks like there's several us that will willing to do it. So I guess we'll We'll find a time to do it something out a couple weeks beforehand and Like week or so before and say hey, are we gonna do this if things are a little more under control What's going on? And and I mean it didn't take us very long to decorate the tree Okay, okay, I guess it is what it is. Okay, well, we'll continue with it as planned and we'll find a way Right, we'll find a way to do it. Okay. Thanks Pat and mark appreciate that so Is there any Which we're getting ready to close a meeting, but is there any Thing that you want to put on agenda for next month or if not just if you have something just email Sarah or I or or Mayor Mike and We're looking for items on the on the agenda We're really looking forward to Whenever we can start planning our trip, but we're gonna keep that off of the agenda until we can really get some sense of what's going on here so Any other business Hearing none, I will take a motion to adjourn Yolanda is our second Okay Okay, we got a watch of seconds. Okay all in favor. Hi pose. Okay. Thanks everyone. Take care of yourselves. Happy Thanksgiving


Texas Lill's way. You're sure looking for trouble here for us? Yes, you are, Carl. I didn't have to wait long to meet up with Texas. There's plenty of cash in the pockets of you. Sting the troopers and local peace officers to maintain law. We're the fearless and courageous United States Marshals. Please come back to us now in the thrilling adventures of United States Marshal Lightning Jim Whipple and his deputy Whitey Larson. I mean, another train was held about by Del Plot. Well, they did the catch the Yeager Sudan, didn't they? Our report says it was Texas Lill's gang. Texas Lill's gang? Come on, we're heading for Elk Lodge. Let's cross under! I'd help back the Elk Lodge. I'll look around. Talk to you later. I'm afraid, Robert, you wouldn't be after Texas Lill, huh? Oh, she's the one all right. Oh, give us luck. You're right, and you know the funny thing about it was, I was sitting next to the sheriff at Elk Lodge when that train stopped and in walked Texas Lill. Did the sheriff make a play to get her? No, no, but I guess it didn't have much. She was in and out of that coach before you could win tonight. What she looked like, Doc? Well, she was called, built more like a man. She meant business. Yeah, try to follow her? Yes, yes, he got up a part-time but they couldn't pick up a trail. He was here just a minute ago. They went across the street, the sheriff's office. A few Mexicans around here, they work in the mine. Yeah, I see.  Yeah, I was building up. So I thought I'd come out and start up a practice. Good idea, Doc. Hey, why don't you boys come on down to my house? Well, but this first day, I think it's so dizzying, you know? How about joining us, Doc? Oh, thanks, thanks. I've had my day.  I live right down this road in a white house by the creek there. You can't miss it. All right, Doc, we'll be down. Yeah, we do. I couldn't get a whole car. All right, Wattie. We'll eat and then go over and have a talk with the sheriff. Talking to me on the street was the most important. The train conductor shot at us, and Sam, he was wounded. What? She's a senior. What? Was he hit bad? I put it to the shoulder, senior. He breathed plenty much. And the senior needs to say, I must get the doctor quick. Yeah? Well, where is he? At our hideout place in Secret Valley, senior. I hear there is a new doctor in town. Yeah, yeah, that's right. Where does he stay? He just moved into that white house by the creek. See, I will go get him now. We'll go out the back door, senior. Don't worry about Sam. The doctor will fix him up soon. Come on. My name's Jim Whipple. United States Marshal from Fort Anderson. Right, Jim, eh? Yeah, this is my deputy. Why'd he last? Well, howdy. Oh, pleased to meet you. Well, what's your name, Jim? Thanks. That's all? Yeah, here they all come. Well, we got a report about the train hold up. Oh, yeah? Understand it was Texas Lilligan. Yeah, yeah, I got up a posse and went out right after her. But didn't have much luck picking up a trail, though. Hey, he's funny, smart, and slippery as an eel. Well, that train was carrying mail, Sheriff. That makes it a government crime. Well, maybe you could help us, and we could help you, and let me catch up with it. Yeah, yeah, sure thing. Understand the railroad's offered a $5,000 reward. Yeah? Yeah, I didn't notice any reward signs posted, so I think you hadn't heard about it. Yeah, well, well, I got the sign right here in the desk, but I ain't had time to put it up yet. I see. Any idea where Texas Lill might be hiding out? Hey, now, if I knew that, I'd go and get her. Sure, that's right. Me and Wattie will mosey around town tonight, and tomorrow we'll do a little scouting. Might run into something. Yeah, yeah, sure, sure. And if you see anything, let me know. Sure, yes. Come on, Wattie. You're too glad to see us, Wattie. Yeah, that's right. And he didn't say anything about being under train leader. Now, why do you keep an eye on the sheriff's office? Watch where it goes. I'm going down the road and see the doctor. There's some more questions I want to ask him. I'll let you and the doctor through the water. It's a little scary. I don't know why they did this. Well, it's gone, T. But the doctor right now, what you can't put a blame on me up up in that hidden valley behind is the doctor. You shot both of them. You left them two men up there, taking Wattie and me, come up to that cabin after you left. And the doctor told us who shot him and your brother. Dr. Paul's testimony will put a rope around your neck, Sheriff. Why that yellow double-cropped and pole-cropped? I just hope I live long enough to see that critter. Marshall Lightning, Jim Whipple.


Statistics and Excel coin flip statistics example in Excel part number two. Get ready taking a deep breath holding it in for 10 seconds and looking forward to a smooth soothing Excel. Here we are in Excel if you don't have access to this workbook that's okay because we basically built this from a blank worksheet in a prior presentation so you could start from there with a blank sheet if you so choose and we will be continuing on with the practice problem in a format where you might be able to simply open a blank worksheet starting from here going forward as well. If you do have access to this workbook three tabs down below example practice blank example in essence answer key practice tab having pre-formatted cells so you can go right to the heart of the practice problem the blank tab is where we started with a blank worksheet so we can practice formatting as we work through the practice problem. Let's do a recap of what we've done in prior presentations and then we'll take those concepts and continue on with this presentation so we are imagining a scenario where we're trying to test whether or not a coin is fair in other words if we were to flip the coin the null assumption is that it would come out or have a 50-50 chance of landing heads or tails if we look at this from a sampling kind of perspective we can imagine the entire population then being a theoretical number as though we flipped it infinite amount of times and of course to test it we're going to take a sample flipping it some finite amount of times and see whether or not we have a preponderance of evidence to overturn the null hypothesis which is that we expect it to be a fair coin now in order to do this in excel we practice using some tools to simulate a 50-50 chance and we used the between so we took a random between one and two so that excel will give us a nice random sample we showed how we can then we can then show the results in terms of heads or tails or ones and twos if we so choose and then how we can basically get get these results and see how close they are to what we would expect if it was a fair coin which would be the 50-50 noting it's not going to be exact because we're just simply taking an example of an infinite number of flips and then we saw how we can put together a table and come up with a random function in the tables and use that table to copy and paste uh so that we can run multiple tests so in this case we ran multiple tests with two and then three and uh i'm sorry with two and then three and then four of them and then we looked at our results the percent that's head the percent that's tails on a result to note that obviously if we take larger samples we're usually going to tend more uh closely to what we would expect the population results to be which is going to be the 50-50 although of course uh more uh numbers in the sample does not necessarily we're going to come up to a closer result than some other than a sample that has less results because there's going to be an element of chance that's going to be involved so now we want to take the same concept and just expand the number of flips that we have so let's say let's say that we're going to test this out a hundred times with just let's say 75 flips just to get a nice number and then we'll try to approximate what if the coin is not fair how can we use our between function to simulate something that isn't fair so that we can test a coin it's not fair right so let's do let's do our same normal kind of test with a fair coin so we'll build out uh we'll build out a hundred tests so i'm going to make a skinny ar column i'm over here in ar if you're working in a new sheet you can just build a new sheet and start in column one if you so choose uh or column a and then i'm going to put the number here and i'm going to say we're going to go from one two and let's just do it to 75 i'm just going to not do a hundred so that we have to still calculate the percent of the result so i'm going to select those two and take it down to let's say 75 so we'll flip it 70 times 75 times for each test 75 times i'm going to center that and then i'm going to say this is going to be test one and then test two and then i'm going to copy that out a hundred times so i'm going to copy this out a hundred times i'm putting my cursor on the fill handle dragging to the right notice the testing excel's being nice and gives us that little uh little hint or to show us what how far out we are so there we're at a hundred so there's a hundred tests now i'm going to select all of these headers and make them my header formatting so i'll select this whole thing and i'm going to make it home tab alignment center and headers i usually make black background and white so black white and the headers okay so now if i go all the way back on over so now i'm going to now just implement my random knit my random function equals rand between between one and two one representing heads comma two representing tails or you can do it vice versa whichever way you want to see it but one or two enter and so that so that comes out to one and some which is the heads right and i'm going to take that i'm going to copy it all the way down to 75 and then i'm also it might be easier to copy it and paste it instead of using the fill handle to drag it to the right so that i can see the headers so i'm going to copy this whole thing right click and copy and when i paste it it'll paste the cells so i'm going to then select myself from a u all the way to the 100 tests and then i'll put my cursor here and right click on the selected area and paste them not one two three normal pasting and there there we have it now we have a hundred tests that have been populated now i might want to put a table into this the table might make it easier to kind of randomly shuffle these if i click on anything notice they kind of randomly shuffle so if i but if i insert a table insert tab table insert and okay so now we've got our our table and if you sort the table up top and each row that kind of gives it a good shuffle and then and then it it reshuffles all the all the time right so now what we want to do i want to keep my shuffling here i want to keep this thing up so i can go back in and shuffle the 100 uh tests see every time i click something the whole table seems to shuffle so i'm going to hope that that is the case so i get a nice random shuffle every time and then i'm going to copy the whole table i'm going to take the whole table or maybe i could just copy the headers let's do it this way i'm going to copy from as as all the whole all the way down to excel the whole column out to uh test 100 at e o and ctrl c or right click and copy and then i'm going to paste it it to the right but i'm going to paste it one two three so i'm going to paste it in let's paste it over here in er and right click and i'm going to paste it but make sure i paste it one two three just the values only one two three values only so now it's not going to shuffle and i've got a hundred random tests hopefully they're all random right so then i could go down and i can i can do my averages on the 100 tests let's go ahead and format it though let's select the ones up top and do my formatting making this my header i'm going to go to the home tab uh black white and then center and then i'll select all of the data and we'll take this all the way to the right and all the way down through the data and i'll make it that blue that i like to use home tab font group and i'm going to hit the bucket drop down if you don't have that


because the more exposure you get of not just your training, but of your business, right? The more out of obscurity you are going to get, right? So obscurity is pretty much something that kills a lot of businesses, because if no one knows you, no one's gonna do business with you. And if no one does business with you, you're not gonna create or generate any new revenue into your business, right? So parents have to know you, kids have to talk about you, coaches in your local area have to want to get in contact with you because they see you as a specialist, as an expert at what you do.


Live from Boston, Massachusetts, it's theCUBE. Covering AWS Reinforce 2019. Brought to you by Amazon Web Services and its ecosystem partners. Well, welcome back everyone. We're here at CUBE's live coverage here in Boston, Massachusetts for AWS Reinforce. First inaugural conference run security. I'm John Furrier, Dave Vellante. Next guest is Dan Hubbard, CEO of Lacework. I've started out of Mountain View, California. Great to have you on. Thanks for joining us. Thanks, thanks for having me. So, you know, Reinvent was developers. Reinforce is kind of like CISO's coding security. Cloud and intersecting with security. This is a new kind of show. What's your take on it? Super impressed so far. I mean, there's what, 8,000 people here. You know, we have literally hundreds of demos lined up at the booth. So really impressed so far, first impressions. It's a good move for Amazon to do a security conference. Don't you think? I mean, really smart. Yeah, really smart. It's a lot more about defending than, you know, a lot of the security conference about offense and vulnerabilities and how to find kind of holes and weak cracks. This is really about, how do we defend, you know, our security in the cloud? Talk about your company, your mission.  You're going after a hot space. The CISO's, or CIO, is the one you talk to. They want a new breed of supplier service provider. Certainly cloud, APIs are going to be critical in all this. So, you start to see really smart platform thinking, systems thinking around, companies around, the security challenge and opportunity. What do you guys do? Explain what you guys do. We really believe, you know, this new wave of cloud, IS and PASS, really needs a new architecture. It's a whole new architecture from an IT perspective, so we need a new architecture from a security perspective. And the great thing about the operating model is you can do a wide set of things and then go deep in the areas that are really important. So what LACE Work does is we allow you to secure IS and PASS services with compliance, configuration, host and container security. And there's one platform that kind of wraps across all of those different areas. And that's targeting for developers, right? So they don't have to think about security all the time? Is that like one of the core things? Yeah, so definitely, so in almost every case, security is unlocking the budget. However, DevOps is involved. And DevOps is involved from an influence. But, you know, it used to be that, you know, developers would ask security for permission. Now security is going back to developers and asking for permission to secure the infrastructure. Yeah, and you said that the architecture has got to be different because the IT is changing. So cloud security needs a new architecture. What are the fundamentals of that architecture and how is it different from security on-prem? So I think it has to be SAS. So it's got to be delivered multi-cloud from the cloud. You know, if you're going to secure the cloud, it really should be from the cloud. There's business models that should be different.  There's not perpetual models.  You're always keeping your customers happy and you're always innovating. The pace of innovation has to be really quick because the pace of the cloud is moving at such a dramatic speed. So those are kind of business-oriented, you know, that's kind of a different definition of architecture than I thought. Technically, is it a fundamental do-over or is it fundamentally similar? Well, you know, there's some of the tenants which are the same. You know, we need to get visibility. That's very similar. You know, we need to have controls. We need to have auditing. We need to find threats. However, the way you do it is very different. So you don't own the hardware. You don't own the racks. You don't own the network. You got to get used to that. You got to live above the responsibility line. So you have to fit within their infrastructure. So what that means is you need to be very API-friendly because we're sucking a lot of data. You know, on Amazon, we're pulling in configuration and cloud trail data.  So we support things like Kubernetes, things like Docker, or we also interoperate with things like Bare Metal and, you know, in the AMIs themselves. What problem do you guys solve? You know, every startup has that cultural vector in. They kind of sometimes you weave into a market and then also you get visibility into a key value property. What's the key problem that you solve and what's the benefit? So the key value we solve is if you are in the cloud or migrating to the cloud, we give you compliance, configuration, and threat protection across all your clouds. So irrespective of which cloud you live in or operate in, we give you one central threat detection engine and which gives you visibility but also gives you compliance and controls into that. So Amazon has this, you know, shared responsibility model. They're protecting the compute, the storage, the database and customers are responsible for the endpoints, the operating system, the data, et cetera, et cetera, et cetera. And Amazon certainly has tools to help them.  Oh yeah. To your point. Absolutely. But can you help us sort of squint through that maze? Sure, yeah. I mean, the easiest way that I can explain it is, if you can configure it, you have to secure it. Everything below is the provider's responsibility. That said, there are different areas where things are kind of peeking through the responsibility lines. So what I see is a world where there's not 50 security vendors that you've bought, like in-premise or traditional data center, but you're interoperating with a provider. So, you know, the big three providers, open source, and then a solution like ours. So it's more about how do we interoperate there together.  So technically it's a little bit different. So the threat of containers is an interesting topic, all right, you're spinning them up and you're spinning them. It makes VMs look like, you know, child's play. Yeah.  Yeah. You know, like the shell game. What we do is we get baked right into your infrastructure. So every single time you deploy and run through CICD, a new container or a new app, we're baked in there. And what we're doing is we're looking at all your applications, processes and network traffic, and then we look for the known bad and the unknown bad based off of that behavior. So it's native security in the container at the point of creation, not an afterthought. Correct. What's your take on Kubernetes landscape? Obviously, pretty much everyone's kind of consolidated around that from a de facto standard. That's good news. Where does it go next? Cause there's all kinds of stateless stateful applications. That becomes like the service mesh conversation. You got all kinds of services that could, you got Lambda out there, automating all these things.  It's incredible. I think Kubernetes is the fastest growing enterprise open source project ever. Where every customer we talk to is either in the midst of migrating, migrating or just thinking about it. That said, the world is looking to go multi-cloud, but most customers today have a combination of in-premise, bare metal, AMIs, Kubernetes containers. What we're doing is we give you visibility into your Kubernetes infrastructure. So we talk pods, nodes, clusters, namespaces, and we allow you to secure the management plane and the communication between those. So it's really critical when you're deploying those from a security perspective that you know what's happening. The ephemeral nature of it is very different from regular security too. You need to answer questions like what happened for 10 minutes during this timeframe six months ago? And that's really hard with traditional tools. Yeah, it's really hard. And that's really where the automation plays in. Talk about the journey of where your customers are going at because we're seeing a progression kind of categorically, you know, three kind of levels. I really wanted to enter the cloud. I really want to take advantage of that cloud and very aspirational, maybe not realistic, but it's on their plans.  So you've got the leaders, people who are kind of in the middle and then people jumping in. Where do you guys see your benefit? What are some of the challenges? How do you guys get into those areas? I think it's a super dynamic marketplace because what's happening is every big company that may not be fully cloud-native is buying companies that are cloud-native. So then they become the sexy new way to deploy and then they start figuring out how to deploy there. So one of the trends we're seeing is core centralized security is becoming governance and tooling and then they're distributing the security function within the app teams themselves and that model seems to work really well because you've got security practitioners baked within the DevOps team, but then you've got a governing role with tooling and centralized tooling from there. That said, depending on the customer or the prospect, it's all over the place. Many systems are scratching their heads saying, oh, I don't know what's going over the cloud guys, they've got a different group that's running it, they're trying to figure out, how do I just get visibility? I know my name's, I'm the one they're going to come after if there's a problem. So it's really all over the place right now. But you're a service, so you're baking it in, we're natively into the containers. Yep, it doesn't matter. The container aware, if you will. It doesn't matter if you're in-premise or not, containers or not, we work across all of those. So was that the hook for your sort of original idea, your business plan, your investors, you've raised I think 32 million, you got 70 employees. What was that hook? What attracted the investment community? So I think the original idea was, if you're deployed in the cloud and you have a breach, how do you know you had a breach? You know, things that happen come and go very quickly. All the data is encrypted on the network. I don't have full visibility on the network itself. So that was the original idea. How would I go back in time, kind of a time machine to find out what happened? Then we originally supported AWS and it was really about visibility within the AWS infrastructure. Then Kubernetes happened. Now the big hook really is, am I using containers? Am I using Kubernetes? And then how do I make sure I'm compliant and then I'm following best practices? And then that breach scenario still definitely happens. Everybody tries the service before they buy it and they're almost always finding out problems along the way. What did Kubernetes do for you guys that made a kind of such a step function change for what you guys were doing? Was it because they had the dynamic nature of dealing with the services, was it the orchestration? What specifically was the benefit? I think the orchestration, the single management plane from a security perspective is one of the big things. If you get access to that one brain, if you will, you have access to everything. Obviously the ephemeral workload is big. Yet it was an enforcement. Kubernetes with service mesh and things like pod security policies allows us to hook APIs in a way that you can actually write enforcement versus a firewall or some of these old school ways of killing packets. Yes, you got a cloud native approach. Kubernetes comes along. It's aligns with your philosophy and architectural approach. And we run Kubernetes ourselves. So our entire infrastructure is based off of Kubernetes. So we were a Kubernetes user very early on. So we just take the things that we learned to our customers. So here's a quote from a CISO. I won't say his or her name, but I want to get your reaction to it. When talking about dealing with suppliers, looking for the new generation of suppliers, like what you guys are doing, I would put you in the new classification of emerging suppliers. This is the message to all the suppliers in the room. I happen to be in there. Have an API and don't have it suck. Because UI is shifting to API, UI focus is shifting to API focus. So we are evaluating every supplier on their APIs. Your reaction to that? I absolutely agree. So there's two levels of APIs. One is you have to interoperate with the APIs from the providers in order to get the data properly, right? That's a big, big component. The other is you have to have APIs for your consumers. And you can't automate without APIs. So that's really critical. That said, I will disagree a little bit on the UX and UI aspects. If you are triaging data, it's really important that you have the right data at the right time, and visualizing that data in a way is pretty important. How real is multi-cloud in your opinion? I mean, everybody's talking about multi-cloud. A lot of times we've said multi-cloud is kind of a symptom of multi-vendor, but increasingly it could be a strategy. In terms of you're thinking about your total available market, your market opportunity, how real is it when you're conversations with customers? It's very real. We were really surprised. We first started supporting AWS, and then we added GCP and Azure together. Now we have a core principle that everything we build has to be parity across all the clouds. And we had a huge uptick across GCP and Azure very early. So we were really surprised. What we were surprised about was it's not portable workloads. So it's not about taking one application distributing across multi-cloud. That's kind of fiction. That doesn't happen very often. It's either you bought a company that's in another cloud or use a past service in another cloud, or you have just two totally disparate applications in a large company that just happen to be in different clouds and the data's in different places. They don't need to inter-operate. So it's just a little different, but we're seeing- Kind of horses for courses as well, right? Some clouds may be better for data-oriented. You're point early and we've heard this in some of the CISO conversations. M&A becomes a big factor because they get new teams and new culture and they might have different cloud approaches. But I totally agree with you on that. I would say I would even go more further and it's absolutely fiction between multi-cloud because it's just got latencies on the connections, whether they're direct connections or not. They've all gone the factors. So I've always said, and I kind of believe and I'd love to get your thoughts on it, is the workload should dictate to the infrastructure which cloud it should use and go with one cloud for that if it makes sense. And then use multi-cloud across the workloads and the workload can handle a better cloud that the cloud selection be driven by the workload. It's certainly from an application perspective. You want to silo it, you know, probably there. I think what's interesting about, you know, a lot of the work each provider is doing in security, a lot of people ask, well, you know, why don't I just use all my provider security tools? And the answer is, they've got some great tools. You should use those for sure. But there is a bunch of technology above that that you can use. And then you've got to span across multiple clouds. What you don't want is three different APIs for security across every single cloud. That's going to be a major pain. You have to stitch those things together. And that's where you guys come in. Yeah, absolutely. What's your take on this show reinforced against inaugural show? Love to go to the inaugural shows. If they don't have a second one, we can say we were there. Yeah. Reinvent, you made a comment before we came on. Reinvent started out, we were there early on as well. It was developers. Yeah. It wasn't a lot of fanfare. In fact, you could wander around Andy Jass. It wasn't crowded at all. It was great, great time. That was younger now. Amazon's gotten much stronger, bigger. What's the vibe here? Is it developers for security? Is it CISOs? Is it, because what's your read on the makeup and the focus of the attendees? So I think it's a little bit of a mix of both, which I think is good. I've met a number of developers or what I would call kind of new breed security engineers. These are engineers that are more interested in how does the cloud work and interoperate and how do you secure that versus reverse engineering malware with assembler, which a lot of the other places are really about the threats and what are the threats and how specific are those? This is really a little bit more about how do we up our game from a security perspective in this new world order, which is really good. Which is cloud very agile, very fast, horizontally scalable, alas, all the goodness of cloud. All right, final question, developers, bottom line is developers continue to code and do the things whether it's a DevOps culture of having a hackathon and testing new things out, which is how things roll now. Getting into productions hard, what's the developer's impact to security? Is the trend coming out of the show that security's baked in enough to think about it? It's kind of like how configuration management took that track and DevOps took that away. You mentioned that earlier, you can configure it, you can secure it. So similar track for security, going the way of automation, what's your role? So automation is going to be critical for sure and then it's going to be a combination of security and DevOps together. Call it DevSecOps, call it security engineer, whatever you want to call it, but it's definitely going to be a combination of both. Security people aren't going away, that's for sure. We're still going to need security experts and focus is just a critical aspect about this. Dan, thanks for the insight coming on here, Reinforced. Take a quick second, give a plug for your company. What are you guys looking to do? You're hiring, what's going on in the company? Yeah, sure, Lacework, we're going to help you protect all your workloads, your configuration and compliance in the cloud, regardless of which cloud. We are hiring, websiteslacework.com and we'd love to talk to you. What's the culture there? Culture's great, very fast moving, very fast paced, very modern, we live and breathe by the success of our customers. It's a subscription business, so we have to continue innovating and renewing our customers. Got to be smart, probably, to deal with Kubernetes and containers, thanks for coming on. It's theCUBE coverage here, live in Boston. I'm John Furrier, Dave Vellante. Stay tuned for more live coverage after this short break.