top | item 43371103 (no title) quinnirill | 11 months ago Having teams is exactly the wrong reason to have micro services, having endpoints with different traffic patterns and resource/scaling constraints is exactly the correct reason. discuss order hn newest brewmarche|11 months ago Do you really need to jump to micro services when you need scaling? You can also start multiple instances of monoliths/bigger services. quinnirill|11 months ago If all the endpoints share the same resource constraints and traffic patterns, sure you can just scale up the monolith.Even otherwise, yes, you sure still can, just like you can write the service in bash if that’s how you want to spend money.
brewmarche|11 months ago Do you really need to jump to micro services when you need scaling? You can also start multiple instances of monoliths/bigger services. quinnirill|11 months ago If all the endpoints share the same resource constraints and traffic patterns, sure you can just scale up the monolith.Even otherwise, yes, you sure still can, just like you can write the service in bash if that’s how you want to spend money.
quinnirill|11 months ago If all the endpoints share the same resource constraints and traffic patterns, sure you can just scale up the monolith.Even otherwise, yes, you sure still can, just like you can write the service in bash if that’s how you want to spend money.
brewmarche|11 months ago
quinnirill|11 months ago
Even otherwise, yes, you sure still can, just like you can write the service in bash if that’s how you want to spend money.