[crdoconnor]

True, but if you prematurely divide your services up based upon what you think their performance requirements might be you will be wrong. That's premature optimization, which is, as we all know, the root of all evil.

If you've loosely coupled your services until the point where it becomes obvious that two parts of the code have markedly different performance requirements and then you decide to split them into two separate services then yes, that could work, provided you understand the trade off you're making.

I don't think that's typically what people mean by 'microservices' however.

There's a good chance it'll still be wasted effort, too. Hardware is cheap. Developers are not. That applies to large businesses and small.

[mfjordvald]

I always saw the point of micro services as not having to figure out the scaling part yet.

If you focus on grouping by purpose rather than what resource they might use then you can keep them on small instances until you better understand what kind of resource they require.

Once you learn their usage pattern you can adapt more quickly (if scale is needed at all) and not have to first split up the code.