444 karma · joined October 7, 2016
For example, in Canada it is illegal to sell unenriched flour. Flour sold in Canada has to fortified with things like folic acid, riboflavin, and thiamine. Why? Because this helps contribute to Canada having one of the lowest birth defect and infant mortality rates in the world. This kind of thinking extends to regulations around food prep in restaurants, car safety, pharmaceuticals, etc...
Given the single payer health insurance that is pervasive in Canada, the government(s) are incentivized to ensure proper delivery of services and care as efficiently as possible.
Canada is far from nor will it ever be some libertarian hellhole.
Having their flagship code editor available for their OS regardless of platform from day one seems like a no brainer, but yet here we are.
Give this a try: https://www.digitalocean.com/community/tutorials/how-to-inst...
Each service having well scoped and defined RBAC or AuthZ for its focused set of features makes the whole architecture as a whole much easier to reason about from a security standpoint. I've done successful pen testing and auditing of some monoliths in my time where the critical security issues arose out of untested and unexpected execution paths that were only possible because the surface area is so large.
Maybe in theory a "well written" monolith would be superior but I'm only going but what I have seen in practice. I think the extra work is worth the trade off.
I remember when docker first came out and people were losing their minds about how they will be able to deploy their applications with all their dependencies in a single shippable bundle, kind of like an uber jar.
So much poor API design out there that most would be better off with server side rendering.
I was the technical lead on a project where I warned the product owner that implementing a certain feature the way they wanted in AWS would have astronomical costs. I was told "let me worry about the money".
A month later we were told to scale down our ECS and EMR usage as the bill was astronomical.
This is pretty much it. Google is fundamentally an advertisement company and that scares me.
Any place that can lay off a significant majority of a team has issues.
The presenter looked confused, and then the group asking the question clarified that their big data workflow involves loading millions and millions of records into excel and they would have trouble migrating to google cloud until google sheets could match excel in performance.
Somewhat unrelated story, but it shows how well loved some software is, and how some users will take it to use cases you never imagined.
Rest assured, this person is a mainlander washing money in Canada.
Working as a lead in a small team that deals with a colossal amount of data (human genomics), it was always easier for us to hand roll deployments with terraform/ansible in either baremetal or OpenStack environments.
In the public clouds like AWS we are using the managed services like EMR.
The whole sales pitch I've always got from either hortonworks or Cloudera always seemed more aimed at nontechnical stakeholders than the technical ones. Am I wrong? Have I missed out on some cool stuff?
This just makes it all the more confusing.
Atoms are much more nebulous than the concept of small indivisible balls of matter.