Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
maxthegeek1
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
31.
▲
by
maxthegeek1
3y ago
Wow this is a really cool idea. I feel like in the future we're going to have more of this kind of stuff, and move away from the idea that product engineering, and infrastructure engineering can be cleanly separated. Infrastructural co
32.
▲
by
maxthegeek1
3y ago
Really cool. I wonder how much of this is going to make its way into GKE for us plebs.
33.
▲
by
maxthegeek1
3y ago
Congrats on the launch! Elasticsearch/Splunk/Datadog, are expensive beasts. It's great to see an opensource alternative!
34.
▲
by
maxthegeek1
3y ago
Thank you. :')
35.
▲
by
maxthegeek1
3y ago
Great question. Hasn't been requested yet, but I'm sure we'll need to support arm at some point.
36.
▲
by
maxthegeek1
3y ago
It's honestly gratifying to see that we landed on a similar product space independently. I read it as a strong signal that there's a real need for the product. I've been impressed by how much ground they've been able to
37.
▲
by
maxthegeek1
3y ago
Unfortunately, we don't plan on supporting caprover. We do plan on supporting render, and providing a helm chart in the near future.
38.
▲
by
maxthegeek1
3y ago
Currently, we're just hosting temporal ourselves in our k8s cluster. However, I've been working with their team, and we'll likely be migrating our temporal cluster over to their cloud in the near term future.
39.
▲
by
maxthegeek1
3y ago
Thank you, and you raise some great points. Re-"developer as the customer", the mismatch between who makes the buying decisions for this kind of tech (CMO's etc.), and the devs who do much of the heavy lifting to make it work
40.
▲
by
maxthegeek1
3y ago
Thanks! Definitely, migration guides are coming. In the meantime, feel free to ping us on our community slack and we'll walk you through a migration process.
41.
▲
by
maxthegeek1
3y ago
Great!
42.
▲
by
maxthegeek1
3y ago
Thanks for the kind words :) Temporal is a great technology for this use case. Wow, our DSL even looks similar! Your app has beautiful design, which I guess shouldn't come as a surprise given that it's Airbnb. Would love to chat t
43.
▲
by
maxthegeek1
3y ago
One of our motivations for selecting Clickhouse, is that it's relatively simple to run as a single node. This makes things easier for people who are looking to self-host a small to midsized installation of Dittofeed. It's also IMO
44.
▲
by
maxthegeek1
3y ago
+1. Wanted to jump in to say that the kafka dependency is strictly optional. It's used to batch writes to clickhouse, but for less intensive workloads Dittofeed can use clickhouse's asynchronous inserts for in-memory batching.
45.
▲
by
maxthegeek1
3y ago
Our plan is to model loops by having journeys define re-entry conditions, allowing users to run through journeys multiple times on a schedule. Would love to talk, to learn more about y'all are doing. My email is: max@dittofeed.com, or
46.
▲
by
maxthegeek1
3y ago
Offering a single executable binary is definitely great, but wouldn't be super practical given our choice of technologies. Tradeoffs.
47.
▲
by
maxthegeek1
3y ago
We're working on our second channel right now (mobile push), which will have the flow you'd expect when released. Thanks!
48.
▲
by
maxthegeek1
3y ago
Thank you! Choosing typescript was intentional on our part, because we want growth / marketing engineers to feel comfortable contributing.
49.
▲
by
maxthegeek1
3y ago
We have authorization built into the app, but are using a simple auth proxy, with oidc for authentication. If you want to authenticate your own app, you can use something like ouath2-proxy with an oidc provider, and set the `AUTH_MODE` conf
50.
▲
by
maxthegeek1
3y ago
It depends! If you're self-hosting you'll get your own clickhouse instance. Our base cloud hosting currently uses a multi-tenant clickhouse instance, but we also optionally provide a single tenant instance as part of our enterpris
51.
▲
Launch HN: Dittofeed (YC S22) – open-source customer engagement platform
135 points
by
maxthegeek1
3y ago
|
46 comments
52.
▲
by
maxthegeek1
4y ago
The best reason to use k8s is to take advantage of the wide array of open source k8s resources, including helm charts, custom operators, articles and tutorials etc. It's become an open standard. Like with many other technologies, k8s&#
53.
▲
by
maxthegeek1
4y ago
Pretty cool to see more db's built on top of modular components. Was first introduced to the concept in the context of FoundationDB and it's cool to see it here again!
54.
▲
by
maxthegeek1
4y ago
Yes, but you also don't want to have to deploy in the middle of the night in order to avoid downtime during peak hours. Not only is that a pain for whoever is monitoring the deployment, but now if the deployment breaks something you&#x
55.
▲
by
maxthegeek1
4y ago
What? I've never worked for a company that would tolerate downtime during deployments. Downtime is ok for personal projects, but not for most business applications.
56.
▲
by
maxthegeek1
4y ago
Snowflake is a pretty amazing piece of engineering. I suspect that solutions to problems of this kind, resource allocation given conflicting constraints and objectives, will only get more sophisticated over time.
57.
▲
by
maxthegeek1
4y ago
Hi, this seems like a really cool project! Given your use of rust, have you considered providing the option to run this as an embedded datastore, like you might use sqlite? Might bring more users onboard, for the better CI/testing ergo
58.
▲
by
maxthegeek1
4y ago
There's a whole world of engineering that standard software dev work relies on, that we're isolated from. It's rewarding to have the curtains pulled back every once in a while to appreciate the complexity of it all.
59.
▲
by
maxthegeek1
4y ago
Congrats! You all have a really great product and team.
60.
▲
by
maxthegeek1
4y ago
Super interesting to read about the implementation details of IPFS. IPFS feels like one of those developments in the space of decentralized applications, that's more likely to stand the test of time.
More ›