911 karma · joined January 13, 2020
I see what you are getting at though.
The truth is that micro services are a tool. However your organization has broadly agreed to utilize the tool is the correct approach.
It wasn’t just optional but other areas as well.
There were a lot of other slow areas as well, not where you would expect it.
The startup time is also a real problem, as you really want to be able to scale up pods quickly.
That said, it’s good enough right now. You can make it work at scale, and it’s worth the cost trade off of trying to do it more efficiently in a different language.
I would be curious to see how a rust microservice would compare in my companies infrastructure. How much cloud saving could we squeeze?
Homer jay simpson
742 Evergreen terrace, Springfield.
The only problem is I don’t know the state.
I think you learn to bear the load more gracefullly as you age and mature. It also puts life more into perspective.
My main point is you learn to handle it, which is actually a good form of personal growth.
1) people who migrate to larger cities are exposed to more crime
2) not many people from the 1950s around that can really compare accurately
For instance, crime may be decreasing, but it could be increasing where there are more people, meaning more people think crime is increasing. I’m not sure if that is true or not, but I feel like it is with perceptions of the economy.
Maybe the data doesn’t tell the whole story or is being carefully curated. We probably shouldn’t try to piece together micro trends with coarse macro level statistics, as there is no guarantee that the macro effect is happening at the micro level.
I am well versed in all three areas, but obviously I can’t remember all the syntax, and don’t have time to trial and error the changes, and ai reduces that loop. I don’t use it to generate massive blocks of code, I use it mostly to demonstrate the principle of what I am trying to achieve.
I have many specific examples of massive time save.