not directly related to OP's question
but
api kohomada hadana software ekaka (eg: billing system of a pastry shop network like P&S, large system like food city cashiering system) REST API thiyena monolith or REST api Micro service yanawada da kiyala decide karanne?
I'm not
@NEMISIS 
but here's my 2 cents..
oya okkoma base wenne requirements, budgets anuwa thamai...mokada microservices kiyanne overhead ekak
specially uba hithapan uba oya kiyana category eke software ekak nam gahanne, ubata microservices dala waatha wenna wenawa...
implementation patta amarui,,(transactions track karana ekama amarui services godak athara) okata thiyenawa SAGA , CQRS wage ewa..owa implment karanna efftort eka wadii...

(effort eka wadi kiyane, time eka wadii == $$$ ),,
anith athin deployments walata ehema cost eka wadi..
godak un mama dakka microservices walin monolith walata maru wela thiyenawa cost eka save karaganna
ubata loku team ekak nattham, monolith walin start karana eka thamai hodama de..mokada eka atthatama fast..(habai drawbacks thiyenawa..deployments ehema kachal ithin,,
scaling prashna thiyenawa (hithapan, ubage thiyenawa billing service ekak, user service ekak ohoma kiyala,,,nattham order service ekak,,whatever,,,)
dan oya services walin, atthatama billing service ekata comparatively requests wadi wenna puluwan user service ekata wada...e welawata ubata e service eka witharak scale karanna puluwan,,,
but monolith ekak ehema karanna ba

( habai mehema ekak thiyenawa,,,ehema welawata ara okkoma monolith eke thiyenna arala, shape eke kalla kalla awashya welaawata microservice widihata gahanna puluwan..okata kiyanne microservice decomposition kiyala..)
microservices kiyanne kohomath ehema saralwa awata giyata karanna puluwan ekak nemei,,,hariyata study karala, hodata plan karala gahanna one
hope it helps!