Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
StabbyCutyou
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
StabbyCutyou
5y ago
Thanks! In terms of backend engineering, I'd say one of the trickiest things is always depending deeply on a third party service or provider to be the backbone of the value you add. That's a pretty high level answer, but in genera
2.
▲
by
StabbyCutyou
5y ago
Yes! Right now we have a PD integration that will allow us to receive your alerts, and once you bind them to an Allma Incident, manage the alerts for you as well!
3.
▲
by
StabbyCutyou
5y ago
Hey folks! I'm Sean, the CTO of Allma. Would love to chat about the product if folks have any questions!
4.
▲
by
StabbyCutyou
10y ago
So, specifically in the context of a distributed queue (which, if we're talking about using MS arch + queueing due to scale concerns, you really need some kind of distribution to the message queue imo), these things get a lot harder. J
5.
▲
by
StabbyCutyou
10y ago
This is more of the intended audience (earlier startups or smaller groups of devs), but I could have done a better job spelling that out.
6.
▲
by
StabbyCutyou
10y ago
The accuracy of this statement is as depressing as it is apt.
7.
▲
by
StabbyCutyou
10y ago
Thanks for adding some historical context for me!
8.
▲
by
StabbyCutyou
10y ago
I didn't discuss queues because queues aren't intrinsically a part of a MS architecture. You certainly can do it that way, and there are lots of benefits, but queues (and if you're doing this at scale, distributed queues) are
9.
▲
by
StabbyCutyou
10y ago
Hello all you nice folks on HN. Original author of the article here. A few things I'd like to add, since this is essentially what feedback I get every time this has made the rounds: 1. I don't think microservices are bad, or that
10.
▲
by
StabbyCutyou
10y ago
Hi, original author here! Quickly, on the "elementary" nature of the post, this was adapted from a lightning talk I gave, and so it was sort of designed to be a very quick introduction into the problem space. Also this was meant t
11.
▲
Early Warning Detectors Using AWS Access Keys as Honeytokens
(blog.komand.com)
160 points
by
StabbyCutyou
10y ago
|
19 comments
12.
▲
by
StabbyCutyou
10y ago
Elegant, simple, and idiomatic. The perfect solution for Go.
13.
▲
by
StabbyCutyou
10y ago
This is definitely one of the main takeaways that I wanted to get across.
14.
▲
by
StabbyCutyou
10y ago
Well said, thanks!
15.
▲
by
StabbyCutyou
10y ago
I do wish I had titled it better, as most people have (rightfully) dinged me on this one ;)
16.
▲
by
StabbyCutyou
10y ago
One of the downsides of the blog post was that I adapted it from a lightning talk, so it was meant to be a little content-light, but to put ideas in peoples minds around how to think about the tradeoffs. For example, your point about Go vs
17.
▲
by
StabbyCutyou
10y ago
You have a good point in that in the early stages, any app is likely not to be a "monolith", but it's less about size/LOC and more about the design ethic of the architecture itself. If you build your codebase internally
18.
▲
by
StabbyCutyou
10y ago
Author here - your ninja edit is one of the core premises of the entire post. Some other folks have addressed the scalability questions you raised, but i'd add - I am in no way advocating for monoliths as a better approach. Rather, bot
19.
▲
by
StabbyCutyou
10y ago
I appreciate the feedback, but unfortunately I think you've made a bit of a leap in terms of what my point here was. It isn't that i'm saying "Don't build microservices", but rather "Don't adopt this
20.
▲
by
StabbyCutyou
10y ago
Hi, author here - thanks for taking the time read it. You're not wrong in that this article is meant to point out the pitfalls of the approach, and to advocate for understanding before diving into a particular architecture. It's m
21.
▲
by
StabbyCutyou
10y ago
Author here - Came to reply with basically what you just said. Thanks for giving it a read!
22.
▲
by
StabbyCutyou
11y ago
Well... Guess I need to rename https://github.com/StabbyCutyou/0db
23.
▲
Moldova – A utility for generating random data based on templated input
(github.com)
1 points
by
StabbyCutyou
11y ago
|
0 comments
24.
▲
by
StabbyCutyou
11y ago
They actually would let you increase that, but only up to a certain point and only if you specifically requested it. I don't see them mention the absolute ceiling being lifted, so that is probably still in place somewhere. I'd wag
25.
▲
by
StabbyCutyou
11y ago
I notice you're using interfaces to do your handlers, and (forgive me if i'm reading this wrong) casting those interfaces to a specific "type" of function before invoking them. That seems like it would be inefficient in
26.
▲
BuffStreams – Streaming Protocol Buffers messages over TCP in Go
(github.com)
10 points
by
StabbyCutyou
11y ago
|
0 comments
27.
▲
by
StabbyCutyou
11y ago
Hi, thanks for the feedback. Before I respond, let me say that I'm one of the core developers of the system, and that I am a big fan of Redis, and conceptually of Beanstalkd (never used it, but I know someone who is a big fan of it). T