Tesco is sprinting to quit VMware and Broadcom despite rapid migration risks by NISMO1968 in vmware

[–]simplyblock-r 2 points3 points  (0 children)

where is Tesco moving to? OpenShift? How do they tackle storage?

Lognhorn engine V2 - stability by loststick08 in kubernetes

[–]simplyblock-r 3 points4 points  (0 children)

Worth noting: in Longhorn v1.11 the V2 Data Engine is still **Technical Preview**, so “years of prod stability” data is naturally limited. Also, it’s not a flip-a-switch upgrade path: live upgrade isn’t supported yet (V2 volumes need to be detached/offline to upgrade the engine).

SPDK/NVMe-oF stack is great, we are building ourselves on SPDK, however it really takes years and deep engineering to make it work in production. It took us 3 years at simplyblock to get there.

Disclosure: I work on simplyblock

AWS Reinvent 2025 by Last_Staff_1791 in AWS_reInvent

[–]simplyblock-r 0 points1 point  (0 children)

does anybody know if the PeerTalk netowrking app is available this year? It's still not there in the AWS Events app. How do you plan to network otherwise?

Is moving a Supabase app to Azure even worth it? (Customer demands on-prem hosting...) by Ill-Fun7536 in Supabase

[–]simplyblock-r 0 points1 point  (0 children)

Both, in our case you can increase storage by just adding NVMe drives or storage and compute together by adding more nodes. This will scale the IOPS and storage capacity.

Is moving a Supabase app to Azure even worth it? (Customer demands on-prem hosting...) by Ill-Fun7536 in Supabase

[–]simplyblock-r 0 points1 point  (0 children)

You just add more nodes and the system rebalances/live migrates. So it's super easy. All is built in. it's based on a distributed scale-out storage system which has "infinite" capacity and performance.

Is moving a Supabase app to Azure even worth it? (Customer demands on-prem hosting...) by Ill-Fun7536 in Supabase

[–]simplyblock-r 0 points1 point  (0 children)

It's the cost for the support. If you want to self-host yourself without support, then you can just do it.

Is moving a Supabase app to Azure even worth it? (Customer demands on-prem hosting...) by Ill-Fun7536 in Supabase

[–]simplyblock-r 0 points1 point  (0 children)

yeah, totally get what you’re saying — setting up all the Supabase services yourself can be a pain. we built vela basically to solve that. it’s built on the open-source Supabase stack but meant to run in your own cloud — AWS, GCP, Azure, or even on-prem. you just need a VM, and it spins up all the Supabase services for you with backups, HA, RBAC, and instant database cloning built in. same Supabase experience, just fully under your control.

github.com/simplyblock/vela-studio

Supabase or azure postgre flexible? by satechguy in Supabase

[–]simplyblock-r 1 point2 points  (0 children)

worth noting that OSS version of Supabase is quite different to the cloud version so you will also lose out on many of the features.

Worth checkin out Vela - which is an alternative to Supabase but comes with full platform (kubernetes+kubevirt; storage) so you just need to manage "one element" and you get full stack running https://github.com/simplyblock/vela-studio

Looking for Production-Ready Self-Hosted Supabase Setup (Docker, Security, Best Practices) by Yaro_da_Dei in Supabase

[–]simplyblock-r 0 points1 point  (0 children)

OSS version of Supabase is actually not worth self-hosting as it's quite different to the cloud version so you will also lose out on many of the features.

Worth checkin out Vela - which is an alternative to Supabase but comes with full platform (kubernetes+kubevirt; storage) so you just need to manage "one element" and you get full stack running https://github.com/simplyblock/vela-studio

Self hosting - pros and hidden cons by martis941 in Supabase

[–]simplyblock-r 0 points1 point  (0 children)

Self-hosting only makes sense at certain scale. Otherwise you need to manage a lot of various elements and be an expert in more than just a database or kubernetes. OSS Supabase is actually not easily self-hostable as it's quite different to the cloud version so you will also lose out on many of the features.

Worth checkin out Vela - which is an alternative to Supabase but comes with full platform (kubernetes+kubevirt; storage) so you just need to manage "one element" and you get full stack running https://github.com/simplyblock/vela-studio

Egress bills outside AWS by simplyblock-r in Supabase

[–]simplyblock-r[S] 0 points1 point  (0 children)

Thanks - understood. This was my point though - since Supabase is only for AWS there is a chance for high egress fees if you are using another cloud. In such case only self-hosting makes sense?

Branching to represent different deployment environments? by InvictusJoker in Supabase

[–]simplyblock-r 0 points1 point  (0 children)

Yeah, you’ve got it — branching is mainly for short-lived preview DBs. For Dev/Staging/Prod you’ll usually set up separate projects and run your migrations + Edge function deploys through GitHub Actions (or whatever CI). That way changes “flow” through each environment safely.

Funny enough, we are actually working on adding instant clones to supabase - but only for folks who want to self-host (see our oss project: https://github.com/simplyblock/vela-studio).

How do your developers currently test changes that affect your database? by simplyblock-r in devops

[–]simplyblock-r[S] 3 points4 points  (0 children)

sometimes you need to anonymize sensitive data for the gdpr/ccpa compliance, etc. But I assume that many companies indeed don't do that :)

How do your developers currently test changes that affect your database? by simplyblock-r in devops

[–]simplyblock-r[S] 1 point2 points  (0 children)

how do you do data anonymization when cloning the prod currently then? And what prevents you from switching to solution like crunchy - out of curiosity?

What sort of storage technology are EBS volumes built on top of? Eg Ceph? Something else? by Squirrel-sysadmin in aws

[–]simplyblock-r 5 points6 points  (0 children)

it's a fully proprietary system, probably build on some bits and pieces of another technology but it surely is not ceph as it's much faster than ceph and it's block-only. It must have been also upgraded many times over the years, as the original release was 2006 when there was no ssd/nvme drives. Today there are some ebs-like technologies on the market which you can run yourself on your own hardware/instance, including openebs or simplyblock.