garethmcc

6 ms·

1.
by garethmcc 3y ago
The difference is that the model is based on usage not seats and revenue is going to be shared with builders of extensions used by users of the framework (80% of the revenue) to help grow the serverless ecosystem
2.
by garethmcc 4y ago
The "bankrupt your company with the wrong keystroke" is not entirely accurate. AWS does work with companies (or even individuals) if they genuinely made an error that wracked up a huge bill. Personally they have dropped bills of $
3.
by garethmcc 5y ago
I have watched almost all those talks as they are technically dense and full of very good and very useful technical knowledge that I would be much poorer for not watching. These are not sales videos but highly complex instructional content
4.
by garethmcc 5y ago
Have you looked at the recent crop of Serverless rechnologies that rtuly abstract away even considering the underlying hardware platforms. I am talking about tools such as Serverless Cloud where you write code and it infers the hardware nee
5.
by garethmcc 5y ago
I have worked with many teams and found lambda to be by far more cost effective. Did your calculations include the time lost waiting to deploy solutions while infrastructure gets spun up, the payment for staff or developers spending time pu
6.
by garethmcc 5y ago
This is where using a tool like the Serverless Framework helps solve a lot of these problems: - Use async/await promises instead and the specific plugin for the Serverless Framework for configuring your Step Functions makes it easy! -
7.
by garethmcc 5y ago
I agree somewhat, but its a little more nuanced. Right up front, you could absolutely get infrastructure setup yourself using things like EC2 etc that would eventually be cheaper when traffic gets high enough but there this does not take in
8.
by garethmcc 5y ago
FaaS has been remarkably good for many companies with very late stage products running with very large numbers of users for a very long time. The speed of development even in a mature product and the much lower maintenance overhead make Fa
9.
by garethmcc 5y ago
Non-relational databases match one of the largest use cases that exist; large volume OLTP workloads. Non-relational databases typically can handle far more load on reads and writes than relational databases due to their intrinsic distribute
10.
by garethmcc 5y ago
Not to mention that that same infrastructure you say is in abundance is usually pretty heavily utilised already so there isn't just spare capacity lying around. Procuring new hardware can take months and if there is no rack space you a
11.
by garethmcc 5y ago
Its not as simple as that. Just because its the case of "we have lots of old stuff" doesn't mean you need to ignore the new stuff. Building solutions with traditional data centers and staff, even if you have a lot of it, is
12.
by garethmcc 5y ago
This happened to me once and AWS entirely reversed the charges no questions asked. And its really something you don't need to worry about. AWS makes more than enough money off of legitimate traffic they don't need to deny someone
13.
by garethmcc 5y ago
Hi tdfirth. I am with the team at Serverless, Inc, creators of the Serverless Framework. I can totally understand the frustration, especially with new development architectures such as serverless. Over the years of building serverless appli
14.
by garethmcc 5y ago
Oh yes, and serverless is not just Lambda, its a about the whole suite of cloud services you combine together to build your solution.
15.
by garethmcc 5y ago
This is not entirely true. Firstly because Lambda keeps getting cheaper with the move from per 100ms billing to pwe 1ms being a big contributor. but also that I see organizations handling millions of requests per hour at peak but because of
16.
by garethmcc 6y ago
EC2 is a managed solution but you still need to manage servers.
17.
by garethmcc 6y ago
I am curious what made you unsatisfied. As a member of the Serverless team I'd love to hear the feedback so we can potentially improve the experience for you and others.
18.
by garethmcc 6y ago
Shipping value is important. If you can build a solution faster in a monolithic, MVC style framework running on EC2 instances, then do that. I think people get too bogged down in the minutiae up front and forget they are being paid to solve
19.
by garethmcc 6y ago
I have been building JAMstack apps since 2016 using exactly the stack you are asking about. Using something like the Serverless Framework to help you build and deploy your collection of microservice backends into AWS as well as your static
20.
by garethmcc 6y ago
I am not entirely sure this is correct. There are definitely ways to delete or update data.
21.
by garethmcc 6y ago
Serverless Framework. And you have some choices. You can use the serverless-express component to just get Express deployed into Lambda: https://github.com/serverless/components#serverlessyml Or you can use the original
22.
by garethmcc 6y ago
If you use a tool like the Serverless Framework, you can trigger Lambda functions off of many different events, includinmg a schedule: https://www.serverless.com/framework/docs/providers/aws/even...
23.
by garethmcc 6y ago
I just want to add in about version controlling Lambda code, this is entirely possible using the available tooling with something like the Serverless Framework at serverless.com
24.
by garethmcc 6y ago
Not entirely true. The largest use case we see for Lambda is as the compute service for an API backend provisioned with API Gateway (so a full application backend) with synchronous responses over HTTP (so rapid response provided within mill
25.
by garethmcc 6y ago
There are an enormous number of people using Lambda's as a part of very complex workloads including customer facing platforms. Your specific use case of 100 000 incoming requests in 20 seconds is actually far more extreme than most use
26.
by garethmcc 6y ago
If anyone is initially fooled by the naming that illusion is broken very quickly after just a few seconds of looking into it so I doubt that this was an intentional act to trick people
27.
by garethmcc 6y ago
Autoscaling is monstrously good on DynamoDB. You can turn on on demand mode so that it will scale up to the sheer limits of DynamoDB itself, but you pay per usage. So if you do want to set some kind of limit based on affordability you can s
28.
by garethmcc 6y ago
DynamoDB costs you nothing when its not in use. It only charges based on actual reads and writes performed. As opposed to a traditional Relational database that always has to be on and has to be scaled up vertically to the maximum anticipat
29.
by garethmcc 6y ago
You forget a few things: 1. AWS and other cloud vendors don't have just one data centre per region, they usually have three redundant locations for availability reasons connected via a direct fibre link. 2. Cost of time; time to find h
30.
by garethmcc 6y ago
There are organisations with 1000's of services on Serverless seeing enormous benefits in reduced management overhead and reduced costs compared to the Kubernetes solution they previously ran.

More ›