Otherwise you might consider doing the same with CDK. As a last resort you can use CloudFormation's new import/export tools and manage the stacks with SAM.
It's really too bad, I'm sure a more reasonable pricing scheme (framework only?) would lead to more adoption, but I'm sure that revenue had been a huge challenge lately and it seems like that means it's the end of the road for the Serverless Framework until v3 is forked.
I write about cloud minutia and generally focus on serverless. I try to focus on reproducible benchmarks and actionable advice. If you've wondered about the performance of AWS-SDK v2 or v3 in NodeJS, or weird edge case behaviors anywhere from Lambda to zip files, you may be interested.
It's typically fine - AWS bills by GB/s (in ms), not by number of functions in an account.
There are limits to the number of functions per account, and number of resources per CloudFormation stack (etc); but within those parameters it's usually a good idea to use one function for a specific controller or action. This allows you to limit IAM permissions, configure memory/CPU, and define associated resources at a per-controller level.
After spending a decade living and biking around Minneapolis, I recently moved to Boston.
The comparison of bicycle infrastructure (and number of people cycling) is stark. Given how bad the vehicle traffic is in Boston, I expected lots of bike commuters.
But there's no cohesive bicycle infrastructure here. Protected lanes barely exist, and even when they do, they suddenly end - leaving you on the side of a busy road.
It’s really problematic. Next door Cambridge is devolving into civil war over bike lanes on Mass Ave. The trouble is that to put in the bike lanes something else has to give. What’s giving is parking spaces which the merchants consider essential to their livelihood. Every time this comes up on Nextdoor it becomes a shouting match. Personally, I stick to riding on the Minuteman. My calculation of the risk reward ratio isn’t good enough to justify riding on the streets.
Ironically if you had better bike infrastructure you wouldn't need all the parking.
The MBTA bus redesign ought to help too.
But there is no reason why downtown dense city areas should be so car-dependent. It's not like people will stop going to shops along Mass Ave if they can't drive there!
What's worse is that even in surrounding suburbs, which have wide roads, the bike infrastructure is basically nonexistent, and car traffic is correspondingly horrible.
Not to mention the economic benefits to small businesses of having downtown bike infrastructure. Imagine how places like Malden would benefit (especially since there is already a bike path there).
It's a case of the relatively spread out development pattern and associated wide rights of way being advantageous. Minneapolis can tack on fairly substantial bike infrastructure without totally screwing over cars, which would be just as politically difficult in Minneapolis as any other American city.
The Grand Rounds help a lot too. It's a great basis to have inherited from the past.
Not a Boston resident, but have some friends up there who say that there are great bike paths for urban ingress/egress, but not particularly good for intra-urban travel. Does that match your experience?
I've put on about 200 miles since moving to Boston, and that observation does not align with my experience at all.
So far I've ridden one very good path connecting a few suburbs to Boston (Minuteman Bike Trail, a rails to trails path). There are other paths, but they're combined with running/walking trails and generally not conducive to bicycle travel.
The bike lanes of nearby Somerville and Cambridge are okay, but still lacking in comparison with Minneapolis.
I think my friends were riding along the Charles River, for what it's worth. They're more occasional bike commuters (once or twice per week) than a real serious bunch, and I don't know their start/end points.
Rail-to-trail appears to be how most longish (10 mile +) bike paths come into existence in the northeast, from my observations. There's a lot less "free space" to work with than other parts of the country, since the land is so developed / dominated by automobiles.
I used to commute on the Charles River bike paths and esplanade. It is actually pretty great for commuting from the Allston and Harvard areas downtown, but that experience doesn't generalize to other routes around the city. And the last half mile or so to get to your actual office can be pretty perilous.
- Serverless Framework. Write 5 lines of YAML and have an API endpoint that scales to infinity and back to zero. Still blows my mind. (I am biased though)
- Fullstory/real user monitoring/session replay tools. Such a clear way to see what someone was doing when they ran into a bug.
> - Serverless Framework. Write 5 lines of YAML and have an API endpoint that scales to infinity and back to zero. Still blows my mind. (I am biased though)
If you're actually pitching your own product as "scaling to infinity" and you're doing that to developers, I'd suggest to scale back on the exaggeration a bit.
I'm speaking specifically to the question asked - the first time I saw a demo. I worked there after it already existed, and am no longer employed there.
hey Aaron! yeah Serverless has a great demo for sure. very fast move by Austen to spot and grab that opportunity as fast as he did, feels like someone wouldve figured it out eventually.
i feel like this is a list of "products that demo well". obviously a nice advantage but am also looking for "great demos of products that would have been hard to demo", if that jogs any ideas
and dont feel constrained to just demos, sometimes a verbal pitch alone is enough to give someone the mind virus
SST has a good guide for migration: https://docs.sst.dev/migrating/serverless-framework
Otherwise you might consider doing the same with CDK. As a last resort you can use CloudFormation's new import/export tools and manage the stacks with SAM.
It's really too bad, I'm sure a more reasonable pricing scheme (framework only?) would lead to more adoption, but I'm sure that revenue had been a huge challenge lately and it seems like that means it's the end of the road for the Serverless Framework until v3 is forked.
(disclosure: I worked there for a while)