Comment Re: Opinion (Score 1) 288
Wow, show me on the doll where the microservice hurt you...
If you put the country data into a database table, and you at least separate your database servers from your application servers, then you will require a network call to the database server to get the data. If you put it on a file in a volume, its probably network attached storage and again... a network call. The only way that is prevented is by hardcoding the data or deploying it as part of your app resources, which comes with its own set of issues I wont get into.
Your criticism of excessive network utilization and resource wastefulness is equally applicable to other architectures as well. Regardless this problem I would argue is MORE solvable in a microservice architecture in that containerized services more efficiently utilize the infrastructure resources made available to the container hosting platform. It is vastly more scalable to meet system resource needs and is more efficient at that capability. To take it further for seldom updating reference data like Countries for instance, things like Redis caching make all of this a moot point anyway.
The bottom line is that if your example you provided is based on a true story, then I would argue there are more pressing problems in your design than whether or not microservices are used or not.