Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mfreed
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
15 ms
·
91.
▲
by
mfreed
6y ago
Yes, our offering is of the "open core" nature, although our non-open-source code is covered under the Timescale License (source available, free). For most "open core" companies, this latter part is instead closed-sourc
92.
▲
by
mfreed
6y ago
Hi @camkego We tried pretty hard to define a pretty specific definition of "Value Added Service" for TimescaleDB, which is why the license also has some "custom" aspects rather than just having a general clause about &qu
93.
▲
by
mfreed
6y ago
Oof. Making undergrad course project reports available for the world to see! ;) The third member of that team has also built some pretty cool technology -- maybe behind some of the music you're listening to right now: https:/
94.
▲
by
mfreed
6y ago
where the authors are hiding the implementation from public scrutiny We agree that such visibility is a good thing! All of our source code (both Apache-2 and TSL) has always been public on github: https://github.c
95.
▲
by
mfreed
6y ago
Not sure I follow? The parent poster was asking about "well, isn't it an issue with your TSL definition of 'DDL schema access' if you can store data in JSON or EAV so it doesn't have a 'fixed schema'"
96.
▲
by
mfreed
6y ago
My own perspective is that companies should probably stop saying that "if only Amazon would contribute back the occasional patch, everything would be fine." If much of the future is cloud, then getting the hyper-scalars to contrib
97.
▲
by
mfreed
6y ago
Appreciate the sentiment. We try pretty hard to be careful to not describe the Timescale Licensed code as Open Source, and typically refer to it as "source available". Of course, a big portion of our code is licensed under Apache
98.
▲
by
mfreed
6y ago
The "Software" column of product page [0], which I assume you are referring to, corresponds to our Community Edition, as least from a feature-set edition. But thanks for the feedback. Always a balance between making things easily
99.
▲
by
mfreed
6y ago
Aww, thanks =) We are good co-editors for each other! We have a fun and long co-founder history, actually, going back >20 years. So lots of experience doing so!
100.
▲
by
mfreed
6y ago
The AGPL allows Amazon to offer a competing service. It just needs to be open-source. But the cloud vendor's efforts aren't typically with the software itself -- they often run the open-source version unmodified -- but rather with
101.
▲
by
mfreed
6y ago
Most of the enterprise features were moved actually moved into the Community tier in our 1.7 release, where we also announced that the upcoming multi-node would also be a Community feature: https://blog.timescale.com/blog&#x
102.
▲
by
mfreed
6y ago
You aren't only one =) https://twitter.com/bradfitz/status/1301565453702107136
103.
▲
by
mfreed
6y ago
This is all great to hear, and the whole team really loves this type of feedback/support from the community. So thank YOU! (Feel free to also reach out to me at mike (at) timescale anytime, or mike in slack.timescale.com)
104.
▲
by
mfreed
6y ago
Azure Postgres offers the Apache-2 Edition of TimescaleDB, not the Community Edition (which the TSL applies to). Same with DigitalOcean, Rackspace, Scaleways, Alibaba, etc. So they can continue to offer the Apache-2 Edition, but could not
105.
▲
by
mfreed
6y ago
Internally, a hypertable "partitions" data into 1+ dimensions, typically always by time, but also by other dimensions (esp. for multi-node). Each of these partitions are called a "chunk" (and are actually Postgres tables
106.
▲
by
mfreed
6y ago
Storing JSON or EAV-format data do not require DDL access, and are commonly deployed in many settings, from product/SaaS analytics, IoT, IT/APM monitoring, and others. That's actually one of the reasons we tried to frame it i
107.
▲
by
mfreed
6y ago
TimescaleDB (single-node) leverages Postgres features for HA (physical replication). It was never in the "enterprise tier", it fully works with the pure Apache 2 version. We also make available k8s helm charts that make it super
108.
▲
by
mfreed
6y ago
I posted below, but an important check really is the definition of the "Value Added Product or Service". https://www.timescale.com/legal/licenses#section-3-10-value-... On its face, it sounds like your use ca
109.
▲
by
mfreed
6y ago
Thanks for question. One of the things that Timescale License does (similar with Elastic, Confluent Community, etc.) is to define a "Value Added Service", and basically say you can utilize/distribute the database as part of a
110.
▲
Show HN: Updating the TimescaleDB license thanks to HN
25 points
by
mfreed
6y ago
|
1 comments
111.
▲
by
mfreed
6y ago
Also, we have a very active slack community if you want any other opinions: https://slack.timescale.com/ I'm mike there - come say hi.
112.
▲
by
mfreed
6y ago
Yep, absolutely. Here's a blog post outlining our general approach, which applies type-specific compression based on a column's datatype. (While m3db only supports floats, TimescaleDB supports a whole range of 40+ data types.) h
113.
▲
by
mfreed
6y ago
ORMs that work for Postgres should "just work" for TimescaleDB. So while we mention Sequelize in some tutorials, if you have a favorite Node.js API client, you should just go for it. As aside, you mention enjoy this developer Q&a
114.
▲
by
mfreed
6y ago
Would love to hear from the HN community: what are some of your favorite features in managed database or infra platforms, or what do you wish more platforms offered that are still hard-to-find?
115.
▲
by
mfreed
6y ago
=] And getting a true technical resource on the phone at AWS requires an enterprise support contract, which starts at an additional $15,000 / month.
116.
▲
by
mfreed
6y ago
Yep, Digital Ocean (as well as Azure, Rackspace, and others) offer TimescaleDB with their managed Postgres offerings, but they can only offer the Apache-2 version. So you don't get native compression, continuous aggregates, downsamplin
117.
▲
by
mfreed
6y ago
I haven't done experiments to measure downtime on Azure myself. SLAs are tricky once you dig very closely into the details. If I recall correctly, years ago when Google Cloud came out that they defined "uptime" as "respo
118.
▲
by
mfreed
6y ago
Pricing differs on Timescale Cloud based on the cloud & region to reflect variances of the underlying costs of running infrastructure on those regions. Azure Postgres and AWS RDS do _not_ include HA replication in their base price -- yo
119.
▲
by
mfreed
6y ago
And...if anybody is interested in helping us build the best cloud service for time-series data, we're hiring cloud engineers! https://www.timescale.com/careers/4128985002-cloud-engineer Timescale is a remote-first
120.
▲
by
mfreed
6y ago
Yes, there are a number of great options here provided out-of-box: 1. All plans (including the lowest-cost dev tier) includes PITR recovery out of the box. You can also "fork" any current database to a second instance (e.g., for
More ›