Hey all, I don't want to setup a dedicated postgres database in azure just yet and instead as a sandbox wanted to use an azure vm and download postgres and lakfes on there. Any sizing suggestions? Temp storage, ram, cores etc?

Hey @Yusuf Khan, welcome! For learning purposes, see the quickstart section in our docs- you can spin up a containerized lakeFS using docker-compose or on Kubernetes. This will include postgres as a container.

Hey, not super familiar with docker but I know it can pose potential security concerns unless images are vetted. But even if I use docker, are there any suggestions for how to size the VM?

Yes, we have a sizing guide describing the desired database size in terms storage, memory and CPU. Please let us know if you find it helpful

I appreciate the help but not particularly. Like I mentioned I'm looking for sizing suggestions for an azure vm. I'm not spinning up a dedicated postgres db service yet. Just need a vm size suggestion if anyone here can help with that.

Is there a different channel I should be posting this question in? Or on github? I assumed this was a beginner question

@Yusuf Khan this is a great place for this question 🙂. The sizing guide should give you an idea of how much storage, memory and cpu your lakeFS server and/or database will need. You should choose an Azure vm according to the combined amount of resources. Does that make sense?

@Yusuf Khan @Yoni Augarten if you're just getting started, looking to do a POC, starting with something like a F4s v2 Azure VM should probably take you pretty far in terms of throughput (thousands of requests per second).

Yep yep, thank you guys! I'm doing a presentation later this week to my team borrowing heavily from the ideas from you guys.

Our pleasure! let us know how things go and if you have additional questions or requests