The point of a microservice based architecture is to allow a large team (15+ people) to work together without stepping on each others toes. The idea is you break the application into smaller services, and each service can be iterated on and deployed by a small group of 1 to 4 people. I cannot see any reason why it would be a good idea to adopt a microservice architecture for personal projects or for a startup with less than 10 people.
I did work on an application suite that included a blogging platform, that aimed for a service based architecture. We had services for:
* taking screenshots of the rendered blog post, for use in preview thumbnails
* user identity and settings (shared service for the entire suite)
* asynchronous task handling
* sending emails
* adding blog post analytics to the dashboard
* all things commenting (including a javascript embed code)
* the main application for editing and rendering the blog content
* customizing blocks of content based on visitor identity
I did work on an application suite that included a blogging platform, that aimed for a service based architecture. We had services for: * taking screenshots of the rendered blog post, for use in preview thumbnails * user identity and settings (shared service for the entire suite) * asynchronous task handling * sending emails * adding blog post analytics to the dashboard * all things commenting (including a javascript embed code) * the main application for editing and rendering the blog content * customizing blocks of content based on visitor identity