Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
asim
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
42 ms
·
691.
▲
by
asim
4y ago
It's real code https://github.com/micro/services It runs on software that's also real https://github.com/micro/micro It's hosted on a cloud platform with real customers https:/
692.
▲
by
asim
4y ago
I mean opinions are better than generic solutions so yea I think having X implementations of the same thing isn't of value but at the same time something as simple as github star count, forks, etc created a signal for what had momentum
693.
▲
by
asim
4y ago
lol, really don't want to be in the same sentence as Urbit so please no. Everything is defined as protobuf interfaces, which is a standard used by Google and everyone else now that gRPC is so dominant. So the idea is, define the API in
694.
▲
by
asim
4y ago
Building a standard set of interfaces consumed as APIs regardless of what the backend implementation is. Something that exists on a network rather than as a library that can be executed and changed ad-hoc without having to upgrade thousands
695.
▲
by
asim
4y ago
Yea like you're part of this club that has exclusive access to something, you contribute to it, deliver value, see it grow and then it's gone when you leave. It exists within a silo and for the better part of a decade that's
696.
▲
by
asim
4y ago
Just a desire to define an abstraction that's going to be consistent across all the services built. The value of a services catalog isn't just many separate services but the consistency and ability to reuse many in a coordinated f
697.
▲
by
asim
4y ago
Born in 84. I have been a user of all the above. The reason I mentioned GitHub to this level is truly in 2009 onwards it unlocked sharing of code at a level I had not seen before. It really did eclipse the reuse of software to what came pri
698.
▲
by
asim
4y ago
Why is the standard library not a HTTP call? Maybe all of this stuff ends up in WASM, I don't know, but I just get the feeling like if it was all over a network that's constantly evolving and becoming faster, that we end up with s
699.
▲
by
asim
4y ago
Hey, I have a non-comprehensive list of issues for new services https://github.com/micro/services/issues but most of the bugs/features are still in my head for other stuff. I think purely on the DB front we n
700.
▲
by
asim
4y ago
So in a case like email it's a local shim to sendgrid. What this essentially means is you have one service that's storing your API key and gatekeeping access to sending email rather than all of them doing it independently. In the
701.
▲
by
asim
4y ago
Yea we are aware, there's a lexer/parser but ideally we should have some Query op and use prepared statements. I am probably looking for some additional help on that front in the near future.
702.
▲
by
asim
4y ago
Probably not but users tell me when something isn't working. I spent my entire career in this sort of development model where 80% was good enough, put it into production and then moved on. When something breaks, fix it, when something
703.
▲
by
asim
4y ago
Not sure how to approach that comment really, I don't think it matters if the pattern used is microservices or not, the basic premise that we're still way far off reusability of software that's basically identical across thou
704.
▲
by
asim
4y ago
I value your points because they are the same concerns I would have being a CTO of a company. Ultimately vendors don't yet care enough about this problem to invest in it and I think ultimately that's a mistake because while we hav
705.
▲
by
asim
4y ago
hear hear
706.
▲
by
asim
4y ago
So I'll start by saying, I've spent the past 7 years working predominantly on open source, 4 of those years were bootstrapped and the majority of stuff I've written is basically given away for free. I fully understand what th
707.
▲
by
asim
4y ago
Can you point to the ones you're talking about? A lot of the services are actually not that, they're offering simplified API and RPC access to data that's siloed elsewhere or systems that are quite complex to manage. There&#x
708.
▲
by
asim
4y ago
I don't know what other people's motivation is but for me after experiencing life at Google and elsewhere I really understood that to build anything at scale takes a multi-year effort building on the foundations already set. Googl
709.
▲
by
asim
4y ago
Testing in production https://m3o.com
710.
▲
by
asim
4y ago
Even if they did we have no standardisation. I truly wish we had Android for Cloud. An open source operating system and framework that then let people publish software that worked seamlessly on it. I don't think docker and kubernetes w
711.
▲
by
asim
4y ago
There are some services that are still singular endpoint you're right e.g SMS. But the goal is to address immediate need and expand on requirements beyond it. No one using SMS has asked for more yet. Other things are more full fledged
712.
▲
by
asim
4y ago
I spent quite a few years working on a standalone framework called Go Micro which has now been donated to a community - https://github.com/go-micro/go-micro . Ultimately it never really achieved the potential standardi
713.
▲
by
asim
4y ago
Right now I'm just sharing a set of open source services. A hosted offering exists as an API platform called M3O as mentioned in the post. Ideally just as infrastructure is now shared as cloud services maybe the same would occur here b
714.
▲
by
asim
4y ago
Hey, maintainer here. Happy to answer questions. I know some people are skeptical of such an idea working outside of an existing organisation or without large vendor support but had to take a shot nonetheless. These are built and hosted for
715.
▲
by
asim
4y ago
Kudos to Kenton who keeps delivering great stuff on Workers.
716.
▲
Real World Micro Services
(micro.dev)
189 points
by
asim
4y ago
|
126 comments
717.
▲
by
asim
4y ago
> What I actually want is a well designed and integrated solution for 80 to 90% of these functions. I agree. I think a lot of this should just be done by one tool. Unfortunately the incumbents like Google and Microsoft are doing a poor j
718.
▲
by
asim
4y ago
So many tools. What really frustrates me about stuff like this, every new employee brings in their own biases and tools they prefer to work with, then there's a battle over working with an existing process or replacing it for the new s
719.
▲
by
asim
4y ago
Whoa I love SMTP and email, as a distributed systems nerd I'm a huge fan of the federated protocol and it's simplicity but JMAP I'm sorry is garbage. The http/json part is great, the potential to simplify email access an
720.
▲
by
asim
4y ago
I think that just sort of says, hey share this signal.tube link or use a hashtag on a public channel like Twitter. When they say DM or use a private channel to distribute it my question is, what are those channels? What if those are also bl
More ›