One gotta build to find out 🙊

The only difference is that you can share the bill of the dedicated machines with others. It allows a whole other group of possibilities.

That is one point I need to legally validate. But you can look at this just the way you look at serverless. You are sharing resources with everyone, but you do it against one business model of idle computing.

With this approach you would be able to still run your code on your own space.

Also, I thought about doing public capture the flag events for everyone to participate and try to break it (win = 💰)
In other words, think about it like managing a really big cluster
The only difference is that you have multiple disconnected projects instead of a single domain in your infrastructure

One thing that would be a bit hard to ensure everywhere is that there should be no leak of any direct address of the cluster. Everything should be routed by a WAF.

I need some POC's to give a really detailed answer here. But my first take on this would be to create a different private virtual network for each account. All the deployments should handle their traffic and eventually creating shared networks between accounts upon proper configuration.

All open for everyone to help, review and trust the service.

I have something on my mind but I know this is a sensitive topic. Would be very helpful to get some insights as early as possible.

Thank you guys! #buildinpublic

If we share resources securely and pay our share we can have more control on what we do at a fraction of the current price.

I'm talking about servers, CI/CD, storage space, registries, databases, queues, logs, telemetry with the experience we deserve...

#buildinpublic

**“PS: I’m on my solo founder journey, sharing my experiences and ideas as I go. Hopefully, something here adds value to your life.

If you enjoyed this, give me a follow—it means a lot on this side.”**

Everything in between is about refining data with straightforward actions to make it more useful, often masking underlying challenges. These ensures that data appears to be optimal, even if foundational issues persist.

(This is why software is hard…)

2. How you display/collect data

Web, native, watches, phones… you name it. The goal here is to reduce friction from our world to “normal people”. Don’t make it harder than it is.

1. How you store data

Relational, object or document oriented it doesn’t matter… You are doing one thing, storing data into disk space. Just do it in versatile way for your context. This often defines your coding standards.

Please tell me exactly where I’ve extrapolated your words and did any assumption 😂

I’ve never claimed problems were easy. Just said I could handle them.

“Preform operations over encrypted data”

First, data is not encrypted, it is cyphered

Second, encrypting data is done for a reason, normally privacy. If you are playing with it you are at least near a grey area

I would just be happy if you understood what I’m trying to say instead of picking up the keywords and play with them as you feel

It’s exhausting because we were discussing if UI is easier than server side code or not. This was taken out of context and is not near what I was trying to say

The good part here is that my ethics forbid me to comply with companies that make a living out of charging per idle computation.