The Architecture of Serverless Data Systems
jack-vanlightly.com
The Architecture of Serverless Data Systems
1–10 of 45 posts
Re: The Architecture of Serverless Data Systems
#2[dead]
Re: The Architecture of Serverless Data Systems
#3I wasn't aware of 800G/1TB networking before.
Very strange world that transferring data between servers is 2x as fast as reading from a PCI bus.
Re: The Architecture of Serverless Data Systems
#4I wasn't aware of 800G/1TB networking before. Very strange world that transferring data between servers is 2x as fast as reading from a PCI bus.
InfiniBand, and unless you're super high up on the food chain (aka: married to NVIDIA), you won't get access to it for at least 52+ weeks after you submit your purchase order.
Re: The Architecture of Serverless Data Systems
#5I'm currently working on a server-less, no-code multi-tenant platform. I'm still unsure if I should aim for full no-code or go for low-code. So far it's possible to build complex apps with it using only HTML tags (web components). Although it also exposes a CRUD interface, I haven't promoted this aspect as I feel it detracts from the huge time-saving and maintenance benefits which come with building apps using only declarative HTML + CSS.
The other thing I've been careful about is to ensure that the backend is fully no-code. As soon as you allow the user to execute custom code on your backend, it opens up security risks with multi-tenancy. The risk doesn't fully go away when you containerize as vulnerabilities have been encountered in the past in Docker which allow escaping the sandbox.
In my case, although the user can customize back end behavior, they can only do so in a highly constrained way using well defined parameters, not custom code. It saves a lot of effort not having to write a VM or restrict each container to a single host.
Re: The Architecture of Serverless Data Systems
#6Two observations:
- "serverless" is a really bad name for these systems. As is often commented, some variation of "somebody-elses-server" would be better.
- Cost wasn't mentioned in the article, but the cost of renting databases and search-indices is still really high, even though these technologies are no longer the new hotness.
Re: The Architecture of Serverless Data Systems
#7Two observations: - "serverless" is a really bad name for these systems. As is often commented, some variation of "somebody-elses-server" would be better. - Cost wasn't mentioned in the article, but the cost of renting databases and search-indices is still really high, even though these technologies are no longer the new hotness.
Serverless and managed basically mean the same thing?
Re: The Architecture of Serverless Data Systems
#8Two observations: - "serverless" is a really bad name for these systems. As is often commented, some variation of "somebody-elses-server" would be better. - Cost wasn't mentioned in the article, but the cost of renting databases and search-indices is still really high, even though these technologies are no longer the new hotness.
Cost is one of the core premises of the article:
> Top tier SaaS services like S3 are able to deliver amazing simplicity, reliability, durability, scalability, and low price because their technologies are structurally oriented to deliver those things
The whole point is to explore how to drive cost down (due to higher efficiencies in sharing resources) by having multi tenant approach from the get-go.
The point isn't to compare to running your own database on your own rack. It's to compare single tenant RDS with something like an S3-like multi tenant postgres for example.
Re: The Architecture of Serverless Data Systems
#9Two observations: - "serverless" is a really bad name for these systems. As is often commented, some variation of "somebody-elses-server" would be better. - Cost wasn't mentioned in the article, but the cost of renting databases and search-indices is still really high, even though these technologies are no longer the new hotness.
All cloud hosting is "somebody-elses-server". Serverless is more like "pay-per-function-call" in which case Azure Functions has a pretty appropriate name.
Also, the cost of renting databases has nothing to do with newness. Databases have evolved a lot in the past two decades. They do all sorts of stuff under the hood, which is why they can now often consume massive amounts of RAM. That doesn't come for free.
Re: The Architecture of Serverless Data Systems
#10I'm currently working on a server-less, no-code multi-tenant platform. I'm still unsure if I should aim for full no-code or go for low-code. So far it's possible to build complex apps with it using only HTML tags (web components). Although it also exposes a CRUD interface, I haven't promoted this aspect as I feel it detracts from the huge time-saving and maintenance benefits which come with building apps using only d…
> serverless no-code
Heck, at this point, it's time for a software platform called softwareless.