So its all perplexed situation to make any conclusions.
34 karma · joined November 8, 2022
So its all perplexed situation to make any conclusions.
Suppose we had this AI at the dawn of internet, we would have google using this tech to search internet back then. We would have saved countless hours of search to fix a bug.
AI is having an Einstein in our pocket. Any one who had to develop/research on any topic, he has an Einstein level assistance ready to help you out. We are just at the dawn of the sci-fi era we always have imagined for. And AI will be our companion in this fast changing world: "Jarvis explain me how that thing works" , and you get somewhat of an idea about any new or complex subject, which otherwise would have taken days to comprehend.
government should release there own open source safety sdk, which others can simply include in there code, to adhere to minimum requirements.
otherwise this seems to me like Innovation killer bill, by eliminating small players out of equation.
DB should only contain key value pairs. Don't store big blobs as values in them. Store meta info(like network path, size, name...) for these blobs in values. Blobs sould be on some Network drives.
This way you can scale these two things independently. The client can locally store this meta info and won't need it again and again.
You can have some sort of analytics on these blob access and than replicate more copies accordingly of often accessed blobs, to get more read through out.
Use of "range" http headers to stream data can also be helpfull.
Zero copy is another concept to get the best through put. Familiarize yourself with it.
The easy and best solution is to store these blobs on some properity media server solution. As they do handle most of these optimization. Your database must only deliver meta data, which do contains cloud path to these blobs. it then becomes headache for these media server to scale your big blobs.