HN user

earless1

488 karma
Posts0
Comments111
View on HN
No posts found.
An Update on Heroku 6 months ago

From a business perspective, this means they will not be investing in innovation on the platform anymore. Instead, they will focus their efforts on maintaining the current operations and keeping the lights on.

In the situations you mentioned, it doesn't seem the end goal is to be 100% correct about things. Approaching these situations with a curious mindset is key. You may be able to provide a set of options that encompass your understanding of the thing being asked without pinning yourself down to a specific outcome. Once you've allowed folks to understand the potential options, you can tell them you can get back to them with specifics and understanding of implications.

The pattern also puts an additional burden on the database. Therefore, we should consider the potential performance hit on the database

Massive understatement, one of the downsides that we've found with this pattern is the increase increase in binlog size for our database replication topology. One must be very careful with this pattern as to not create downstream issues with replication delay and such.

If taking advantage of this pattern in MySQL land, you should look into filtered replication to avoid this outbox table from being copied to every single replica. https://dev.mysql.com/doc/refman/5.7/en/change-replication-f...

The watch deactivates most features and locks as soon as you take it off of your wrist. You'd need to re-enter your password to unlock it. so it is unlikely that throwing it would trigger the feature.

Also from their initial demo, the fall detection uses more input than just a fast falling motion. Apparently humans fall in a specific way that the watch detects

This is a space that I am deeply interested in, but my team have not found a good pattern around this for MySQL. We currently use a combination of MySQL Slap and Jmeter, but we feel like there are better ways to do this.

Anyone have nice patterns for this around MySQL?

I don't really see a benefit in updating existing instances in this manner. Launching replacement instances with the new code is much easier for us, and it also provides a super fast means of rollback.

In the past I've thought about using the an ec2-meta-data style endpoint for secrets that would accessible by an agent with some sort of key. that way the application always dynamically requests the secret as oppose to setting it statically at launch.

The FCC seemed extremely responsive and considerate back then. I wonder how long things would have taken now-a-days to get consensus and authorizations

The xkcd survey 11 years ago

You must accept that you will sound like a fool just for using this word. You can use it for anything you want to show satisfaction/approval for. React.js on fleek, eyebrows on fleek, uptime on fleek

With web projects there exists the potential to reach many more users than desktop and native projects. I would assume that the percentage of the population with access to a web browser is much much larger than any other segment.