[Context: I worked with this team previously] Data here is coming from mobile apps, and is similar in volume to typical mobile app user analytics. I can certainly imagine that Segment would be a poor (or maybe just costly) fit for device telemetry in most IoT use-cases.
It’s non-obvious, but that’s actually very close to how farming works today, at least in the US. Farm-owners will lease their land for a season to grow a specific crop. The land needs to meet requirements for acreage, irrigation, etc., but someone else will “use” the farm.
I’m sure this happens on a continuum from “that’s a big field, can I use it?” to “here are seeds, I expect XYZ yield in N months”.
IFTTT | Full-time | Software Engineer | San Francisco, CA (ONSITE) | https://ifttt.com/jobs
Are you a maker/hacker/tinker-er? Do you love Ruby _and_ type systems? Want to help scale one of the largest consumer-oriented serverless platforms? Join IFTTT!
IFTTT is the free way to get all your apps and devices talking to each other. Not everything on the internet plays nice, so we're on a mission to build a more connected world.
IFTTT is hiring for a number of engineering roles* but I’m selfishly plugging the systems engineering (more-or-less backend) role. We’re a high-leverage team building resilient systems that operate at scale. Help us thoughtfully break apart our monolithic Rails application into composable services that support our consumer-facing teams to deliver award-winning experiences.
If you’re in the Bay Area and want to learn more, shoot me an email at nicky@ifttt.com. Happy to grab coffee and chat about what we’re working on and how you can help.
* Are you a data, mobile, or infrastructure engineer? We’d love to talk to you too! I’m happy to connect you with the right folks here at IFTTT.
Mesos running on AWS, almost entirely with EC2 spot instances.
We were big Heroku users as well, so carried over a number of Heroku patterns. For example, configuring everything with ENV vars, lightweight load balancing, grouping apps into several deployable targets, etc.
It’s certainly not better than Heroku in most ways, though there was no plausible way for us to continue running our workload on Heroku.
Is that true? The default limit on concurrent function executions is 1000. The existing Aurora (MySQL) should be able to handle cycling through those connections without issue.
The browser still has to make a request to the CDN to get back an HTTP 304. The goal is to avoid downloading a potentially large payload, not be resilient against connectivity issues.
To add to silvamerica's comment, this process is specific to running containers in development. When building images for deployment the dependencies are installed as a RUN step in the Dockerfile.
Edit: GitHub actually has a good list of trending repositories that you can filter by language. Most C projects seem to be libraries, but you might be able to glean something interesting - https://github.com/trending?l=c&since=monthly
