tylertreat

7 ms·

31.
Stop Treating YAML Like a String(theyamlengineer.com)
23 points by tylertreat 2y ago|0 comments
32.
Automating Infrastructure as Code with Vertex AI(realkinetic.substack.com)
7 points by tylertreat 2y ago|0 comments
33.
Gitlab CI/CD vs. GitHub Actions: A Comprehensive Comparison(realkinetic.substack.com)
3 points by tylertreat 2y ago|0 comments
34.
It's Time to Retire Terraform(blog.realkinetic.com)
4 points by tylertreat 2y ago|0 comments
35.
Cloud Without Kubernetes(blog.realkinetic.com)
4 points by tylertreat 3y ago|0 comments
36.
No feature survives contact with the user(blog.witful.com)
5 points by tylertreat 4y ago|0 comments
37.
SRE Doesn't Scale(bravenewgeek.com)
2 points by tylertreat 5y ago|0 comments
38.
My approach to taking notes in meetings(blog.witful.com)
152 points by tylertreat 5y ago|65 comments
39.
Show HN: Witful, meeting notes and action items connected to your calendar(witful.com)
3 points by tylertreat 6y ago|0 comments
40.
The trickiest Elm bug I've ever seen(blog.realkinetic.com)
1 points by tylertreat 6y ago|0 comments
41.
We built an app to fix our own meeting fatigue(witful.com)
10 points by tylertreat 6y ago|2 comments
42.
by tylertreat 6y ago
Thanks, this is a good suggestion. The docs definitely need a lot of work still!
43.
by tylertreat 6y ago
Some of the key differences: - Written in Go rather than Java/Scala (big benefit here IMO is getting a small static binary rather than having to run a JVM) - Doesn't rely on Zookeeper - Is integrated with NATS (can extend NATS wit
44.
by tylertreat 6y ago
I'm not super familiar with Akka beyond high-level/actor model so I can't competently compare the two. NATS can be used to implement an actor model and has a similar philosophy to Akka core in terms of delivery semantics (i.e
45.
by tylertreat 6y ago
Good question. It's early days, so there's still a lot of work to be done around geo-replication/geo-aware. It depends on the specific use case, but there are a few approaches you could take. You could run a Liftbridge and NA
46.
by tylertreat 6y ago
Author here. I started Liftbridge after working as a core committer on NATS and NATS Streaming (as well as my experience using Kafka in the past). In particular, implementing replication in NATS Streaming and drawing from that experience&#x
47.
Show HN: Liftbridge – Lightweight, fault-tolerant message streams(liftbridge.io)
147 points by tylertreat 6y ago|24 comments
48.
by tylertreat 7y ago
Yes, for more on that see my reply here: https://news.ycombinator.com/item?id=21946939
49.
by tylertreat 7y ago
It's getting very close. I had wanted to make a production-ready 1.0 release before the end of the year, but we're in the process of switching from protobuf to flatbuffers. Once that is complete, a stable release will be made.
50.
by tylertreat 7y ago
ZeroMQ is not a message queue, it's a networking library.
51.
by tylertreat 7y ago
Check out Liftbridge ( https://liftbridge.io ) as a way to add these capabilities to NATS.
52.
by tylertreat 7y ago
Also check out Liftbridge ( https://liftbridge.io ), which is a Kafka-like API on top of NATS. Disclaimer: I'm the author and former core contributor of NATS and NATS Streaming.
53.
Terraform and Infrastructure as Code Best Practices(blog.realkinetic.com)
2 points by tylertreat 7y ago|1 comments
54.
What’s Going on with GKE and Anthos?(bravenewgeek.com)
7 points by tylertreat 7y ago|0 comments
55.
by tylertreat 7y ago
This is correct. Also, I'm planning to introduce a mode that runs NATS "embedded" within the Liftbridge server, such that NATS basically becomes an implementation detail of Liftbridge. Re: consumer-offset checkpointing, this
56.
by tylertreat 7y ago
It has at-least-once delivery guarantees currently. I have plans for some lightweight transactional-style publishing with an idempotent producer though.
57.
by tylertreat 7y ago
Just to clarify, Liftbridge relies on a single Raft group used purely for metadata replication, i.e. control plane, not data plane. Streams themselves are replicated using a protocol very similar to Kafka (ISR-based with followers fetching
58.
by tylertreat 7y ago
Basically the same types of uses cases as Kafka and similar systems: event sourcing, CQRS, stream processing (e.g. processing click stream events), data pipelines (e.g. log or metric aggregation used to feed multiple backends), or as a repl
59.
by tylertreat 7y ago
Author here. Happy to answer any questions.
60.
Security by Happenstance(bravenewgeek.com)
1 points by tylertreat 8y ago|0 comments

More ›