Issues we had in our adopting it: I like the term "nano services" is it probably the wrong term. But I like it. We went monolith -> micro services -> micro se

Issues we had in our adopting it: I like the term "nano services" is it probably the wrong term. But I like it. We went monolith -> micro services -> micro services + nano services Everything that adds complexity in a micro service system, adds far more complexity with nano services. Debugging and tracing is a nightmare. And yes, logging, a lot of logging and instrumentation helps. But if you add too much of it then the whole point of the nano services is lost. Versioning can get complex, depending on your deploy model. Presumably if you push 100% of your nano services with every deploy you can get around it. We have about 600 nanoservices running on AWS now across 4 different systems. My advice, that nobody would ever ask for, keep AWS Lambda for certain special tasks where they are a very good fit. As always run the numbers, performance, cost to run, cost to maintain. Will the immense ability to scale really help your use case? In most of our cases, no, they will not. For some companies it will be a great solution and solve pain-points, save money