Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Micro 3.0 is a platform for cloud native development

micro.mu

Post reply on HN
Print view View original

51–60 of 63 posts

Re: Micro 3.0 is a platform for cloud native development

#51

Post by asim »

punkbit wrote: post #48
asim wrote: post #45

Earlier quoted context omitted.

Yes! We are Netlify for the backend and in fact our next post will be titled "Netlify for your frontend, Micro for the backend". We think there's really a need to do what Netlify did for frontend to the backend and just help people build APIs and services super fast. The M3O Docs have some content about getting started with things quickly https://docs.m3o.com/getting-started but we need to add more. The open source d…

Thanks for replying back to me, I've been having a look and it seems that you guys are very talented. I'm going to start a new project and if this can help me save time and not have to deal with aws, etc would be great! Depending on cost of course. Hopefully we can get some info in terms of cost. About the repository/database layer, I found the "store" documentation; just going through things quickly at the moment, b…

No worries. Please join the slack at https://slack.m3o.com if you need help or want to engage with the community. For us Store means key-value or crud data storage. I think if that's what you're calling repository for persistence then that's it. If you're thinking repository as in git then that's a separate connective piece from "source to running" which basically you can do by running the git URL.

On the store front. We are working on a data model so we can move beyond key-value which might end up being of interest.

Re: Micro 3.0 is a platform for cloud native development

#52

Post by asim »

bdcravens wrote: post #44
punkbit wrote: post #41

I've been learning golang for backend dev, and for that reason checked your project. Is this sort of like Netlify for the backend? Are there any examples of how the repository/database layer fits here? What'll happen to the name m3o when Micro reaches 4.0?

“M3o” refers to the 3 letters in the middle, not the version number (similar to i18n or k8s)

This is correct

Re: Micro 3.0 is a platform for cloud native development

#53

Post by asim »

karmakaze wrote: post #47

Regarding these two points: - Key-Value Storage - Event Streaming Is there specific software used for these--what are its characteristics comparable with?

We use cockroachdb for the storage and nats-streaming for events. We know cockroach is a SQL database but the scaling properties are nice, we know the team and we think we'll leverage the SQL layer too so it's a good fit. On events the reason we chose nats-streaming over Kafka is because of the low memory footprint and because we've been using nats for a long time in Micro and know the creator Derek Collison pretty well. We trust these technologies a lot.

Over time we'll offload these to managed services and potentially allow people to plug and play based on their needs.

Re: Micro 3.0 is a platform for cloud native development

#54

Post by punkbit »

asim wrote: post #51
punkbit wrote: post #48

Earlier quoted context omitted.

Thanks for replying back to me, I've been having a look and it seems that you guys are very talented. I'm going to start a new project and if this can help me save time and not have to deal with aws, etc would be great! Depending on cost of course. Hopefully we can get some info in terms of cost. About the repository/database layer, I found the "store" documentation; just going through things quickly at the moment, b…

No worries. Please join the slack at https://slack.m3o.com if you need help or want to engage with the community. For us Store means key-value or crud data storage. I think if that's what you're calling repository for persistence then that's it. If you're thinking repository as in git then that's a separate connective piece from "source to running" which basically you can do by running the git URL. On the store front…

Yes, as in CRUD data storage. I'll join slack.

Good luck Asim, the project is kick ass!

Re: Micro 3.0 is a platform for cloud native development

#55

Post by unneededlogic »

asim wrote: post #51
punkbit wrote: post #48

Earlier quoted context omitted.

Thanks for replying back to me, I've been having a look and it seems that you guys are very talented. I'm going to start a new project and if this can help me save time and not have to deal with aws, etc would be great! Depending on cost of course. Hopefully we can get some info in terms of cost. About the repository/database layer, I found the "store" documentation; just going through things quickly at the moment, b…

No worries. Please join the slack at https://slack.m3o.com if you need help or want to engage with the community. For us Store means key-value or crud data storage. I think if that's what you're calling repository for persistence then that's it. If you're thinking repository as in git then that's a separate connective piece from "source to running" which basically you can do by running the git URL. On the store front…

I see that you can point it at a git URL and I see the "running a git source" section of the docs, but I am not seeing how to authenticate to a Github or Gitlab repository if it is not publicly viewable. Do you support that type of authentication?

Re: Micro 3.0 is a platform for cloud native development

#56

Post by asim »

unneededlogic wrote: post #55
asim wrote: post #51

Earlier quoted context omitted.

No worries. Please join the slack at https://slack.m3o.com if you need help or want to engage with the community. For us Store means key-value or crud data storage. I think if that's what you're calling repository for persistence then that's it. If you're thinking repository as in git then that's a separate connective piece from "source to running" which basically you can do by running the git URL. On the store front…

I see that you can point it at a git URL and I see the "running a git source" section of the docs, but I am not seeing how to authenticate to a Github or Gitlab repository if it is not publicly viewable. Do you support that type of authentication?

Yes. See the doc on private repos https://docs.m3o.com/getting-started/private-repos. Hopefully that helps. If not please drop into slack (https://slack.m3o.com) and we can try help further

Re: Micro 3.0 is a platform for cloud native development

#57

Post by asim »

punkbit wrote: post #54
asim wrote: post #51

Earlier quoted context omitted.

No worries. Please join the slack at https://slack.m3o.com if you need help or want to engage with the community. For us Store means key-value or crud data storage. I think if that's what you're calling repository for persistence then that's it. If you're thinking repository as in git then that's a separate connective piece from "source to running" which basically you can do by running the git URL. On the store front…

Yes, as in CRUD data storage. I'll join slack. Good luck Asim, the project is kick ass!

Thank you!

Re: Micro 3.0 is a platform for cloud native development

#58

Post by asim »

kp995 wrote: post #23
friendly_chap wrote: post #2

Hi people, I'm one of the people working on this. Thanks for your support! If you want to try the thing in minutes may I advise you to start here: https://m3o.com/start . Pretty much just a couple of commands to get started :)). Cheers

Hi, Great work just one tip, adding syntax highlighting to the start page will help. I noticed you have that similar on landing page tho

Thanks, its raw html at the moment. The front page is using carbon which seems to help. Need to figure out better embedding of commands.

Re: Micro 3.0 is a platform for cloud native development

#59

Post by capableweb »

emptysongglass wrote: post #43
capableweb wrote: post #39

Earlier quoted context omitted.

> nothing but maintenance. It's not something to be proud of What? Absolutely! Maintenance is hard. Maintenance of old/big/complex systems is even harder. Maintaining something for so long with substantial user base is definitely something to be proud for. Everything doesn't need to constantly add features in order for people to be proud of their work. Just adding bug/security fixes once you feel something is feature…

I think you've run off with the ball a bit here. I have plenty of respect for maintainers. To the example we're addressing, of OpenOffice: nothing but maintenance is the big deal here. Maintenance is hard, yes but you can also find a developer or two to push the ball ahead a bit and Apache hasn't seen fit to do even that.

I don't think I have. You say your respect it but then say "nothing but maintenance is the big deal here".

My point was, nothing but maintenance is OK too, and sometimes even favorable, depending on what you're working on.

As an example, the software behind HN is pretty much maintenance-only for as long as I've been lurking here. While there is bug fixes sometimes, I don't think there been any new features the last few years. You don't think the people running the HN software should be proud of that?

Post reply on HN