davidwells

Vendia | Frontend & backend developers | Remote, San Francisco/Bay, Seattle | Full-Time | https://jobs.vendia.net

The TLDR: We offer an immutable database that handles kind of data/file that stores a complete version history of everything saved to it. This data is accessible via a standard GraphQL API or via our typesafe SDK client (kind of like prisma). Vendia is cofounded by Tim Wagner, creator of AWS Lambda. We've raised over $15 million in VC.

Our tech stack includes:

All major cloud providers (AWS, GCP, Azure, etc), Python, Node.js, Serverless, CDK, Terraform, Lambda, GraphQL, Next.js, React, TypeScript. etc.

We have several positions open at https://boards.greenhouse.io/vendia.

Come and join us!

Additional details:

We are building out a way for companies to share data & files via a b̶l̶o̶c̶k̶c̶h̶a̶i̶n̶ immutable ledgered database thats accessible via a standard graphQL API. It’s designed to work for multiple parties (e.g. external partner companies, different internal teams, etc., however it can work as a single user database as well. At it’s core, it’s the ledgered database that keeps full history over any data or file changes throughout time. Users can read/write/subscribe to data via a graphQL API and a typesafe SDK client (like prisma). Under the hood, it’s deployed as serverless resources to alleviate operational burdens & have a pay per use pricing model. When someone joins we spin up a cloud based b̶l̶o̶c̶k̶c̶h̶a̶i̶n̶ database via an easy to use GraphQL interface.

https://boards.greenhouse.io/vendia

Vendia | Frontend & backend developers | Remote, San Francisco/Bay, Seattle | Full-Time | https://jobs.vendia.net The TLDR; about Vendia:

We are building an easy to provision, use, & manage multi-party cross-cloud blockchain database & file storage system with the ability to write smart contracts in any runtime. Vendia is cofounded by Tim Wagner, creator of AWS Lambda. We've raised over $15 million in VC.

We have several positions open at https://boards.greenhouse.io/vendia including:

- Senior Backend / Core Engineer https://boards.greenhouse.io/vendia/jobs/4419688003

- Senior Backend / Core Engineer - Azure https://boards.greenhouse.io/vendia/jobs/4436638003

- Senior Backend / Core Engineer - GCP https://boards.greenhouse.io/vendia/jobs/4436662003

- Senior Full Stack Engineer - https://boards.greenhouse.io/vendia/jobs/4415072003

Our tech stack includes:

All major cloud providers, Python, Node.js, AWS, Serverless, CDK, Lambda, GraphQL, Next.js, React, TypeScript. etc.

Come and join us!

Vendia | Frontend & backend developers | Remote, San Francisco/Bay, Seattle | Full-Time | https://jobs.vendia.net

The TLDR; about Vendia:

We are building an easy to provision, use, & manage multi-party multi-party blockchain database & file storage system with the ability to write smart contracts in any runtime. Vendia is cofounded by Tim Wagner, creator of AWS Lambda. We've raised over $15 million in VC.

We have several positions open at https://boards.greenhouse.io/vendia including:

- Senior Backend / Core Engineer https://boards.greenhouse.io/vendia/jobs/4419688003

- Senior Backend / Core Engineer - Azure https://boards.greenhouse.io/vendia/jobs/4436638003

- Senior Backend / Core Engineer - GCP https://boards.greenhouse.io/vendia/jobs/4436662003

- Senior Full Stack Engineer - https://boards.greenhouse.io/vendia/jobs/4415072003

Our tech stack includes:

All major cloud providers, Python, Node.js, AWS, Serverless, CDK, Lambda, GraphQL, Next.js, React, TypeScript. etc.

Come and join us!

Do you any any examples of a company having ONLY a graphQL API for public use?

Hey gbrits. Thanks for the comment.

This looks like a great alternative solution!

Haven't messed around with step functions yet but was looking into it today after I found this https://www.youtube.com/watch?v=9MKL5Jr2zZ4&t=226s

Are you using step functions for other flows?

Good point. I care greatly about these things.

This project greatly simplifies how we publish content in an elegant out of sight out of mind way.

Before, if someone was out of town, we would need to rely on others to push the merge button on posts for us. Now, the robots do it for us!

Thanks tom! I love golf!

> The hourly cron runs about 720 times a month which is far below the 1,000,000 free invocations that lambda provides under their free tier.

This entire service (the 2 functions & 1 dynamo table) should run well under the AWS free tier. see https://aws.amazon.com/free/

Hey zokier. Thanks for the comment.

In theory yes. I could provision a new function with an exact cron schedule to run once and then tear itself down.

In practice, this is a lot of extra logic to write to achieve this and would also potentially make own AWS account rather messy.

The hourly cron runs about 720 times a month which is far below the 1,000,000 free invocations that lambda provides under their free tier.

One lambda runs when github webhooks are fired: https://github.com/serverless/post-scheduler#github-webhook-...

The other lambda fires on a cron job https://github.com/serverless/post-scheduler#cron-job-archit...

I built the rocket ship so you don't have to ™

https://www.youtube.com/watch?v=qz72V84uWWA

Thanks for the comment foxhop! We try to keep things as simple as possible where we can.

This project came out of the need from our content team needing to publish content late at night and when people are out of office =)

Check out the code https://github.com/serverless/post-scheduler/blob/master/han... this serverless service is just 2 functions that get deployed. It's a set it and forget it service =)

Hello there! The serverless framework supports a number of different FAAS (function as a service) providers like IBM openwhisk, AWS lambda, & Azure functions from microsoft. See https://serverless.com/framework/docs/providers/ for more info.

So it's up to you where your code runs =)

Hey Chad,

What do you use https://github.com/andreypopp/react-async for?

I was trying to wrap my head around that the read the warning:

"WARNING: Keeping data in React component's state is a bad idea. React component's state is for purely UI state, like "if this dropdown openned or closed?". In light of that, React Async is an anti-pattern so you shouldn't use it unless you are 100% sure you need it"

Checkout https://hall.com/ its super slick