rywalker

Implying that Airflow is a simple mixture of a few ingredients is selling it quite short. There are a lot of knobs and switches in Airflow (i.e. features) that have been built and battle-tested over a lot of users. It has quite a lot of dependencies across the scheduler, webserver, cli, and worker modes. And there is a lot of new development going into Airflow in recent months (new API, DAG serialization, making the scheduler HA).

No.

yep, just wasted 10 min on this :)

Yes I need to hire a React dev right now :)

Super exited to see the project get out of incubation. It's an amazing tool.

Great overview. Do you plan to open source the DAG dependency graph tool?

I'd suggest using a service like Segment or MetaRouter.io to collect the event data, then use Airflow to prep it.

+1 from me as well. Well done.

This is likely a middle case, not enough traction to get next round of funding as a viable product/company.

I personally use Astro on my iPhone (just uninstalled this morning when I got their notification). It was good app, but no way for them to get any money from me.

It's really hard to build a product AND a predictable, profitable, repeatable growth model that VCs want to fund.

My guess is that you had an underpowered database instance backing Airflow.

Here we have a company that is simply opening up visibility of the code of their commercial offering, which will enhance customer relationships vs. keeping the code black box —— and it's observed as user-hostile?

Open core isn't evil. Companies need to make money, and shouldn't have to choose between fully-open-source vs. closed-source.

Fully-open-source companies have a really hard time of building a good company, because despite the great work they put out into the world, other enterprising cloud companies can build closed-source cloud services around it. For example, I've paid Compose.io and other companies real money around MongoDB, and never a cent to MongoDB the company. Same goes w/ Docker, who has struggled to build a great business because they open-sourced so much of their value.

So yeah, Elastic is trying to make it more likely that you'll choose to buy a license, because the health of their business depends on getting paid customers.

They are working to resolve https://medium.com/@dwalsh.sdlr/hi-ezequiel-6855beab08cb

Understand the pause, and if we were a social networking company I'd be more concerned - but already our decision to use GraphQL/React is paying off, as it differentiates for customers looking to integrate our product into their product due to the richness of the API that we are inherently providing.

Yeah that ending is a bit mysterious. In the end, Romeo decided not to move forward. It wasn't price; just not a great fit. The experience did prompt us to change our back-end from a heavy reliance on AWS services to more standard big data technology: http://www.astronomer.io/blog/sneak-peak-at-our-new-backend

It was ranked #1 by SeedRankings in 2015 when we went through it (http://www.forbes.com/sites/briansolomon/2015/03/17/the-best...). Looks like 2016 dropped to #4, but still an amazing program.

Great post Leo. Most startup "diligence" is a waste of time, usually just investors checking the box after they've already made a decision.

Very cool. Is there a getting started tutorial somewhere?

Project looks promising... Do you have source code to a demo app available?

You deserve more upvotes. I think HN is sleeping.

Great looking demo... I was captivated to watch to the end. Looks like you've got some great features. Is development done + you're ready for customers?

Good suggestion, angersock — though it might take a bit more than an afternoon to get it done ;)

At least 1/2 the blame is on them. No excuse not to have jr dev completely busy. That's incompetent management on their part.

Great points Josh - it's pretty common for new Meteor devs to rely only on console.log - this is a valuable reminder of all the other options for stepping up our debugging game :)

Sounds interesting. Curious about something — if my app relies on cloud services (Amazon S3, Google BigQuery, etc), does Replicated do anything around that? I'm guessing I might need to modify my app a bit to ensure that cloud services endpoints are stored in deploy configuration, and not baked into the code?

Looking forward to seeing what they come up with for Galaxy.

Sorry to hear it didn't work out for you guys. I definitely prefer the new world where communication goes through Slack rather than email.

Meteor's hosting platform will be optimized for websocket-oriented always-connected applications, with monitoring/auto-scaling features for that sort of app.

Congratz to a very smart team. Love how Meteor seeks to include other good Javascript frameworks into the platform (like React, Angular), rather than trying to force an artificial "one true way" — looking forward to seeing Galaxy.

That first chart has me worried... This would be the year of a startup bubble burst, if it follows same pattern as last time.

USERcycle "BI for startups" — we think user retention is most important metric for products early on. Here's our own weekly active users, since we started building product: https://usercycle.com/share/project/ekxMvhGEGWwWbHi8x/retent...

I'm guessing they sent obvious yes's and obvious no's already, and now they're going through the bubble teams.