HN user
I just implemented incident manager org wide :(
I knew the service was rough, but had the right building blocks plus Cfn/CDK support and has been working well.
My lack of trust in AWS is increasing, feels like a google move.
API gateway timeout increase has been nice.
Is this really xenophobia?
China does not provide equal access to their markets, why should we provide it to ours?
And the specifically pertains to a loophole that would be getting closed for everyone...
For anything we inject secrets in via env vars (which really is only supported by ECS, maybe EKS?), it is easy to add a lambda to kick off a nightly ECS restart. Easier if you are already using the AWS CDK for tooling.
The purist in me thinks restarts are a hack, but the pragmatist has been around long enough to embrace the simplicity.
Adding another dependency/moving piece that AWS could drop support or it could just break also steers me away from this.
For Lambda, processes should be getting swapped fast enough and you also normally load during a cold start only. I could see some argument there around improving cold start performance, but would need some testing.
So, maybe this is to save a few cents?
Agreed. I would imagine the previous approach of forced upgrades ended up burning lots of customers in worse ways than just their pocketbook.
Is above still an issue with http2/3?
edit: From the article: To workaround the limitation you have to use HTTP/2 or HTTP/3 with which the browser will only open a single connection per domain and then use multiplexing to run all data through a single connection.
As others have mentioned, moving to per tenant databases can really simplify things at scale and doesn't leave a massive amount of engineering complexity and debt in its wake.
I feel sorry for the team managing this 5 years from now.
Yes, GoDaddy does this.
If you want to leverage cheap spot, use us-east-2 / Ohio region. The prices are typically half of what you see in us-east-1.
Also, it really helps to analyze at the AZ level. Certain AZs lack instances or have very low spot availability and contrary to recommended best practice, reducing AZs can sometimes be beneficial (I am looking at you eu-central-1a).
While lowest price sounds nice, they can be really messy in terms of spot interruption rate. It is much better to set a max price and choose capacity optimized with as many instances as possible.
The automatic region thing is problematic for many companies.
I would much rather be able to explicitly choose this and know that customers data is where I told them it would be.
GoDaddy is really a dishonest company. Please do yourself a favor and avoid them. Things I've personally experienced:
* The purchase of webfaction w/ a promise to migrate sites to a new host. They promised for over a year to do this migration and then 30 days before shutdown told me they could not migrate and to figure it out.
* Domain name sniping. Never ever use godaddy to search to find a domain. They will just steal anything you search for if you don't immediately claim it.
There are lots of good reasons in that thread why the patch was declined.
The patch made things more lenient which makes things less compatible (this whole thread is about ANSI SQL standards and they do matter) and changes what was an error behavior to now silently succeed.
+1 to postgres devs for curating patches.
This is a very common pattern especially with the cdk. Having a locally deployed stack makes development in the cloud so much easier.
That is incorrect. Cross az fees are steep.
Kinesis data streams and firehouse were down. All but one out of 300 RDSs failed over. One was down for 5 hours.
So you are aware your dislike of Blackboard for reasons above are misplaced:
- TurnItIn is a 3rd party Blackboard extension and the school selected to use this.
- The school was also likely self hosting an under provisioned system.