leehampton

Timescale | Remote

We're looking for experienced software engineers to help us build and maintain our managed TimescaleDB cloud services. You will have the opportunity to work with a close-knit team and build out the cloud platform for TimescaleDB. Depending on the role, you will develop Golang services and features to power our platform, work with our underlying Kubernetes infrastructure to ensure stability, security, and performance, or some combination of both!

Timescale is a remote-first organization; this is a full-time position and can be located anywhere across a wide range of time zones and locations (UTC-8 to UTC+3)

See the relevant roles below:

https://www.timescale.com/careers/4128985002-cloud-engineer https://www.timescale.com/careers/5052759002-infrastructure-... https://www.timescale.com/careers/5052761002-kubernetes-engi...

See additional roles, including Support Engineer, Developer Advocate, Prometheus Open Source Contributor, and Product Marketing Manager below:

https://www.timescale.com/careers

Timescale | Remote

We're looking for experienced cloud engineers to help us build and maintain our managed TimescaleDB cloud services. You will have the opportunity to work with a close-knit team, developing Golang services and features to power our platform as well as working with our underlying Kubernetes infrastructure to ensure stability, security, and performance.

Timescale is a remote-first organization; this is a full-time position and can be located anywhere across a wide range of time zones and locations (UTC-8 to UTC+3)

See the role below:

https://www.timescale.com/careers/4128985002-cloud-engineer

See additional roles, including Support Engineer, Developer Advocate, Prometheus Open Source Contributor, and Product Marketing Manager below:

https://www.timescale.com/careers

I love HA Proxy, but one thing I'm confused about is why the http-tunnel feature was removed in this release (and deprecated in earlier 2.x releases). http-tunnel allowed you to start a session with an HTTP request/response, then keep the socket to the backend alive without further inspection of the protocol.

This is useful for things like RTSP where you kick things off with HTTP but then stream lower level TCP content over the same socket. There are also lots of other custom protocols that benefit from this type of set up, including one that I'm working on wrangling HA Proxy to work with now.

Does anyone know if there's some replacement way to handle this in HA Proxy that I'm overlooking?

Hey rw, one of the core contributors to TSBS here. First of all, thank you for the work you did on influxdb-comparisons, it gave us a lot to work with and helped us understand Timescale’s strengths and weaknesses against other systems early on. We do appreciate the diligence and transparency that went into the project. We outline some of the reasons for our eventual decision to fork the project in our recent release post [1]. Most of the reasons boil down to needing more flexibility in the data models/use cases we benchmark and needing a more maintainable code design since we’re using this widely for a lot of internal testing.

Verification of the correctness of the query results is obviously something we take very seriously, otherwise running these benchmarks would be pretty pointless. We carefully verified the correctness of all of the query benchmarks we published. However, it’s a process we haven’t fully automated yet. From what we can tell, the same is true of influxdb-comparisons — the validation pretty prints full responses but each database has a significantly different format, so one needs to manually parse the results or set up a separate tool to do so. We have our own methods for doing that internally — once we get the process more standardized and automated we will definitely be adding it to TSBS. We encourage anyone with ideas around that (or anything else) to take a look at the open source TSBS code and consider contributing [2].

[1] https://blog.timescale.com/time-series-database-benchmarks-t...

[2] https://github.com/timescale/tsbs

Canary | Mid-Senior Level Backend Engineer | New York/NYC - Manhattan | Onsite

Canary is a smart, all-in-one home security system. Check out the product at https://www.canary.is

We're looking for backend engineers to help us scale and add features to our systems, which deal with live and on-demand video, sensor data, communication with our IoT devices, and more.

Primary Technologies: Python, Go, MySQL, DynamoDB, Redis, RabbitMQ, Kinesis, AWS, Docker

Requirements: At least 3 years of production experience working with high volume distributed systems. Strong understanding of concurrency. Knowledge of relational and non-relational databases. Comfortable in a cloud computing environment like AWS. Experience with DevOps, Configuration Management, and CI/CD is a huge plus.

Email your resume to [email protected] with a brief note if you're interested in applying.