mulmboy

There's a channel called GameHut on youtube that has some really interesting videos, eg https://www.youtube.com/watch?v=gRzKAe9UtoU

A pattern I have implemented is to have my API code on both ECS/Fargate and Lambda at the same time, and send traffic to the appropriate one using an Elastic Load Balancer. I flag specific endpoints as "cpu intensive" and have them run on lambda.

Implemented by

- Duplicating all routes in the API with the "/sls/" prefix (this is a couple of lines in FastAPI)

- Setting up a rule in ELB to route to Lambda if the route starts with /sls, or to ECS otherwise.

- Set up the CPU intensive routes to automatically respond with a 307 to the same route but prefixed with /sls.

Boom, with that the system can handle bursts of CPU intensive traffic (e.g. data exports) while remaining responsive to the simple 99% of requests all on one vCPU.

And the same dockerfile, with just a tiny change, can be used both in ECS and Lambda.

AWS CDK makes this much easier - including automatically invalidating the cloudfront distribution https://docs.aws.amazon.com/cdk/api/latest/docs/@aws-cdk_aws...

Smaller Discord servers are close

Cheers for the history lesson - True and False really are relatively new in Python. I wonder how common that knowledge is.

http://python-history.blogspot.com/2013/11/the-history-of-bo...

https://www.python.org/dev/peps/pep-0285/

I can't point you to an existing one. However I'm confident I could put this together in a day.

Do you think it would be difficult? Github actions can be boiled down to running shell commands (with a bunch of other handy features), so it's quite versatile. At times it does require you to make workflows which are a bit convoluted but all in all I think it's pretty good.

As someone who's about to assist a frontend team to implement testing against a backend I've developed (my first time doing something like this), I can see that mocking backend APIs is inherently tedious and error-prone. And I'm not confident that we have the resources to keep the mocked endpoints consistent with the real backend given the pressure to develop the "real product".

What are the downsides of of using a real API (e.g. dev environment) for automated testing?

Computers are not joy boxes for a lot of people, or at least not joy boxes with any depth.

The trendlines made me physically recoil. Please, just leave them out if they're useless.

How does Maat compare with pydantic? https://github.com/samuelcolvin/pydantic

> You'd just reach a path that has not been implemented yet, break, implement it and continue.

This is exactly what I do with the PyCharm - hit a breakpoint, write the code as it should be, and execute it in the debug REPL to do basic initial testing [repeat]. Extremely productive.

Will that not lead to bloat and/or more deprecation of services in the future?

I suppose you can tell people "hey this service shouldn't be relied on! We might get rid of it one day!". But that erodes trust - people just don't fully internalise what that means, they expect the same level of long term support from all AWS services. Soon the common sentiment will turn into "AWS changes its services all the time" when the truth is "AWS changes the services marked as experimental all the time".

AWS has established itself as being highly backwards compatible - and the cost of that seems to be the long-winded process you described. If they were more liberal with what features they implement then they would have to either be more liberal with what features they deprecate (removing a core value proposition of AWS: backwards compatibility) or they would have to suck it up and deal with the bloat which would naturally lead to higher cost and overall slower delivery of new services.

For a counter example see GCP. One of the biggest barriers to entry is trust: no one wants to use it because they don't trust Google to not arbitrarily yeet features out the window with six months notice. Whether or not that's actually what GCP does, it's how people perceive Google.

I'll take AWS's approach for things that I work on professionally and have to support for many years.

Why use this over something like sphinx[1], which has quite a rich and established ecosystem? Combine with Furo[2] and it even looks quite similar.

[1] https://github.com/sphinx-doc/sphinx

[2] https://github.com/pradyunsg/furo

yeah that's what I mean - that Cinder precipitated the open sourcing of Pyston.

Hard to argue this wasn't precipitated by Instagram's Cinder - nice to see it smoking others out already.

yeah - you shift the risk from the retailer onto the consumer. Usually these deals will have some kind of faux-insurance arrangement baked in where the consumer will never have to pay more than something like $300/MWh

Yeah you're right. But, tracking solar (and solar with fixed positioning that maximises energy output later in the day) largely applies for more sophisticated sites such as commercial and industrial. I've seen such setups that forego around 20% of solar energy production to maximise production during more expensive time of use windows (including offsetting time of use demand charges).

Residential installations are usually setup to maximise the total output, and often the positioning is constrained by the geometry of the roof. Residential solar installers are really in a race to the bottom.

One up and coming trend which might have a significant impact on this is for residential retail tariffs to be directly linked, at 30min resolution, to the wholesale energy market prices.

Peak solar production during the middlish periods of the day in summer. Peak demand (if your grid is summer peaking - some peak in winter) is likely in the afternoon when people get home, right as solar output starts to taper off. It all varies a bit by culture and climate, but I think this is largely true.

The post didn't describe net metering

edit: actually I think it did :) ignore me

Yeah that can be done with BrowserFS - probably among other ways https://github.com/pyodide/pyodide/issues/613

This runs super well for me. Looking at chrome developer tools it's sending out a new frame request about every 38ms. Runs much nicer than the top two google results for "play doom online".

Trying to suss out the damage but getting 502. Begs the question of who's deploying static sites not behind a CDN? Assuming this site is static

Plenty of people live on the wage from waiting tables or walking dogs. Of course it's possible for you - it's just a lifestyle change.