Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
treeder
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
Project Thor Will Deliver First True Hybrid IronWorker Solution
(blog.iron.io)
9 points
by
treeder
11y ago
|
0 comments
32.
▲
by
treeder
11y ago
Docker support is a new feature to enable more complex jobs where you need to control the entire stack, for instance, maybe you need imagemagick installed on the core machine, or ghostscript. IronWorker can support that. It also allows you
33.
▲
by
treeder
11y ago
Yes, default is 100: http://docs.aws.amazon.com/lambda/latest/dg/limits.html
34.
▲
by
treeder
11y ago
Doesn't seem to be an issue. The files created inside the container and written to the mounted volume outside the container are the same user/group as the parent directory (outside the container), not root.
35.
▲
Why and How to Use Docker for Development
(medium.com)
16 points
by
treeder
11y ago
|
3 comments
36.
▲
Super Easy Serverless Slack Bots
(blog.iron.io)
4 points
by
treeder
12y ago
|
0 comments
37.
▲
The New Docker Based IronWorker Development Workflow
(blog.iron.io)
2 points
by
treeder
12y ago
|
0 comments
38.
▲
AWS Lambda vs. IronWorker
(blog.iron.io)
7 points
by
treeder
12y ago
|
0 comments
39.
▲
How to Make Your Android Phone as Close to Stock as Possible Without Rooting
(medium.com)
1 points
by
treeder
12y ago
|
0 comments
40.
▲
Go and Polymer, So Happy Together
(medium.com)
3 points
by
treeder
12y ago
|
0 comments
41.
▲
Docker in Production – What We’ve Learned Launching Over 300M Containers
(blog.iron.io)
21 points
by
treeder
12y ago
|
0 comments
42.
▲
MyVicePal – The best way to track your drinking habits and lose weight
(myvicepal.com)
3 points
by
treeder
12y ago
|
0 comments
43.
▲
Node.js + Iron == Relief from Parse Background Jobs
(medium.com)
1 points
by
treeder
12y ago
|
0 comments
44.
▲
Go After 2 Years in Production
(blog.iron.io)
323 points
by
treeder
13y ago
|
173 comments
45.
▲
IronMQ Fan-out Support
(blog.iron.io)
17 points
by
treeder
13y ago
|
1 comments
46.
▲
IronMQ Handling 250M Requests Per Day, IronWorker Executing Over 500K Jobs
(blog.iron.io)
5 points
by
treeder
13y ago
|
0 comments
47.
▲
by
treeder
14y ago
There's also the mgo library for MongoDB which is probably one of the best Mongo libraries out there (even 10gen thinks so): http://labix.org/mgo And http://github.com/lib/pq for Postgres.
48.
▲
by
treeder
14y ago
This first rewrite in Go was for the IronWorker API so all the operations are here: http://dev.iron.io/worker/reference/api/ There were less endpoints back then, but you can get the idea. The most heavily used operation being queuing up t
49.
▲
by
treeder
14y ago
We actually have our own deployment tools for Go (and for Rails, our databases, etc). We built them before all the new hip options that are around today. We build on the target machines, although that's not a requirement since we all run th
50.
▲
by
treeder
14y ago
We got a bunch of the little plastic ones sitting behind my desk: https://plus.google.com/u/0/101022900381697718949/posts/1Dbe...
51.
▲
by
treeder
14y ago
Hah, nice photo! Are you ok with that? Found it on google images.
52.
▲
by
treeder
14y ago
This was on Ruby 1.9, 2010 era. No patches. Memory was definitely a concern and probably contributed to some of it. Just to note though, after a machine was taken offline by the load balancer, it would generally come back to life.
53.
▲
by
treeder
14y ago
Mostly because I can't stand Javascript. It makes me cringe just thinking about it. Go is much nicer to work with.
54.
▲
How We Went from 30 Servers to 2: Go
(blog.iron.io)
688 points
by
treeder
14y ago
|
495 comments
55.
▲
Game of Nines - Iron.io Uptime Report
(blog.iron.io)
3 points
by
treeder
14y ago
|
0 comments
56.
▲
by
treeder
14y ago
Built from the ground up, made for the cloud. We use Go as our language.
57.
▲
by
treeder
14y ago
You're welcome. ;) Let us know what you think after you've tried it.
58.
▲
IronMQ Push Queues - Reliable Message Delivery for the Cloud
(blog.iron.io)
21 points
by
treeder
14y ago
|
7 comments
59.
▲
by
treeder
14y ago
Some queues offer "at-least-once" delivery (such as SQS) meaning even if you do ack/delete the message, you can still get it again. IronMQ will not deliver a message again if it's been acked/deleted. And yes, work should be idempotent, as i
60.
▲
Queue Webhook Events with IronMQ Webhook Support
(blog.iron.io)
11 points
by
treeder
14y ago
|
3 comments
More ›