It is harder to install fiber in densely populated areas than in some backcountry farm. Imagine tearing open a busy street in NYC for a few weeks to install fiber vs. digging a trench in the dirt next to the farm road. Which one do you think costs more? For which do you think you need to jump through 1001 bureaucratic hoops?
Hyperscalers buy so many CPUs and so much RAM they can dictate prices (to a point) or at least make an agreement to buy at a much lower price but buy X amount for the next 5 years.
Hi, sorry I'm late to respond. The price was something like this:
150€ Hoymiles HMS-800W-2t
300€ 4 Trina Solar 445W Full Black panels
100€ Shelly Pro 3em (not necessary but I wanted to see how much we feed in)
The rest was construction materials and small stuff. We have mounted it on our roof, 900W East, 900W West. One east and one west panel are wired in parallel and connected to one MPPT of the HMS-800W. We're producing around 1.3MWh per year.
I live in Germany, installed a micro solar system in September 2024. Since then, we've been producing 45% of our electricity consumption ourselves. This has saved us 550€, while the initial cost was around 800€. So this September, after 2 years, the system will have paid for itself.
Why would I ever want to book a course with someone who just realized weeks ago they don't know if the code does what they want if they don't look at it?
You're right, I didn't pay attention there. Still seems that there a many solutions better suited than S3. Probably a classic case of "We need an MVP fast, let's optimize later".
Exactly, my first thought was "Why in earth would anyone think that S3 was the right service to store millions of tiny ephemeral files?" and now it seems they have invented their own in-memory store instead of just using something like Redis. I also wonder what happens if their DIY thingy crashes, are the videos lost? Why not send to Kinesis or SQS in the first place?
I think technology choices should be made depending on the team. If you have 5 teams with 10 people each, then it is a great idea if your service is comprised of 5 microservices that talk to each other across team borders through well defined APIs. If it takes you 3 days to run your microservice locally, then you somehow didn't set up your development environment when you should have.