Broadly speaking, a lot of the 'cloud native' stuff are complex solutions to potentially complex problems that fit within the parameters that those approaches can handle.
If you don't have those complex problems, then it's a premature optimization that is painful. If your use case is not the sort of use case resembling the bread and butter of the applications that instigated these approaches, then it's all pain, no gain.
There was a team that maintained a project that was broadly panned for not being good enough. The developers decided that the cure for what ails them would be changing to 'cloud native' approach, despite the complaints really being about limited functionality, not even about performance or scaling issues. Now on top of having the same functionality complaints *now* they have performance and reliability complaints too, and they have no idea what they are doing, they just arbitrarily carved their single fixed instance of software into a couple of dozen fixed instances of services (they can't figure out how to scale arbitrarily, so they still have exactly one instance of every component). Not one of them is capable of debugging the convoluted network situation they've created, and the logging information is just a mess.