southpolesteve

6 ms·

1.
by southpolesteve 2y ago
I worked on this project in college and went to the South Pole in 2009. Happy to see it is still making discoveries!
2.
Angular and Wiz Are Merging(twitter.com)
5 points by southpolesteve 3y ago|3 comments
3.
by southpolesteve 6y ago
Please do!
4.
by southpolesteve 7y ago
Azure Cosmos DB does. There is a good video about it: https://www.youtube.com/watch?v=kYX6UrY_ooA
5.
by southpolesteve 8y ago
I worked on this project in college and went down to the south pole after graduation to help install some of the detectors. Neat to see the results! ~10 years later.
6.
by southpolesteve 8y ago
Yes. bustle.com, romper.com, and elitedaily.com are all 100% serverless and do 80+ million unique visitors per month. GraphQL+AWS Lambda
7.
by southpolesteve 8y ago
More specifically React https://developer.microsoft.com/en-us/fabric
8.
by southpolesteve 9y ago
I also find `this` is terrible for linting. Most tools won't be able to figure you what you attached to `this` at runtime. It's a grab bag object ripe for bugs.
9.
Amazon is Terrifying(medium.com)
3 points by southpolesteve 9y ago|3 comments
10.
by southpolesteve 9y ago
Very straightforward. We send text, they send back categories. We then map those to IAB categories in our own code
11.
by southpolesteve 9y ago
The mapping is custom. Not something they have out of the box.
12.
by southpolesteve 9y ago
I see this comment a lot. The issues are the same with any REST API. Often they have been solved many times by the community or are baked into whatever backend framework you happen to be using. GraphQL (and community) are still converging o
13.
by southpolesteve 9y ago
Yes. We use the Natural Language Understanding service at www.bustle.com for doing categorization of content. It maps decently to IAB categories: https://www.iab.com/guidelines/iab-quality-assurance-guideli...
14.
by southpolesteve 9y ago
Martin Fowler's serverless post was written by Mike Roberts. It is just hosted on Martin's blog.
15.
by southpolesteve 9y ago
The place you linked in Philly is a few blocks from my house. I've been a handful of times. Much more of a restaurant. I think it is a good example of a place trying to do too many things. As a coffee shop it is pretty sub par. It does
16.
by southpolesteve 9y ago
We haven't seen any issues. Most of our latency critical functions are called a lot. We do get significant spikes in traffic but our CDN does handle some of that load.
17.
by southpolesteve 9y ago
API Gateway needs less config since they released the proxy style integration. In Lambda's case this means you can just return a JSON object like: { "statusCode": 200, headers: {}, body: "<h1>Hello!</h1>
18.
by southpolesteve 9y ago
If you go to www.bustle.com or www.romper.com you get a JS app server side rendered by AWS Lambda and delivered through API Gateway (CDN in front of that). We do 50+ million unique visitors a month. Our team is super happy with the result a
19.
by southpolesteve 9y ago
In graphQL they are called mutations http://graphql.org/graphql-js/mutations-and-input-types/
20.
by southpolesteve 9y ago
You are definitely not wrong. In our case the benefits have far outweighed the harshness from the bleeding edge. But for sure we have had to do a thing or two that I would rather not. Adding auth into graphQL, extending built in type classe
21.
by southpolesteve 9y ago
Reading the article, I come to the opposite conclusion. Of course I need GraphQL! I want these problems solved out of the box. I want to build on the shoulders of smart people who already solved them. APIs are contracts. As a method of expr
22.
by southpolesteve 10y ago
Mostly it is not a big problem for us. Our functions that need to be fast have very high traffic. Our other functions don't need to be that fast. We also have a CDN in front of most things. That said, we use node. I have heard cold sta
23.
by southpolesteve 10y ago
We use Lambda and API gateway for all production[1] requests. HTML, Server side rendered JS, API calls. All through lambda. There are some rough edges. We wrote our own framework/deployment tool[2] to fix some of them. AWS has been mak
24.
by southpolesteve 10y ago
Thanks!
25.
by southpolesteve 10y ago
Congrats on the raise, but I'll be honest it really rubs me the wrong way that they renamed to "Serverless Framework" from JAWS. They should have picked a different name. The word "Serverless", for better or worse,
26.
by southpolesteve 10y ago
I'm not sure why this myth persists. We've found Lambda + API Gateway to be an awesome solution for serving front end applications with server side rendering.
27.
The Overwhelming Web(50linesofco.de)
5 points by southpolesteve 10y ago|0 comments
28.
by southpolesteve 10y ago
thanks for doing the math for me :)
29.
by southpolesteve 10y ago
Define horrific. The traffic that generates those calls also generates lots of revenue :) It is also extremely spikey. This is a big win for Lambda since we are only pay for what we need and don't have to worry about scaling EC2 up and
30.
by southpolesteve 10y ago
I can empathize with the OP. Using Lambda in production still has some pretty rough edges. You basically have to use one of the deployment tools/frameworks out there[1]. There are also just certain things it won't do (someone else

More ›