uzarubin
Joined 12 years ago
Karma
13
Submissions
14
Member since
Nov 19
Recent submissions
Comment · 3 years ago
Thanks Tim! We're working toward having visually appealing UI, especially for open source!
Comment · 3 years ago
We live more on the preventive side where we tap into the real-time data flow before it reaches logs or data stores. Therefore, enabling you to be preventive vs reactive.
Comment · 3 years ago
It was tasty : )
Comment · 4 years ago
At first I thought it was a bug on our account. Hopefully they resolve the outage soon.
Comment · 6 years ago
This is definitely a valid approach and it is an expensive path. Athena charges a hefty amount per query if you have a large dataset. In addition, this approach won't work if your data is serialized with something like protobuf.
Comment · 6 years ago
That's awesome! We support http and gRPC collection as well. Let us know what you have in mind.
Comment · 6 years ago
Batch is betting that more companies are going to be utilizing event sourcing in order to scale. We want to be a foundation piece in their data infrastructure and support their transition into event sourcing by initially offering replays. We want to be a "One stop shop" for all event sourcing needs.
Comment · 6 years ago
From their website: Kafka is an open-source distributed event streaming platform.
There are many use cases from piping website activity tracking, metrics, log aggregation and stream processing. For us, it's a communication layer utilized by our microservices. An event goes into the stream and any services that cares about that data will consume it. In other words, it's like an ultra-resilient, scalable, redis pub-sub with history that runs on the JVM. You can read more about the use cases here: https://kafka.apache.org/uses
edit: Sidenote, Kafka is often waaaaaay overkill - if you need messaging, use something simpler like Rabbit or NATS or Redis and only use Kafka if you know why you need it.
Comment · 6 years ago
Thank you! We felt the pain point while actively trying to build observability tools in order to debug our messaging systems. We built plumber to standardize some of our internal tools and then decided to open source it to help others who are feeling the pain.
Comment · 6 years ago
Fixed!
Comment · 6 years ago
We are planning to support as many messaging systems as we can. We will definitely investigate Pulsar. Going to add it to our feature list and make an issue on plumber to support introspection on Pulsar. Cheers!
Comment · 6 years ago
Ustin here.
It's definitely on our roadmap to fix. Thank you for the feedback!
Comment · 11 years ago
BELLHOPS
Chattanooga, TN Full time - on site
Bellhops has been exploding in popularity because we’re solving a problem that every American has had: moving. We’ve decided to attack this industry that hasn’t seen innovation since Henry Hohnsbeen invented the clipboard. We’re changing that by building a great organization of problem solvers who are at the top of their game. We're a hard working team that has a great time together.Join us at our Chattanooga, TN Headquarters. The city is home to the first municipal gigabit network in the nation, and was described by Outside Magazine as the best outdoor city in the country.
Tech: Python/Django Developer, DevOps Engineer, Sr. Front End Developer, Mobile Developer (iOS and/or Android)
Marketing: Digital Advertising Specialist (with SEM and SEO background)
Contact: [email protected] Apply at https://jobs.lever.co/bellhops/ and angel.co