Arghh the biggest issue in current place (I be leaving before year end) is the amount of "engineers" who are pathologically afraid of relational database.
You have dozens microservices per teams, split between k8s, meso, aws, azure, physical servers each on using everything under the moon to store data up to storing files in s3
Needless to say the amount of issues due to data inconsistencies is incredible. And of course the amount of actual users of the overall product is tiny being an enterprise products, maybe few thousand concurrent users at peak.
They now want regional replication and screwed due to so many sources of data. Where postgres alone would have done
If k8s was being designed from ground up I would want a move away from yaml for configuration to a strongly typed DSL, something like gradle doing with move to Kotlin DSL from weak groovy DSL.
This would mean better integration/autocomplete in editors and no time wasted on silly things like number of indents being wrong.
This looks very good well done! Microsoft need to hire you for the team asap!
It always cracks me up playing minecraft on xbox one x and once your village hits few hundred villagers framerate (when running beta from insider it's shown on screen) drops to like 3-4fps
You have dozens microservices per teams, split between k8s, meso, aws, azure, physical servers each on using everything under the moon to store data up to storing files in s3
Needless to say the amount of issues due to data inconsistencies is incredible. And of course the amount of actual users of the overall product is tiny being an enterprise products, maybe few thousand concurrent users at peak.
They now want regional replication and screwed due to so many sources of data. Where postgres alone would have done