ASasim·Nov 29, 2022
We used Micro to build and offer Micro services on M3O. Every API to you see there is powered by the open source equivalent Micro service here https://github.com/micro/services
In The best Go framework: no framework?micro
services
HISTORICAL RECORD2020–2022
micro / services · Not publicly available
services
Discover this repository through its Hacker News conversations.
6Distinct people
19Mentions
0Explicit recommenders
What to know before exploring
What it is
A public description has not been verified.
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month19 dated mentions
Observed mentions: 2020-11-10 15:31:36 UTC to 2022-11-29 17:16:51 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Nov 2020 | 2020-11-01 00:00:00 UTC | 2020-12-01 00:00:00 UTC | 4 | 0 | 4 |
| Dec 2020 | 2020-12-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 2 | 0 | 2 |
| Jan 2021 | 2021-01-01 00:00:00 UTC | 2021-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2021 | 2021-02-01 00:00:00 UTC | 2021-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2021 | 2021-03-01 00:00:00 UTC | 2021-04-01 00:00:00 UTC | 1 | 0 | 1 |
| Apr 2021 | 2021-04-01 00:00:00 UTC | 2021-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2021 | 2021-05-01 00:00:00 UTC | 2021-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2021 | 2021-06-01 00:00:00 UTC | 2021-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2021 | 2021-07-01 00:00:00 UTC | 2021-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2021 | 2021-08-01 00:00:00 UTC | 2021-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2021 | 2021-09-01 00:00:00 UTC | 2021-10-01 00:00:00 UTC | 2 | 0 | 2 |
| Oct 2021 | 2021-10-01 00:00:00 UTC | 2021-11-01 00:00:00 UTC | 1 | 0 | 1 |
| Nov 2021 | 2021-11-01 00:00:00 UTC | 2021-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2021 | 2021-12-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2022 | 2022-01-01 00:00:00 UTC | 2022-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2022 | 2022-02-01 00:00:00 UTC | 2022-03-01 00:00:00 UTC | 1 | 1 | 0 |
| Mar 2022 | 2022-03-01 00:00:00 UTC | 2022-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2022 | 2022-04-01 00:00:00 UTC | 2022-05-01 00:00:00 UTC | 2 | 0 | 2 |
| May 2022 | 2022-05-01 00:00:00 UTC | 2022-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2022 | 2022-06-01 00:00:00 UTC | 2022-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2022 | 2022-07-01 00:00:00 UTC | 2022-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2022 | 2022-08-01 00:00:00 UTC | 2022-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2022 | 2022-09-01 00:00:00 UTC | 2022-10-01 00:00:00 UTC | 5 | 0 | 5 |
| Oct 2022 | 2022-10-01 00:00:00 UTC | 2022-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2022 | 2022-11-01 00:00:00 UTC | 2022-12-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
19 sourcesThanks, that made now more sense. I'd put this condensed together with https://micro.dev/blog/2022/09/27/real-world-micro-services.... more prominently to the readme of https://github.com/micro/services ! Looking at that github alone makes it hard to commect the context.
In Real World Micro ServicesI also can't really take this seriously. Maybe I'm ignorant of something to the Go ecosystem that makes this relevant, but this seems truly bizarre.
The "answer" microservice says: "Instant answers to any question" / "Ask a question and get an instant answer". Okay? Like, is this a service that I would have to back with my own knowledgebase? In which case this is just a service that accepts questions and serves answers? Why would this need its own service then?
The "address" microservice says: "Lookup UK addresses by postcode. Simply provide a valid postcode and get a full list of addresses". Why is this not called "uk-address" then? Or can it be modified for arbitrary locations? Does it handle when new addresses are created? Can it do validation?
How much demand is there for a "joke" microservice? And I think it shows a lack of professio
Read the rest
nalism to seed such a microservice with something like this: https://github.com/micro/services/blob/master/joke/examples....
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://m3o.com
In Real World Micro ServicesHey, 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 need to add a new Query endpoint that's more powerful that will accept a repeated array for Filter options that look like the below.
message QueryRequest {
repeated Filter filters = 1;
}
message QueryResponse {
repeated Record records = 1;
}
message Filter {
string field = 1;
string op = 2;
string value = 3;
}
Something like that. I think otherwise a majority of issues really become clear through use, so those using the services tend to see where the pitfalls are or where they can contribute. It's harder to do that without context and arguably less enjoyable for the person contributing as they're not seeing that change in
Read the rest
whatever they're doing.
Thanks for the comments and questions. I'll do my best to answer them.
> Are things hosted on some other cloud provider, if so where? What region?
Our core platform is currently hosted on DigitalOcean in the London region. That will expand to multiple regions and multiple providers over time. We did start that way many years ago but with a small team it's hard to manage.
> What about uptime? If I end up building an application with all of these APIs, I do need a bit more confidence that things will be stable.
We want to be able to provide uptime guarantees in the near future. Right now I'll say based on our experience running it in the past 9-12 months it's feeling like four 9s verging on 5 but I don't want to jinx us. We are dependent on our providers but we're also people who have managed platforms for many years.
> the crypto endpoint
Read the rest
looks interesting, but for me, it would be quite crucial to know where the data is from? How often is it updated?
Our crypto APIs are currently powered Finage.co.uk. We do some level of caching on our side but only for 5-10 mins. I'll try add some details around that in the overview. You can see the source at https://github.com/micro/services
> For the "Google" endpoint, I'm missing the option to select mobile or desktop results, and also what's the default region? Is this done via a headless chrome instance running somewhere, or just curling results? Do I have to worry that your IPs will be blacklisted by Google if there are too many queries?
This is using Google's custom JSON query API. It's pretty limited but we also started with a very simple usecase. You're the first to ask for anything more advanced and that's how we'd look into it. So happy to dig in more and see if we can work on it.
> And a random idea for the "Comments" API it would be great to combine it with the "Spam" endpoint that's available for emails.
Thanks will look into it!
Thanks for the comments. Yea so we used to say "Powered By X" to indicate what the APIs were backed by but it was a little hacky. We'll try to reintroduce something back into specify the "source". You can otherwise see all the source code for the services in a monorepo on GitHub https://github.com/micro/services. Would be interested to get feedback on a better way to make it available.
In Show HN: M3O – Universal Public API InterfaceShow HN: Micro Services – Reusable real world open source services
2 points · Open discussionNo, that's incorrect. We provide a catalog of services as public APIs consumed via HTTP/JSON. So far we offer 35+ services which you can see here https://m3o.com/explore. Those services are open source and you can see the source code at https://github.com/micro/services. The entire suite of services are built using the Micro platform which is also open source. Think Android for Cloud.
In M3O – An open source AWS alternativeBasically the only way this really works is if we define standard APIs for all forms of cloud services. From infrastructure all the way up to social media and beyond. In prior eras protocols were custom designs on top of the IP protocol. That's not going to fly today and it also won't let us move fast enough. Most API definitions at the likes of Google are now defined in protobuf, another alternative is openapi. Either would suffice but I think protobuf is less verbose and potentially easier to evolve.
It also requires open standards for defining those services and potentially open implementations. See github.com/micro/services as an example.
Ultimately it's going to take a long time and significant coordination between multiple players for it to happen. I do wish we just had an open set of services anyone could run and contribute to. The
Read the rest
n we could either go through the pains of hosting ourselves or paying someone to do it for us.
Yes, we are building on that API. It's referenced here https://github.com/micro/services/tree/master/quran. Unfortunately we're having some issues with our readme processing and haven't yet fixed. All credit will be given where it is due.
In Quran APIWe had standardisation at the protocol level for the internet which let us build services on top, but now we're looking for the same at the app level. HTTP was meant for web pages, we never created anything for Apps and Services. What that new standard is going to look like, I have no idea, gRPC does well to define the APIs and so we use it across dozens of services here https://github.com/micro/services. Curious to hear what others think will happen.
In Bring Your Own Client> It's open source and you can self host it yourself if you want.
But you can’t use it commercially, right?
https://github.com/micro/services/blob/master/LICENSE
In A new API backend for the jamstackFirst of all I think there is merit in trying to do "Netlify for the backend". Or a more flexible and backend focused variation of Vercel (I think they only let you do FaaS, correct me if I'm wrong). Services like these provide a constrained, "just works" user (dev) experience.
However, I don't like the name "Micro Services". It seems like the authors are trying to hijack a well established term for their brand. This might be incredibly confusing for new developers and at the same time turn off experienced ones.
Also there seems to be little explanation of the storage system. From the docs:
> State is a fundamental requirement of any system. We provide a key-value store to provide simple storage of state which can be shared between services or offload long term to keep microservices stateless and horizontally scalable.
Is key-value standa
Read the rest
rd practice for the target audience? This is a little bit of a point of confusion. Especially if we're dealing with a language like Go, which has many benefits and advantages, but expressiveness is not one of them. So building up ad-hoc relational logic with it seems scary!
I'm not too familiar with Go. But from reading some of the example code[0] I get the feeling that there must be some very good reason for avoiding relational.
And what confuses me further is the name collision with go-micro[1].
[0] https://github.com/micro/services/blob/master/messages/handl...
[1] https://github.com/asim/go-micro
Showing the 15 most recent of 19 sources. Enable JavaScript to search and browse every indexed mention.