HackerTrans
TopNewTrendsCommentsPastAskShowJobs

giuseppelt

no profile record

Submissions

[untitled]

1 points·by giuseppelt·3 anni fa·0 comments

Architecture and code organization of an Early Stage SaaS

feelback.dev
1 points·by giuseppelt·3 anni fa·1 comments

Build your own FaaS: Self-host workers, lambda, JavaScript functions

breakp.dev
45 points·by giuseppelt·3 anni fa·5 comments

Build your own FaaS: Self-host Cloudflare workers on Fly and everywhere

github.com
3 points·by giuseppelt·3 anni fa·1 comments

Architecture of an Early Stage SaaS

feelback.dev
3 points·by giuseppelt·3 anni fa·1 comments

comments

giuseppelt
·3 anni fa·discuss
Nicely done. I red about the _simplifications_, what's the target audience? Kids? or some particular group?
giuseppelt
·3 anni fa·discuss
good luck on your path
giuseppelt
·3 anni fa·discuss
As a solo founder, I wrote about design principles, tradeoffs and tricks used to create the architecture of a SAAS I'm building.

It's a deep dive, also with the deployment process.

At the end, also some info on how to manage a monorepo with all service systems and components.

Any suggestion or advice is appreciated.
giuseppelt
·3 anni fa·discuss
Answer briefly now, I will come back later.

Basically, I think that rolling restarts of the worker instances, just does the trick in the easiest way. Mind that flymachine instances, are pretty quick to boot. While an instance is restarting, others still serve requests so the system is still up.
giuseppelt
·3 anni fa·discuss
hi prakis, thanks! really needed!
giuseppelt
·3 anni fa·discuss
Hi, this is more an experiment that a real production-tested project. You can create your own Function as a Service architecture, and self-host everywhere you want.

It leverages workerd, the Cloudflare worker runtime. And as deploy tutorial, it include a guide to host everything on Fly.

It support container-based deployment, so docker is your friend here.

The complete project is on: https://github.com/giuseppelt/self-workerd

Mind this a proof-of-concept, public exposed systems require more work.
giuseppelt
·3 anni fa·discuss
Hi, this is more an experiment that a real production-tested project. You can create your own Function as a Service architecture, and self-host on your resources.

It support container-based deployment, so you can host wherever you like. I published a step by step guide for any one curious: https://www.breakp.dev/blog/build-your-own-faas/

Mind this a proof-of-concept, public exposed systems require more work.
giuseppelt
·3 anni fa·discuss
As a solo founder, I wrote about design principles, tradeoffs and tricks used to build the launch architecture of a SAAS.

Some topics discussed:

- How to design a low-maintenance architecture?

- Which cost-effective providers to use?

- How to deploy to production with ease?

- How to manage a monorepo with all service systems and components?

Any suggestion or advice is appreciated.