Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
talawahtech
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
61.
▲
We Use Web Components
(dev.to)
1 points
by
talawahtech
7y ago
|
0 comments
62.
▲
by
talawahtech
7y ago
AWS Bulletin: https://aws.amazon.com/security/security-bulletins/AWS-2019-... FYI if your instances are behind an Application Load Balancer or Classic Load Balancer then they are protected, but NOT if they are b
63.
▲
by
talawahtech
8y ago
Lots of mention of CircleCI and Gitlab as the reason for Travis' downfall, which is very true. I also think GitHub announcing GitHub Actions[1] may have been the final nail in the coffin. I think GitHub Actions will become a major forc
64.
▲
by
talawahtech
8y ago
Given the scale and popularity of DynamoDB and the distributed nature you would think that they could hire multiple teams just to work on improving it, but I guess it isn't as simple as that. I would love to get a behind the scenes loo
65.
▲
by
talawahtech
8y ago
Saying DynamoDB is built on top of InnoDB is a pretty big oversimplification of a much more complex distributed system[1] and for all we know they could have switched out the low level the storage engine on the backend to something like Roc
66.
▲
by
talawahtech
8y ago
It sounds like it is built on top of the Aurora storage subsystem that is used by both Aurora MySQl and Aurora Postgres[1]. I kinda expected them to build it on top of DynamoDb's backend and provide the same kind of "Serverless&qu
67.
▲
by
talawahtech
8y ago
Several related lambda announcements to around structure/reuse as well: 1. Lambda Layers - Reusable components that can be shared across lambda functions (covered in the linked article) 2. AWS (Serverless) Toolkits for PyCharm, Intelli
68.
▲
by
talawahtech
8y ago
The FAQs on the Firecracker website[1] specifically address the difference between Firecracker and Kata Containers. The main thrust being that they have decided not to use QEMU and have instead chosen a much more minimal "cloud-native&
69.
▲
by
talawahtech
8y ago
Theoretically, if container start up times are around 125ms it should be possible to achieve this with Fargate + Knative's "scale to zero" functionality[1]. AWS is already working on improving Fargate/Kubernetes integrat
70.
▲
by
talawahtech
8y ago
This is huge! It basically removes the VM as the security boundary for something like Fargate [1]. This should lead to a significant reduction in pricing since Fargate will no longer need to over provision in the background because VMs were
71.
▲
by
talawahtech
8y ago
This is useful, and long overdue. Trying to deploy a single page app or static site using S3 + CloudFront is way more complex than it should be. Trying to automate deployment using CodePipeline is a real pain. By the time you start to think
72.
▲
by
talawahtech
9y ago
Pricing seems to be about 15% cheaper than C4 with slightly more RAM and the same ECU equivalence
73.
▲
by
talawahtech
10y ago
The first two paragraphs of this post come across as unnecessarily defensive and combative. Amazon released a product and then released an open source preview project to make that product easier to use. They even mention other similar proje