In cloud-native architectures, which service model do you prefer?

07 Tem 12:33

For medium to large-scale Android and mobile app projects, I've found that **combining microservices with containerization** works best out of the three options. Serverless is great for small-scale projects, but in the long run, a setup with containers + microservices feels more flexible for testing, monitoring, and cost control. Especially when you can split different components like databases, caching, and third-party APIs into separate services. In one of our dating app projects, we initially used Serverless, but as the user base grew, it became expensive and slow. That’s when we shifted to microservices with Kubernetes + Docker. One major advantage was that three different teams could work on different features without stepping on each other’s toes—Team A focused solely on the notification service while Team B handled payments. That’s exactly what we needed, and it’s what a cloud-native architecture provides.