4 ms·

All valid questions. re: context chart and states. The y-axis mentions "adoption". Which is the market adoption of an item. If you click a state, I explain wha

All valid questions. re: context chart and states. The y-axis mentions "adoption". Which is the market adoption of an item. If you click a state, I explain what that state mean. I'm certain this can be improved. So for your example Heroku: Yes they could be growing, I'm not saying they aren't, but they've come into a state where their service is strongly challenged by competitors (usually left in the chart, AWS, Google Cloud). Re: PostgreSQL and Containers. Those are my opinion in this release. I would see state.of.dev evolve into expert/community consensus based on arguments and actual chart releases.

tokenizerrr 10y ago
Considering postgres is streets ahead of anything else on that graph (GraphQL isnt even a database just a query language, SQLite is of course amazing but useful in an entirely different context, mysql/mariadb lack many important features, and mongo...), please back your opinions up because as of right now this seems dishonest if not wrong.
mugsie 10y ago
Containers is still very much in growth, for the majority of deployments. VMs would be mature, and bare metal would challenged / superseded. Remember that 90% (a number that is completely take out of thin air, but a large majority) of deployments are not what we see on HN, lobsters etc. They don't understand why you would have a VM, let alone a container. I have seen feature requests recently for zero downtime migrations of containers, as "some apps cannot be stopped and started" - that is how enterprise sees containers.
- AstralStorm 10y ago
  Hate to break it to you, but for high performance only specialised hardware works. Sometimes even only local hardware. Or even a full cluster that only uses VMs or containers as a nice migration of availability layer. Internet bandwidth and latencies kill clouds while there is no real gain to be had by running multiple heavy compute services on one machine. (as much as certain gpgpu companies want you to believe) Bare metal superceded, ha. It is just augmented with an availability layer.

tokenizerrr 10y ago

Considering postgres is streets ahead of anything else on that graph (GraphQL isnt even a database just a query language, SQLite is of course amazing but useful in an entirely different context, mysql/mariadb lack many important features, and mongo...), please back your opinions up because as of right now this seems dishonest if not wrong.

mugsie 10y ago

Containers is still very much in growth, for the majority of deployments. VMs would be mature, and bare metal would challenged / superseded. Remember that 90% (a number that is completely take out of thin air, but a large majority) of deployments are not what we see on HN, lobsters etc. They don't understand why you would have a VM, let alone a container. I have seen feature requests recently for zero downtime migrations of containers, as "some apps cannot be stopped and started" - that is how enterprise sees containers.

AstralStorm 10y ago
Hate to break it to you, but for high performance only specialised hardware works. Sometimes even only local hardware. Or even a full cluster that only uses VMs or containers as a nice migration of availability layer. Internet bandwidth and latencies kill clouds while there is no real gain to be had by running multiple heavy compute services on one machine. (as much as certain gpgpu companies want you to believe) Bare metal superceded, ha. It is just augmented with an availability layer.