mfreed

12 ms·

1. 61.▲
   by mfreed 5y ago

   To follow up Ajay's point, we really do take compatibility and stability seriously. I believe that our "major version" upgrade from 1.x to 2.0 was the first time we changed/broke any APIs, but that involved a long beta&#
2. 62.▲
   by mfreed 5y ago

   We totally hear you that usability and the developer experience is super important, especially when starting out. One project we launched earlier this year "Timescale Analytics" actually seeks to address exactly this, e.g., bring
3. 63.▲
   by mfreed 5y ago

   Hi @spmurrayzzz thanks for the feedback. (Timescale person) Always strive to do the best and fairest benchmarks we can, and for that reason, all our benchmarks are fully open-source for both repeatability and improvements/contribution
4. 64.▲
   by mfreed 5y ago

   We actually see a bunch of startups directly going after that market leader in historian space that are building on _top_ of TimescaleDB. So they can bring their domain expertise in process manufacturing and elsewhere, and then build on a m
5. 65.▲
   by mfreed 5y ago

   Thanks, super appreciated! I remember always enjoying our conversations as well!
6. 66.▲
   by mfreed 5y ago

   Hi PeterisP, just to avoid any confusion: The sentence you quote is actually meant to -technically- establish a basis for what it means for somebody to run/offer TimescaleDB as part of a value added service (very much allowed) versus a
7. 67.▲
   by mfreed 6y ago

   Timescale We develop TimescaleDB, the open-source relational database for time-series data, and the Timescale cloud platform. Build on PostgreSQL, TimescaleDB offers developers the reliability, performance, scale, and advanced analytical
8. 68.▲
   by mfreed 6y ago

   Thanks for the clarification, Luke. For a bit more background for the HN community: When we initially launched the Timescale License in Dec 2018, we didn't relicense any of our Apache-2 code -- that was and has always remained licensed
9. 69.▲
   by mfreed 6y ago

   Hey pezezin - would love to hear more if you are open to it. Can you ping me at mike @ timescale.com?
10. 70.▲
    by mfreed 6y ago

    It's raided network-attached block storage. We'll update the blog post to make that clear.
11. 71.▲
    by mfreed 6y ago

    We report numbers in the blog post with our managed offering Timescale Forge, running on AWS with storage replicated across AZs and supporting automated failover. Not sure about "comparably provisioned re: IOPS" given that you don
12. 72.▲
    by mfreed 6y ago

    On our managed Timescale Forge, it's multiple AZ. (On some benchmarking equipment on Digital Ocean, it's advertised as "multiple racks", but managed to reduce blast radius.)
13. 73.▲
    by mfreed 6y ago

    1. Timescale sells a fully managed service offering running on AWS, GCP, or Azure. So you can get started with 3-4 clicks and have a database running in 30 seconds. (We actually don't sell "software" at all - that's all
14. 74.▲
    by mfreed 6y ago

    Sorry harder to found, but pricing calculator on product page (not gated): https://www.timescale.com/products#pricing
15. 75.▲
    by mfreed 6y ago

    Hi @nwsm: Timescale offers a fully managed version of TimescaleDB on AWS, GCP, and Azure, starting at $49/month. https://www.timescale.com/timescale-signup
16. 76.▲
    by mfreed 6y ago

    You can create a hypertable with a UNIQUE composite key on (row_id, time). Otherwise, you are correct in that we require your partitioning keys to be at least _part_ of unique constraints; otherwise, we'd need to build global indexes a
17. 77.▲
    by mfreed 6y ago

    Although even if Google were to add support for TimescaleDB, it would only be for the Apache-2 version of the database, which lacks many of its key features (compression, continuous aggregates, multi-node scale out, data retention policies,
18. 78.▲
    by mfreed 6y ago

    TimescaleDB inherits from Postgres a rich role-based access control, so all requests require permissions and roles can be enforced at various levels (database, schema, table, or even rows) and privileges (SELECT, INSERT, DELETE, CREATE, etc
19. 79.▲
    by mfreed 6y ago

    And we in fact have fully open-source/free k8s helm charts to easily spin up TimescaleDB, including with HA and automated failure detection/failover and streaming replication for incremental backups: https://github.com&
20. 80.▲
    by mfreed 6y ago

    I think we (like many) stand on the shoulders of giants when it comes to software, but I’m not sure the comparison is quite apt. Amazon primarily runs and monetizes closed-source, SaaS-only managed services. TimescaleDB instead is implement
21. 81.▲
    by mfreed 6y ago

    > If I were building an developer focused analytics, monitoring, or data analysis product, I wouldn't do it on top of Timescale because some parts of your codebase most definitely prevent that through your license. But that's m
22. 82.▲
    by mfreed 6y ago

    Sorry about that! Can you email me any screenshots / info at mike (at) timescale? Thanks!
23. 83.▲
    by mfreed 6y ago

    Yes, TimescaleDB plays friendly with most PG extensions. And Timescale Cloud comes pre-loaded with many of them - https://kb.timescale.cloud/en/articles/2754991-supported-pos...
24. 84.▲
    by mfreed 6y ago

    Our docs cover some of the data node management [0] and native replication [1] particular in more detail. Right now you can use Postgres physical replication for the access node, with one as the primary (and handling DDL/writes), while
25. 85.▲
    by mfreed 6y ago

    Yes, with the observation is that this is the base flexibility, while we will be adding much more transparent stuff in the future. So in 2.0, if you want a chunk of a distributed hypertable replicated, you don't do it manually, but ju
26. 86.▲
    by mfreed 6y ago

    Yes, works with SQLAlchemy. (Like many ORMs there are a couple things to be aware of, but plenty StackOverflow questions about these already :) And yes, people use it for event sourcing. Often see this in various product analytics use case
27. 87.▲
    by mfreed 6y ago

    Thanks for thoughts here. One thing we continually hear is that the familiarity, trust, ecosystem, maturity, etc. that folks love about Postgres is a huge boon and one deciding factor for their adoption of TimescaleDB. Just to clarify: thos
28. 88.▲
    by mfreed 6y ago

    Regarding offerings on Timescale Cloud around "IO-optimized", "compute-optimized", and "storage-optimized", and particularly that Timescale Cloud runs on all three major clouds (AWS, Azure, GCP) across 76 regio
29. 89.▲
    by mfreed 6y ago

    Thanks for all the questions @eloff! I might try to separate responses for hopefully some threading :) The software in our architecture is actually unified: You spin up K instances of TimescaleDB, log into one of them and then call "
30. 90.▲
    by mfreed 6y ago

    One of interesting things we’ve found is that the typical data models we’ve seen in TimescaleDB (and time-series workloads in general) is that, while having JOINs and additional tables with metadata, business info, etc. is super useful -- a