carimura

34 ms·

1. 481.▲
   by carimura 10y ago

   IronWorker is more classic job processing whereas IronFunctions is AWS Lambda-style sync service. We'll follow up with a longer blog post on the differences.
2. 482.▲
   by carimura 10y ago

   also join the real-time conversation: http://get.iron.io/open-slack
3. 483.▲
   by carimura 10y ago

   Ya if it's a popular request, definitely.
4. 484.▲
   by carimura 10y ago

   Hi All, This is Chad, CEO of Iron.io. It's true that we had to make some hard decisions and say goodbye to some friends. That said, a majority of the team is still here and dedicated to operating and growing the company. IronWorker fir
5. 485.▲
   Serverless computing on DC/OS with Iron.io(mesosphere.com)

   9 points by carimura 10y ago|1 comments
6. 486.▲
   What is Serverless Computing and why is it important?(iron.io)

   16 points by carimura 10y ago|0 comments
7. 487.▲
   by carimura 11y ago

   Thanks for the synopsis. Lots of plans for IronWorker including fully custom Docker image support (soon) and millisecond response times (soon'ish). We also support custom configurations of CPU/RAM for dedicated customers which is
8. 488.▲
   by carimura 11y ago

   Just for clarification, the IronWorker platform by Iron.io supports large enterprise deployments in cloud, on-premises, and hybrid environments, so it scales from small hosted projects to very large deployments processing millions of jobs p
9. 489.▲
   by carimura 12y ago

   [I'm with Iron.io] Similar, yes. We're excited that developers are seeing the power of the task/worker/lambda being the scalable unit of work rather than server or VM or even container. Haven't used Lambda much yet
10. 490.▲
    by carimura 12y ago

    I can't speak for HT specifically but dependency management is fairly straightforward. You can include any gems or libraries in your worker code package. If they contain native extensions, we'll compile and package them in at the
11. 491.▲
    by carimura 12y ago

    Iron.io has 3 functions: the scheduler, the queue, and the processing/worker platform. CRON would just be the scheduler part of that and you'd still be left dealing with where to host workers, how to scale them, manage/monito
12. 492.▲
    HotelTonight's ETL Pipeline Built w/ Iron.io and RedShift(engineering.hoteltonight.com)

    15 points by carimura 12y ago|7 comments
13. 493.▲
    Announcing IronMQ Alerts: Queue state webhooks(blog.iron.io)

    1 points by carimura 13y ago|0 comments
14. 494.▲
    by carimura 13y ago

    The next coming of SOA!
15. 495.▲
    by carimura 13y ago

    Sorry for your issues anfleene. Reliability is our top top priority. FWIW our uptime has been 99.9% over the past year - and this is far from where we want it to be. We now also offer isolated clustering for production level highly availabl
16. 496.▲
    by carimura 13y ago

    Definitely nice lists, and nowhere near complete given the data we've collected.
17. 497.▲
    by carimura 13y ago

    that too.
18. 498.▲
    by carimura 13y ago

    [Disclaimer/Warning I work there and this is about Iron.] Vs RabbitMQ: - Native cloud service over HTTP transport - Clean easy API - Scales to unlimited queues/clients - Push queues can have URL endpoints as subscribers - Highly
19. 499.▲
    by carimura 13y ago

    A long tipping point, but one indeed.
20. 500.▲
    by carimura 13y ago

    Fair enough. :) For the record, we actually use a lot of Ruby in our frontend systems as well as organize the SFRails meetup group in San Francisco. We just -- love GoLang for everything else.
21. 501.▲
    by carimura 13y ago

    Nice analogy. Feel that way all the time.
22. 502.▲
    by carimura 13y ago

    definitely seems useful
23. 503.▲
    by carimura 13y ago

    Happens to the best of them... thanks for the detailed writeup guys. Love the service.
24. 504.▲
    by carimura 13y ago

    Thanks! The energy in the rooms during these meetups is palpable.. like the next big thing is coming.
25. 505.▲
    Go 1.1 and Juju (videos from GoSF)(blog.iron.io)

    13 points by carimura 13y ago|4 comments
26. 506.▲
    by carimura 14y ago

    don't worry... our Ruby servers kept us churning for a long time.
27. 507.▲
    by carimura 14y ago

    Monitor Stands!! [1] https://plus.google.com/photos/100264837158995116368/albums/...
28. 508.▲
    IronMQ Cloud Message Queue as a Celery Broker(blog.iron.io)

    9 points by carimura 14y ago|1 comments
29. 509.▲
    by carimura 14y ago

    Nice one. #11.
30. 510.▲
    by carimura 14y ago

    Awesome guys.. glad to be a part of this.