mfreed

18 ms·

1. 121.▲
   by mfreed 6y ago

   Yep, we like to eat our dog food =) Timescale Forge, which I mentioned elsewhere, is based all around Kubernetes (including StatefulSets), which enables its decoupled compute/storage and instant pause/resume. For that we employ he
2. 122.▲
   by mfreed 6y ago

   The main difference on Timescale Cloud between dev (starting $115) and production is just the resource availability and slightly longer PITR recovery period for non-dev options. Both offer same full TimescaleDB experience, console, ability
3. 123.▲
   by mfreed 6y ago

   In the Timescale Cloud portal, once you create a database, it's one-click "upgrade" to move between any of these configurations, and it happens with ~zero downtime. That's also true for multi-cloud migration, you just se
4. 124.▲
   by mfreed 6y ago

   (Timescale person) This is also true for Timescale Cloud -- especially once people are using it for TimescaleDB (which, as you probably know, is implemented as a low-level extension to Postgres), we see some users start to migrate over the
5. 125.▲
   by mfreed 6y ago

   Hi, TimescaleDB cofounder here. Nice to read about your journey in time-series data, and always welcome another database that can satisfy a specific type of developer needs. I also commend you on your desire to rebuild everything Postgres
6. 126.▲
   by mfreed 6y ago

   Hey, thanks for the continued discussion: > If there is some kind of emergency and I need to have > the database on the cloud, this is a serious restriction. > It limits my choices and constrains my actions. > if the
7. 127.▲
   by mfreed 6y ago

   Hey 120bits - thanks for the nice words! What new/other features would you like to see? (Also feel free to join slack.timescale.com or reach out at mike (at) timescale.com)
8. 128.▲
   by mfreed 6y ago

   Hi - I just want to clarify some mistake / misrepresentation about our Timescale License (TSL): 1. The TSL is not a new license, have had it in place since late 2018. What we recently announced is that multi-node TimescaleDB will be a
9. 129.▲
   by mfreed 6y ago

   Fun fact: TimescaleDB exists because we were using InfluxDB + Postgres for a previous IoT project and also found it unworkable (developer experience, query language, reliability, scalability and performance, operations, etc). We first built
10. 130.▲
    by mfreed 6y ago

    Thanks. I love developer comments -- we've all written things like "this is hacky and ugly" in our code :) # Note: influxdb-python first replaces each backslash in the username with two backslashes # and because in inf
11. 131.▲
    by mfreed 6y ago

    Do you have a URL? Thanks!
12. 132.▲
    by mfreed 6y ago

    Because TimescaleDB is a relational database for general-purpose time-series data, it can be used in a wide variety of settings. That configuration you cite isn’t for the core TimescaleDB time-series database or internals, but to add a spec
13. 133.▲
    by mfreed 6y ago

    I appreciate the discussion here, and as mentioned elsewhere, this has been good motivation for us to revisit this clause in the Timescale License, as a bit has changed since we released it in 2018. That said, I think a lot of this discussi
14. 134.▲
    by mfreed 6y ago

    You are thinking of the AGPLv3. Not to be confused with the GPLv3 =) https://www.gnu.org/licenses/agpl-3.0.en.html "It has one added requirement: if you run a modified program on a server and let other users comm
15. 135.▲
    by mfreed 6y ago

    Thanks! You might also find this related feature, real-time aggregation, really powerful as well. We just released it last month: https://blog.timescale.com/blog/achieving-the-best-of-both-w... "With real-time a
16. 136.▲
    by mfreed 6y ago

    Just to clarify, the Timescale License was originally announced in December 2018. At that time, we didn't "relicense" any existing Apache-2 code, we just said some future features will be licensed under the TSL rather than
17. 137.▲
    by mfreed 6y ago

    Short answer is: The 2.0 release won't natively support automated failover, although you can build around using PG tools like physical replication + Patroni. But these capabilities are certainly things we are working on. Per the PR not
18. 138.▲
    by mfreed 6y ago

    Those 2018 benchmarks pre-dated many of the features we released last year, including columnar compression, continuous/real-time aggregates, etc.
19. 139.▲
    by mfreed 6y ago

    Yep, that's exactly what the "Timescale Observability" stack is about. Type "helm install", and a full stack is spun-up and auto-configures to scrape information. You have graphs up in Grafana within 2 minutes, ze
20. 140.▲
    by mfreed 6y ago

    Absolutely! We wrote one of the first remote backends to Prometheus that supports both the remote_read/remote_write interface: https://prometheus.io/docs/operating/integrations/#remote-en... Given how m
21. 141.▲
    by mfreed 6y ago

    Hi JeremyNT: We've never "changed" any Apache-2 licensed code to TSL-licensed code. And in fact, we've recently basically eliminated most of our enterprise features (read: paid only) and converted them to community fea
22. 142.▲
    by mfreed 6y ago

    A slightly different perspective of our licensing/copyright approach is there isn't confusion about ownership, so if we were ever to decide on a more permissive license, we have the clean ability to do so. Zero plans, but this als
23. 143.▲
    by mfreed 6y ago

    Not yet, I should have been clearer: compress_chunk operates on a single chunk, the way to define "compress all chunks older than 1 week is": SELECT compress_chunk(i) from show_chunks('conditions', older_than =>
24. 144.▲
    by mfreed 6y ago

    We did consider the Commons Clause when investigating our own licensing approach, but ended up concluding that its definition of "Sell" were actually much vaguer than we felt comfortable with: “Sell” ...a product or service
25. 145.▲
    by mfreed 6y ago

    Absolutely possibly to upstream changes. People have, and we welcome contributions: https://github.com/timescale/timescaledb/blob/master/CONTRIB...
26. 146.▲
    by mfreed 6y ago

    Hi @heipei -- one thing to observe is that Graphite & rrdtool are designed for a specific monitoring use case, while TimescaleDB is a more general-purpose time-series database. So what that means is that TimescaleDB has mechanisms to ma
27. 147.▲
    by mfreed 6y ago

    In most cases, yes, the license will permit this. (There is discussion elsewhere in this threads about whether you give DDL access to your users, i.e., they themselves define schemas, tables, indexes, etc. Otherwise, Datadog is primarily a
28. 148.▲
    by mfreed 6y ago

    > FWIW, Heap would automatically create new tables for customers as they sign up and would also automatically create new indexes for customers as needed. For that reason alone, I'm pretty sure Heap would violate the Timescale licens
29. 149.▲
    by mfreed 6y ago

    Just for clarification: This limitation only applies to code under the Timescale License, while most of our code is licensed under the Apache 2.
30. 150.▲
    by mfreed 6y ago

    In the current version, you can execute `compress_chunks` on each of the data nodes and enjoy those same savings (and will work transparently with queries, as before). In subsequent releases, we'll add full support of compression, e.g.