tirumaraiselvan

14 ms·

91.
by tirumaraiselvan 8y ago
Yes. So in serverless, there is no concept of a long running service. So you can't listen on port 3000 and have any routing within the app. You will rather write one function, add a route to it via API Gateway and then use it in your a
92.
by tirumaraiselvan 8y ago
Except in that case, the user already received confirmation that T1 was success before T2 was even executed. So not sure how that is even possible.
93.
by tirumaraiselvan 8y ago
The complexity and dev effort is higher initially because the paradigm is so different from "localhost" development. But once the initial boilerplate and yak-shaving work is done, serverless can actually be easier to manage becaus
94.
by tirumaraiselvan 8y ago
Apart from permissions, which can perhaps be solved by temp credentials etc, how do you prevent 1) DDoS: someone fiddling the queries to result in db outage, 2) scale: browsers can't leverage connection pooling so not sure if DB can ha
95.
by tirumaraiselvan 8y ago
TLDR: Author doesn't have enough time in weekends to rest properly.
96.
by tirumaraiselvan 8y ago
But there are managed Postgres services in almost all cloud providers.
97.
by tirumaraiselvan 8y ago
Does Buildah build images in a completely unprivileged environment? There are other tools like Kaniko which have few gotchas like although they don't need docker daemon but they still need ROOT access which does not make it truly secur
98.
by tirumaraiselvan 8y ago
Also check out Hasura ( https://hasura.io ) which works on any Postgres anywhere. Hasura provides out-of-the-box GraphQL APIs which you can extend as well while hooking into any (web-based) external Auth system for role based acce
99.
by tirumaraiselvan 8y ago
This is what Zeit v1.0 was also doing but they moved to Zeit v2.0 and discountinued Docker support. Not sure why no Serverless platform gives Docker support. Anyways, you might want to check out knative on GKE as serverless on Kubernetes me
100.
by tirumaraiselvan 8y ago
Good to see diversity in most of the teams :) Things are definitely changing.
101.
by tirumaraiselvan 8y ago
Offtopic: The UI of this blog is simply outstanding!
102.
by tirumaraiselvan 8y ago
> We were forced to solutions like github Ghost or Percona if we wanted to stick with Aurora What do you mean by this?
103.
by tirumaraiselvan 8y ago
No mention of connection pooling? Does Aurora handle 1000s of concurrent connection considering it is cloud-native?
104.
by tirumaraiselvan 8y ago
What is the Apollo stack? Do you mean GraphQL in the frontend?
105.
by tirumaraiselvan 8y ago
Seems like this is the main product of a full-time startup. In that case, I am curious how are you thinking about the future and business model considering it is 1) open source and 2) many competitors.
106.
by tirumaraiselvan 8y ago
This is very good insight and I suppose lot of people would be facing the same issues. I think latency is an issue when you use Lambdas for sync operations. Fundamentally when using serverless, I think your application should become fully a
107.
by tirumaraiselvan 8y ago
I see, but security aside I am not sure how the latency is impacted by having a serverless on a DynamoDB VPC endpoint. BTW, you can expose RDS out to the internet.
108.
by tirumaraiselvan 8y ago
Why do the problems that you state with RDS not true for DynamoDB? Does DynamoDB not run in a VPC?
109.
by tirumaraiselvan 8y ago
A much needed paper which goes into the programming model in serverless rather than the operational model. Although, the first cases study is obviously bad for serverless (training a ML model) whereas the second case study does not indicate
110.
by tirumaraiselvan 8y ago
My preferred title would have been: One step sideways A much needed paper which goes into the programming model in serverless rather than the operational model. Although, the first cases study is obviously bad for serverless (training a ML
111.
by tirumaraiselvan 8y ago
Yes. The only difference is the unit economics. You pay per request in serverless whereas you pay "constant" amount in Heroku. Don't think it should be too hard for heroku to introduce price per request plans since they alrea
112.
by tirumaraiselvan 8y ago
I think they are managing the continuous deployment part of the devops cycle which is traditionally done using webhook.
113.
by tirumaraiselvan 8y ago
I am curious to know why they considered IoT Core instead of AppSync.
114.
by tirumaraiselvan 8y ago
I would like to compare this with Haskell's STM.
115.
How Airbnb Is Moving 10x Faster at Scale with GraphQL(medium.com)
3 points by tirumaraiselvan 8y ago|0 comments
116.
by tirumaraiselvan 8y ago
I am the author of Hasura Event Triggers [1], we guarantee reliable webhooks by persisting each event in Postgres which is then processed (parallely) by multiple workers. [1] https://hasura.io/event-triggers
117.
by tirumaraiselvan 8y ago
Even with separate queues per customer, how are you ensuring ordering? Are you using something like Kafka which ensures ordering with-in partitions?
118.
Ask HN: How do you keep track of comments in HN?
1 points by tirumaraiselvan 8y ago|2 comments
119.
by tirumaraiselvan 8y ago
I prefer the the exact opposite approach. I don't want to learn any new tools however easy they might be when a one time effort (few lines of code) can give you a dependency free development/deployment mechanism. Ref: https:&#x2F
120.
by tirumaraiselvan 8y ago
This.

More ›