Status page seems updated now.

I’m fairly confident they usually raise prices through new generations of compute instances.

It's actually the opposite! To pick a representative example

    Current generation:
    m6i.large: $0.0960
    m6a.large: $0.0864
    m6g.large: $0.0770


    Previous generations:
    m5.large:  $0.0960
    m4.large:  $0.1000
    m3.large:  $0.1330
    m1.large:  $0.1750

https://rbranson.medium.com/rds-pricing-has-more-than-double... is a good example of using the generation abstraction to improve margins. Obviously, this source is not a price increase. It’s just increase in premium over EC2.

https://redmonk.com/rstephens/2021/12/17/iaas-pricing-2021/ Is also great and shows a flatness in price

They also don't discontinue any service as long as at least 1 customer* uses it. Which means: you will have the old (in your opinion probably lower) price forever, as long as you don't upgrade.

That's a very important distinction: increasing prices for users who can't go away and increased prices for users which migrate on their own to the new pricing structure. As far as I know, Google does the former which always has a "fader Beigeschmack" (DE; dulm aftertaste?) IMHO.

* = whatever that means :)

"We are reaching out to inform you that we will be retiring EC2-Classic on August 15, 2022. This message contains important information about the retirement and steps to take before the retirement date

How does this impact you? Your AWS account currently has EC2-Classic enabled for EU-WEST-1 Region"..

To be fair, "EC2-Classic is a flat network that we launched with EC2 in the summer of 2006", so I'm not complaining, but thought it was an interesting counterpoint.

I thought that at the time I got that notification.

But it turns out I don't have any EC2-Classic instances, and was really just a notification I wouldn't be able to create new one.

The GP said “ They also don't discontinue any service as long as at least 1 customer* uses it.”

The person you are replying to gave the counterpoint that AWS is discontinuing a service that the person is currently using.

This seems like a valid counterpoint to me.

As anecdata I was an early user of a product called SimpleDB. Long after the product disappeared from their website my application still worked. I didn't like the early version of Dynamo enough to switch. I don't remember what happened, this was 12+ years ago now since I wrote it

That's a very important distinction: increasing prices for users who can't go away [as an example of something Amazon doesn't do]

That's an important note for Glacier, where a significant price increase could lead to a situation of "You can pay punitive rates for retrieval of all the data to migrate it or you can pay us a higher price every month going forward."

That's like saying Apple raises the prices of the iPhone through new generation of iPhone models, which is not true at all. If the same service gets a higher price, then it's a praise raise. If a new service gets a higher price, it's just a new service.

> That's like saying Apple raises the prices of the iPhone through new generation of iPhone models, which is not true at all. If the same service gets a higher price, then it's a praise raise. If a new service gets a higher price, it's just a new service.

I don't think the distinction is that clear: you could just rebrand an existing service and raise the price. "Try our new v2 APIs, guaranteed compatibility with our v1 API and only 10% more expensive!"

I think the reality is somewhere in between, where companies will use new product launches to add stuff for customers and raise prices to protect their margin.

> That's like saying Apple raises the prices of the iPhone through new generation of iPhone models, which is not true at all.

I don't know if I'm reading your comment right, but the average selling price of iPhones has been climbing steadily from the start.

Apple margins are pretty consistent.

Assuming the assumption that intergenerational go up is true, in general compute only gets cheaper over time, so escalating prices implies increasing margin.

Target Retirement Funds sometimes hold non-ideal amount of cash. Also, make sure you are holding these in a tax-advantaged account https://401kspecialistmag.com/target-date-fund-providers-inv....

I don’t quite understand the issue. Is there an ELI5 explanation?

They do have HoloLens though.

Detailed read from two contributors on the project- https://www.ibm.com/cloud/blog/database-deep-dives-janusgrap...

Kinda blocked on the compatibility front after the 4.0 API though, eh?

Not if the recent Oracle vs Google supreme court ruling is to be acknowledged.

DocumentDB is to MongoDB 4.0+ as Dalvik runtime was to JVM.

Here is their 4.0 compatibility update: https://docs.aws.amazon.com/documentdb/latest/developerguide...

Time will tell...MongoDB 4.2 APIs are under SSPL

"Amazon DocumentDB implements the Apache 2.0 open source MongoDB 3.6 and 4.0 APIs by emulating the responses that a MongoDB client expects from a MongoDB server, allowing you to use your existing MongoDB drivers and tools with Amazon DocumentDB."

https://aws.amazon.com/documentdb/

IANAL

Good link, thanks. I don't think there's a equivalent response from the FSF, perhaps it was never submitted for FSF approval.

I have the bike+ and the automatic resistance is great. Unfortunately only available for on-demand classes.

just click the lock button on the workout resistance (can't be live workout)

Look up Chaossearch. They do this.

Oh yeah, I forgot about them. Thanks for the pointer! Still looking for something OSS though :/

Fair enough. They are the closest I know outside of ultra warm from AWS.

ChaosSearch is pretty rad, but it lacks some aggregation and integration support vs vanilla Elastic (last I checked).

Elastic is in beta with its own warm, cold, and frozen data tier system, including "Searchable Snapshots" that work with plain object stores to provide a seamless query experience with lower costs for large volumes of data: https://www.elastic.co/blog/introducing-elasticsearch-search...