Filename: Private: No Yes Filetype: Auto ABAP Sophia Apex Azure CLI Batch Bicep C Cameligo Clojure CoffeeScript C++ C# CSP CSS Cypher Dart Dockerfile ECL Elixir Flow9 FreeMarker2 FreeMarker2 (Angle/Bracket) FreeMarker2 (Angle/Dollar) FreeMarker2 (Auto/Bracket) FreeMarker2 (Auto/Dollar) FreeMarker2 (Bracket/Bracket) FreeMarker2 (Bracket/Dollar) F# Go GraphQL Handlebars Terraform HTML Ini Java JavaScript Julia Kotlin Less Lexon Liquid Lua Modula-3 Markdown MDX MIPS DAX MySQL Objective-C Pascal Pascaligo Perl PostgreSQL PHP Plain text ATS PQ PowerShell Protobuf Pug Python Q# R Razor Redis Redshift ReStructuredText Ruby Rust Small Basic Scala Scheme Sass Shell Solidity SPARQL SQL StructuredText Swift SV Tcl Twig TypeScript TypeSpec Visual Basic V WebGPU Shading Language XML YAML Indentation: Spaces Tabs 1 2 3 4 5 6 7 8 Clone KitchenSyncDB and the two ladies that adore me So this talk is about two very common systems that you can find in any home, but that are generally not very wеll understood by men in IT. This talk is 100% not politically correct, although I believe that it will not offend any women in the room. So... let's start with KitchenSyncDB * What is this new kind of DB, that everyone has? * And what makes it so special? What is it? * Its a DB * Its a log oriented DB * It keeps your dirty log entries * It keeps small and large log entries * It has quantum mechanics properties * while you are looking at it, the DB logs look relatively small * when you query the logs you suddenly see endless log entries. Men in the audience will be questioning, where all these log entries came from? Was there a bug with the daily routine that caused this? * The IT man will dive into debugging why the second quantum property of the KitchenSyncDB appears and instead of cleaning up the logs, will opt-in for takeаway or a night out with the boys. What makes it so special? * Literally every place that supports humans have a single or multiple installations of this DB. * Some men even use it for purposes, that it was not designed for. * If the DB fills its log to the max and it is not cleared, it starts to smell. * If the log is unattended for considerable time, the data starts to mutate, expand and smell even more. Types of installations So I tried to group the types of installations into 3 groups: 1. Single person installation 2. Couple setup 3. Family or large family installation A.K.A high productivity setup We will not be covering large enterprise deployments in this talk. Let's look at the characteristics of Single person setups * The DB is not queried very often * Its taken care as a hobby project * Its often that you forget about it for days or even weeks * The log is not filling very fast * The log has fairly similar items in it * Its common that you cleanup the log entries, only when you can smell them * Even thou its not hard to cleanup the log, it is still annoying to do so, so men prefer to go sit on the couch and expect that the DB will magically cleanup the log Paste
