But if API Gateway or Cognito fails, I'll probably have a bigger problem than a tooltip that does not work. However, the tooltip will be cached, so if you loaded it once, it'll work even if API Gateway fails.
The AI part is used to generate tooltips, not to display them, so if it fails, I'll not be able to create new tooltips, or users will temporarily be unable to interact with them (ask sub-questions).
On Day 25, we connects the Create Tooltip flow by writing React code and an AppSync Lambda resolver with some help from CofounderGPT and Github Copilot.
VideoPuppet is excellent. I am using it to create videos for the Five Minutes Serverless Youtube channel, and so far, results are outstanding. I can create a video from the markdown file really fast.
I am not worried about A at all. This was a technical article, but here's the explanation I posted to twitter:
Although I enjoy talking about technology, and I enjoy working with serverless, it's important to note that using serverless for @slackvacation is not a technology decision. It's a business decision. Not because the auto -scaling, that's nice to have, but that's not a problem startups are facing in their early phase. It's about financial incentives — also, about focus, ability to move fast and test ideas, and the ability to grow without shooting future self into the foot.
We still often fail to do things fast enough, but we are aware of the problem and working hard to fix it.
It sounds like part of your decision was that Lambda comes out cheaper for hosting. That also doesn't pass the arithmetic I use to evaluate such things.
A dev, fully loaded, will cost you $200/hour. A half cage at a colo with a really fast machine in it will cost $800/month. So if you choose a stack that adds 4 hours of work each month (or 80 extra hours upfront), you're behind.
Given that (as I touched on above), your chances of outgrowing a beefy box in a colo (or its managed equivalent) can be thought of as zero until you see the big success event that proves otherwise, my money is still on boring tech and boring hosting.
Granted, Lambda is cool. I love building stuff on it for other people on their dime. But as a guy who also builds businesses on my dime, it remains a tool for tiny niche cases that can safely go down on a saturday morning without making me cancel my weekend.
Lambda I guess would be like using the coffee pot in a hotel room? Don't worry about power, don't worry about beans. Every time you come into your room it's ready to go, just press "on".
the point of serverless is that everything is much simpler, it is just functions! it is more a question of how early do you break even on ROI in simplicity, and maybe that isn’t in the first 6 months of a startup’s life yet. But in the future the break even point may be zero minutes.
Serverless architecture improves the way we build software. But it’s much more than just development, because it can improve the way we are building our products in general.
With serverless, your developers can focus on the business logic implementation, instead spending a lot of time on setting up and maintaining infrastructure. It also decreases the cost of your application, because it converts capital to operating expenses. Besides that, having smaller services allows you to implement changes and A/B tests easier, and to pivot faster.
With all the benefits mentioned above, serverless becomes more than the architecture choice, it becomes an important strategy. For example, it can allow you to charge teams per active user, without having to be a big company, such as Slack.
Well, I spent a few months writing a book about serverless, so we have slightly different opinion about serverless haha :)
I like this explanation why serverless looks promising: https://youtu.be/SPsaqiegOP4. I recommend full video, but those few minutes are the important part.
Personally, serverless helps me to build reliable software faster, and it minimizes the amount of time I need to spend setting up the infrastructure. For me it already changed the things big way. It'll not work the same way for everybody, which is fine and expected.
Serverless is more than a cloud computing execution model. It changes the way we plan, build, and deploy apps. But it also changes the way we test our apps.
Serverless can also change the way we test our non-serverless apps. For example, UI testing or load testing.
