Serverless… how to share a project?

When you have a serverless project (assuming you are using the nano-service micro-function type approach of AWS Lambda and the like) then something happens that I hadn’t considered until recently.

It becomes a lot harder to share a project.

Like a github repository.

That’s because the idea of a serverless project is more complex than previous types of project.

It includes an infrastructure component.

So, you can sort of share code, but really you need to share code + infrastructure.

Which is interesting.

Because most open source projects don’t need that.

Most open source projects on places like github expect you to have a server, or at least define the hardware (e.g. for IoT projects on arduino or similar).

Maybe, as a community, we need to come up with a vaguely standard way of sharing an open source project (a template if you will).

Is it that a project must have a terraform script with it to ensure deployment?

Maybe this is why serverless is seen as quite hard.

We don’t have the “hello world” of serverless yet.

Maybe.

Or just maybe it’s too different for people to grasp yet.

Not sure.

Written by

ServerlessDays CoFounder (Jeff), ex AWS Serverless Snr DA, experienced CTO/Interim, Startups, Entrepreneur, Techie, Geek and Christian

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store