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 :)
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!
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.
Good luck Asim, the project is kick ass!
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.
Are there any examples of how the repository/database layer fits here?
What'll happen to the name m3o when Micro reaches 4.0?