text stringlengths 0 2.35k |
|---|
[1143.38 --> 1151.40] so that you can still prove that the new changes added to the database are consistent with the whole history since the beginning. |
[1151.92 --> 1160.86] Regarding use case, a few months ago, there was a situation with a famous tennis player and the COVID-19 results. |
[1161.40 --> 1168.38] And there was some news regarding multiple results depending on when it was acquired from the service. |
[1168.38 --> 1173.42] Of course, if that data is stored in multiple databases or in blockchain, |
[1173.60 --> 1179.24] then it will be possible to actually know if that data was consistent or was tampered with. |
[1179.86 --> 1184.70] That is kind of use case in a more traditional system or service, |
[1185.30 --> 1191.52] that it may take time to use a traditional immutable database in this type of system or service, |
[1191.86 --> 1194.78] but I'm sure it will happen with time. |
[1194.78 --> 1199.80] So it's not about just sensitive information like it. |
[1224.78 --> 1230.86] What would normally be manual error prone tasks across the entire spectrum of responding to an incident? |
[1231.20 --> 1234.70] This can all be automated in every way with FireHydrant. |
[1235.08 --> 1240.88] FireHydrant gives you incident tooling to manage incidents of any type with any severity with consistency. |
[1241.44 --> 1244.56] You can declare and mitigate incidents all inside Slack. |
[1244.94 --> 1247.94] Service catalogs allow service owners to improve operational maturity |
[1247.94 --> 1250.92] and document all your deploys in your service catalog. |
[1250.92 --> 1256.54] Incident Analytics like to extract meaningful insights about your reliability over any facet of your incident |
[1256.54 --> 1258.28] or the people who respond to them. |
[1258.78 --> 1260.68] And at the heart of it all, Incident Run Books, |
[1260.76 --> 1264.88] they let you create custom automation rules to convert manual tasks into automated, |
[1265.24 --> 1268.26] reliable, repeatable sequences that run when you want. |
[1268.62 --> 1273.42] Create Slack channels, Jira tickets, Zoom bridges instantly after declaring an incident. |
[1273.84 --> 1276.50] Now your processes can be consistent and automatic. |
[1276.98 --> 1278.66] Try FireHydrant free for 14 days. |
[1278.66 --> 1280.24] Get access to every feature. |
[1280.38 --> 1281.38] No credit card required. |
[1281.70 --> 1283.66] Get started at FireHydrant.io. |
[1283.96 --> 1285.72] Again, FireHydrant.io. |
[1285.72 --> 1285.84] FireHydrant.io. |
[1305.60 --> 1310.00] So it sounds like of the use cases, you know, some obvious ones are, you know, |
[1310.02 --> 1315.42] obviously financial transactions, you know, health records and things that basically you care about |
[1315.42 --> 1317.00] that basically change over time. |
[1317.08 --> 1321.72] You want to be able to go back at some point and say, hey, what was the state of things on this day, right? |
[1322.10 --> 1328.84] And have a high degree of confidence that this data hasn't been altered, hasn't been modified or anything like that. |
[1329.06 --> 1331.38] That's the key takeaway here from what I'm gathering. |
[1331.98 --> 1338.86] So I'm curious, what drives folks like you into this particular domain problem? |
[1339.10 --> 1340.38] Why immutable databases? |
[1340.38 --> 1342.86] All the things you could be working on. |
[1343.86 --> 1344.04] Yeah. |
[1344.04 --> 1348.04] I think we both say that we like playing with cryptography and math. |
[1348.30 --> 1354.48] For me personally, when I start learning about IMU-DB and what techniques it uses, |
[1355.14 --> 1359.02] the cryptography itself and mathematics can be very theoretical. |
[1359.02 --> 1367.54] And as long as it doesn't find the practical place to give you some benefits, it's still a theory, right? |
[1367.78 --> 1372.82] And when I've learned about IMU-DB, because I joined the team a few months ago, |
[1373.32 --> 1379.56] that was this moment that you find something that is working, live database, that you can easily use it. |
[1379.56 --> 1388.88] And it has all this machinery behind it that is doing all these proofs and is cryptographically verifying everything and keeps everything in place. |
[1389.70 --> 1395.02] So that's something for me that is a great benefit for basically all of us, right? |
[1395.10 --> 1397.92] So previously we could think of this. |
[1398.34 --> 1406.12] Maybe there is a project that I want to create and it would use this technology, but then I find it hard to implement this. |
[1406.12 --> 1412.92] And suddenly I find this kind of database where I have very easy interface and I can just take it and use it. |
[1413.66 --> 1418.26] So for me, that's the major goal of a project like IMU-DB. |
[1418.82 --> 1427.80] So we have a lot of knowledge and actually majority of the cryptography and all these algorithms were invented a long time ago. |
[1428.30 --> 1431.94] And right now we only started implementing them and implementing them practically. |
[1431.94 --> 1440.94] And that's where I think IMU-DB is, that's where the goal of the project is, give people the way to use immutable database in a simple way. |
[1441.64 --> 1446.92] Yes, before giving the explanation how I end up here. |
[1447.54 --> 1455.20] But actually using IMU-DB for application developer is exactly the same as using a traditional database. |
[1455.20 --> 1466.12] You can download the IMU-DB binary or docking container and you will use like any other key value store or SQL database as well. |
[1466.74 --> 1471.52] So before I joined Cognotory, I was working as a software engineer for IBM. |
[1472.34 --> 1477.34] And the last project were related to digital right management. |
[1477.84 --> 1483.00] And that was related to applied cryptography there for generating the crypto materials. |
[1483.00 --> 1488.80] And also I was a contributor for hyperlateral fabric by then. |
[1489.28 --> 1495.00] Also, I worked in an experimental project where we added SQL to hyperlateral fabric. |
[1495.54 --> 1501.40] And we added SQL support into the chain codes, like actually in the smart contracts. |
[1502.06 --> 1509.04] But by then I was convinced that the complexity of the project was quite big. |
[1509.04 --> 1521.06] There were many companies or organizations willing to use blockchain just to be sure or to prove themselves or to their clients that the data was not changed. |
[1521.62 --> 1524.94] But then they had to run a very, very complex system. |
[1524.94 --> 1532.88] So I always thought about the possibility to have just a traditional database with the verification possibilities. |
[1533.28 --> 1543.74] So to have the same verification capabilities like a blockchain provide, but thinking of single organizations being the owners of the data. |
[1543.74 --> 1552.40] But yet to fulfill with the auditory requirements or to prove to their clients that the data has not been changed. |
[1553.20 --> 1557.22] So by then I started to think about this type of systems. |
[1557.56 --> 1562.22] And I got to know about the company and the initial release of Inmudev. |
[1562.22 --> 1572.10] By then Inmudev was implemented using Relay in another Go, another key value store that was written in Go. |
[1572.68 --> 1575.56] So that's where I started to work. |
[1576.28 --> 1583.84] And related to verific immutability, I think tampering detection is one of the type of verification we can do. |
[1583.84 --> 1590.12] But there are many other things that we are there to be explored or to be included. |
[1590.44 --> 1593.62] Like what is the latest record that was modified? |
[1594.10 --> 1600.62] How to be able to verify when you are dealing with higher level data models like SQL. |
[1601.20 --> 1608.14] If you have a database and you have a document like data model and you have queries and you have to verify that. |
[1608.14 --> 1614.44] So there is a lot of things to get to investigate, to explore and of course to implement. |
[1615.10 --> 1617.68] So it's not law something you mentioned blockchain. |
[1617.82 --> 1618.56] We'll come back to that. |
[1618.70 --> 1619.46] We'll come back to that. |
[1619.92 --> 1623.14] You piqued my curiosity when you said that you support both SQL. |
[1623.70 --> 1629.96] You can use it both as a traditional sort of RDBMS, SQL database, or as a key value store. |
[1630.18 --> 1632.78] Why the dual modality for accessing data? |
[1633.12 --> 1636.08] Actually, everything started as a log. |
[1636.08 --> 1642.46] So InModb has a composite construction. |
[1642.94 --> 1645.36] Everything started as an embedded database. |
[1645.74 --> 1648.16] So InModb can be used as an embedded database. |
[1648.80 --> 1650.52] That is a set of logs. |
[1651.08 --> 1653.16] Append-only log that is verifiable. |
[1653.28 --> 1655.46] It's like a transparency log. |
[1655.98 --> 1664.22] So you can access one of the differences of traditional key value store is that you can access a given transaction by its ID. |
[1664.44 --> 1665.66] Its unique ID. |
[1666.08 --> 1676.54] If you only need to store records, logs, events, and then to query them, you don't need to query the data using an index. |
[1676.54 --> 1680.44] Just directly using the entry of the log. |
[1680.84 --> 1684.08] That is the initial, the basic way of using it. |
[1684.66 --> 1688.62] Then we have the possibility to build an index based on the key. |
[1688.62 --> 1694.84] So because every transaction or log entry consists of a list of key value entries. |
[1695.08 --> 1702.50] So then you can easily get what are the transactions that modify this particular entry. |
[1702.50 --> 1705.80] And you will, of course, you will get the latest one. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.