News for hackers. Stuff that matters.
Re:Micro 3.0 is a platform for cloud native development by heldrida on Tuesday November 10, 2020 @11:19AM (#25047649)
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?

Re:Micro 3.0 is a platform for cloud native development by asim on Tuesday November 10, 2020 @11:33AM (#25047821)
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 docs are a great reference https://micro.mu/reference and otherwise we're working on some sample services in https://github.com/micro/services.

Well luckily M3O is M[icr]o so I think we're going to get away with it for the long term :)

Re:Micro 3.0 is a platform for cloud native development by heldrida on Tuesday November 10, 2020 @11:39AM (#25047896)
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, but guess that's what store means in the Architecture?

I'll check the examples you've provided and read the documentation properly.

Thank you and good luck!

Re:Micro 3.0 is a platform for cloud native development by asim on Tuesday November 10, 2020 @12:25PM (#25048449)
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 by unneededlogic on Tuesday November 10, 2020 @12:50PM (#25048754)
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 by asim on Tuesday November 10, 2020 @01:13PM (#25049082)
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 by heldrida on Tuesday November 10, 2020 @12:38PM (#25048599)
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 by asim on Tuesday November 10, 2020 @01:13PM (#25049085)
Thank you!
Re:Micro 3.0 is a platform for cloud native development by bdcravens on Tuesday November 10, 2020 @11:30AM (#25047792)
“M3o” refers to the 3 letters in the middle, not the version number (similar to i18n or k8s)
Re:Micro 3.0 is a platform for cloud native development by asim on Tuesday November 10, 2020 @12:28PM (#25048489)
This is correct
Re:Micro 3.0 is a platform for cloud native development by bmelton on Tuesday November 10, 2020 @11:36AM (#25047855)
bdcravens is correct. m3o is a numeronym for 'micro' and does not relate to the version number.

The format of a numeronym is to take the first letter of a string (micro) + x + the last letter of the string, and replace x with the number of characters between both. So, Andreesen Horowitz (the most popular one I'm aware of) becomes a16z. Micro becomes m3o.