Not open source. What would be your use case?
141 karma · joined May 4, 2015
This approach isn't right for every use case and juice might be a better fit for this sort of 'direct block store', but wanted to include it here for folks that might want something like Juice but without having to maintain a metadata store.
(Disclosure: I work at Storj that develops Object Mount)
Cameras have been installed to fine cars running red lights. The city then reduces the length of the yellow to catch more people and offset the high cost of the cameras. The shortened yellows cause increased crashes and fatalities.
Net-net the track record in the states is not great.
One example https://www.koaa.com/news/news5-investigates/news-5-investig...
I get a lot of comments about being in an unfinished basement so I recently bought a green screen and some ring lights to try and improve my picture. The webcam on my laptop is too grainy for OBS to use the green screen, so looking to buy a new webcam.
While I agree that how a query planner works is one of the most ‘magic’ aspects, I think the output from the query planner in most databases is very approachable as well to regular common programmers and will get you quite far in solving performance issues. We know what full scans are (searching through every element of an array), etc.
The challenge is usually discovering that the jargon used in your database really maps to something you do already have a concept about and then reading the database documentation…
I can't imagine the pain and anguish over the years that must have been felt as parents, so it was comforting to read about what kind of person Bertrand became.
I hope that if my son ever needs my skills, I would be up to the task so perfectly understated here: "Extending an artificial intelligence tool on the fly to analyze the data, Bertrand’s father found an unusual strain of pseudomonas as the likely culprit in Bertrand’s body."
Best of luck with the Bertrand Might Endowment for Hope!
There are other object storage systems that have strong consistency guarantees that came out after S3.
It greatly simplifies things that an object written to S3 it is immutable.
On a high level, all writes to your storage use some UUID. All reads use a consistent metadata storage (pick a modern database). After your write is complete and you are sure it is persisted, do the metadata update and return success. Everyone gets a consistent view of the operation.
There is a 'Contact Us' button at the bottom of the page you can always reach out.
Glacier can get pricey when you store/retrieve your data because of ops, retrieval fees, and egress (if going to the internet). We feel like immediate availability is a compelling advantage of our product.
AWS S3 Glacier is the same $0.004/GB/month and requires the same minimum of 90 days, but retrieval takes "from 1 minute to 12 hours". They also have large retrieval costs (on top of the regular egress to the internet) and API call charges.
AWS S3 Deep glacier is only $0.00099/GB/month, but requires it to be stored 180 days and also have operation/retrieval fees. "For long-term data archiving that is accessed once or twice in a year and can be restored within 12 hours"
https://aws.amazon.com/s3/pricing/
We feel like the immediate availability of our offering is compelling and a competitive advantage over glacier.
> Is there a forum/discord where the community can discuss/learn?
Not yet, we will have one created soon.
We also purchase storage in datacenters.
I answered the parent.
Storage comes from services that we offer to end consumers. In exchange for our services they agree to let us use the unused storage on device, i.e. (https://crowdstorage.com/products/device-backup/). We plan on expanding to many more devices.
Storage also comes from being able to transparently leverage more traditional storage that we purchase from various providers.
We can seamlessly leverage more traditional storage as well as distributed endpoints. So in a way yes we can 'seed' it. We will likely wait until we have enough storage in a region before launching there.
> the egress pricing seems a little disingenuous
I have made small edits to the website to make it clearer it is 100% of data stored is free egress. This is definitely something we will focus on in the redesign.
We plan on launching regions outside of the U.S. that only store data outside of the U.S. soon.
> Also, how is the data encrypted? "State of the art encryption" is just marketing fluff :)
AES256 and/or xsalsa20poly1305.
You can also use SSE-C to provide our servers with a key to encrypt the data (which our servers then promptly forget). https://docs.aws.amazon.com/AmazonS3/latest/userguide/Server...
What region in particular interests you?
We are currently redesigning our website and this will definitely be something we focus on making more upfront and clearer.
Our website is right now being redesigned and your comments here are helpful to help us know where we need to improve!
We are working on getting as much content up on the website as we can and telling more about us!