awssucs's comments

I believe your blind passion for the eu - a project i support - makes you blind to its flaws. Some of us in the eu are struggling with its incompetence and any criticism is quickly shut down as euro skepticism or misinformation. A dangerous path if we want the project to survive.

Oh really. A close look from someone experienced on most topics will reveal the opposite. Tech discussions at least are pretty shallow or mis informed and usually limited to a few recycled topics. Easy to appear clever in front of impressionable fresh graduates but most experts will immediately see through most comments. But hey whatever suits the echo chamber.

astra zeneca is 90% effective as there are two doses needed, much like pfizers

nah this is not reddit the quality here is lower

I agree nobody knew what the cloud was becoming. But it feels like aws is selling an unfinished product and people are wasting money and time working around non issues. Aws is great for medium sized projects but as soon as your project grows, you bump into silly issues like this one. Given that s3 is more or less a file storage you don’t really expect issues such as “weak” consistency. You expect a file to be committed once written (yes aws can do queueing behind the scenes) but when it returns a 200 ok it means the file was stored. Otherwise the good folks at aws should return a 202 accepted response as all properly designed apis do and let the user know that a delay in reading is expected.

yes for aws it was an issue, what i meant is that aws solved an issue that it itself created.

mmyeah never had this issue on non aws distributed storage. luckily for aws there are plenty of inexperienced devs who think this is a real issue in a properly designed large storage system.