Knock.com | Senior Backend Node.js Engineer | Full Time | REMOTE | https://knock.com
Knock is on a mission to make home buying and selling simple and certain. Knock is an online home trade-in platform that uses data science to price homes accurately, technology to sell them quickly and a dedicated team of professionals to guide you every step of the way.
Stack is JS, Node, AWS, Go, Postgres, MySQL, Docker.
This looks great! I can imagine this lowering the barrier for building a quick side project significantly. I have a FT job so working outside of that stack means I have to spend a lot of time figuring out configs and other non-business logic related work.
Now a question - say I have a Treeline app that works great for a little side project. But eventually the project grows really big, both in traffic and scope. Is there a way to get off of Treeline (export code?) or do you think Treeline can scale well in this case.
You can take the code right now and download it and deploy it to any infrastructure provider you want! We provide a command line tool to sync code down and work locally or to package up and deploy.
Treeline compiles your apps to Node.js apps using the SailsJS framework. Your code is available to you at any time via a command-line tool--we offer the hosted version as an added bonus.
Can you handle apps with background tasks? In my experience, the backend systems basically end up being a large repository of jobs that need to get backgrounded, and handed off to other systems.
I would be even more excited if you could find some way to create and manage those effectively.
Would love to see it integrated with a front end building platform like Webflow. I just built a quick site with Webflow, but because it lacks any integration with DB/Backend it was only used as a landing page. Having this ability would let users create and end to end web product with only basic knowledge of programming.
Sails is very modular, if you wanted to replace the ORM with something else you could just replace the Waterline hook. Waterline is still pretty young and all of these features would be great to get added! We are always looking to add new contributors if anyone would like to help move some of these features along.
Cool! Thanks for the offer to answer further questions. When I google for sails, as you're probably aware, I come across this article from more than a year ago:
It's a "good, bad, ugly" article, but it's old. Care to comment on any of the issues mentioned in the "bad and ugly" parts. Specifically, I wonder about the (alleged, possibly old) lack of Waterline ORM support for associations / relational data.
I'm hoping that's a softball question. I love seeing new approaches succeed!
Version 0.10 of Waterline now supports associations. It's not as robust as I would like it but its iterative and it's getting better all the time. As for issues piling up thats something that is tough to solve. There are only a handful of us and we try our best to get to issues in a timely manner but like any large open source project it's a battle. Our builds are also passing now :) https://travis-ci.org/balderdashy/sails/builds
Should be pretty easy to expand this out to work with any PaaS such as Heroku, Modulus, etc. For aws maybe we could work on getting it to deploy to Elastic Beanstalk? Might also be cool to generate a docker image.
Knock is on a mission to make home buying and selling simple and certain. Knock is an online home trade-in platform that uses data science to price homes accurately, technology to sell them quickly and a dedicated team of professionals to guide you every step of the way.
Stack is JS, Node, AWS, Go, Postgres, MySQL, Docker.
Entire engineering department is fully remote.
https://www.knock.com/jobs