I feel the pain of the author.
Have been using rook/ceph for the past year. We had some miserable times because of the different rook issues, especially the garbage collection bug that deleted more than it should.
Since 3 months now, I almost forgot we are using it. no issues at all, touch wood
Is there similar solution for manipulating tables and json? I am not a front-end developer, so when i am preparing a poc, it always takes me so long to parse data in a table. Someone must have done the same thing as htmx for tables, or i hope ...
I ran it once on an NFS disk. There must be some file locking happening I think. But I could read from multiple nodes, but for some reason the delete was failing (could not delete a database). Did not test the write as my app at that time was writing from one location only.
Anyone tested such HA scenario?
There is a good chance in 10 years we will look back and ask ourselves why the heck it took us so long to allow the genetically engineered chestnuts.
There is a big difference between genetic engineering to remove a species from existence vs reversing a bad thing we did and protect a species from going extinct. Our duty is to protect nature from us, and not not intervening when we destroy it. We did this accidentally by introducing the fungus. It is therefore Our duty to protect the chestnut by any means we have to reverse the damage we did, and restore equilibrium
binoculars cant go too far, the diameter is too small to allow enough light to be concentrated into your eye.
With binoculars, u can look at the moon. boring.
with a telescope, well u can see the planets live and take amazing photos
just make sure the diameter is as large as you can afford. Watching Saturn with its ring and moons is something i still remember 20 years later. Definitely a good investment
I think that technology used needs to be chosen based on today's needs and not tomorrow's. Startups that decide to deploy 5 containers on kubernetes make me cry. The time and cost to operate and maintain this beast is beyond any estimate compared to even hosting each container on a seperate vm.
This read was very satisfying, thank you
Choose boring technology, and every other person can copy your work.
Choose exciting new technology, you will be able to have features that few can replicate, or it will take them more time to do so.
The question should be, are the features you need important for your business or have a supporting role only? U dont need to re-invent the wheel and use the greatest and latest to run a database. But u definitely need to have a cutting edge feature that others will have tough time building.
Search for the late Christensen Clayton, who quoted "disruptive technologies". He has many youtubes great for a Sunday.
Design your architecture for the acceptable downtime. We all want 0 downtime, but it happens. You really need to understand what you are building for. Calculate the time of downtime you are fine with. for 99.5% it is >3h but for 99.9 it is 43m. and 99.95 it goes down to 20m per month.
So the less time you have allowed, the less time you have to react to a problem. So how long will it take you to turn on your pc on a weekend and try to figure out what is the source of downtime? so if you plan to go above 99.95 things will really get tough, and you will have to do major restructuring to reach this, as you cant allow failures.
So If you need 98% or 99.99% availability, your design will be very different. When you start designing for >99.97% stuff will get complicated.
It is surprising that windfarms are freezing. Here in Quebec, we have windfarms that have more than 6 months a year of snow and temperatures much below the freezing point. How can they freeze? they dont use water or gaz or oil.
It is only a fan and dynamo. Did water seep inside and freeze it?
nothing of security threat I guess. It uses your permissions, to modify the current permissions for different product. If u do have permissions to modify things, then this will work. if you have no permissions, it will fail.
So can it be used with bad intention, yes. But if I am a hacker, would i want to open all the available doors? or choose 1 or 2 doors only instead and keep the rest as is!!
Nice review. Bit too technical for me.
For persistence, a function can use a disk (shared or not) or a database (in memory or not)
did not get which is used here.
The approach here is that serverless should be planned at the application level. There is another way, make sure the infrastructure handles serverless. All in all, I wish there was examples for this
it depends on the position you are hiring for. Is it a position that needs solving problems with new technology? or is it to maintain a 5 years old application used by 1 million paying customer? each needs a different personality and maybe a different type of talent
Companies like deloitte sees the CDC as a big cow that needs milking. They will never finish the job.
It is like going to the hospital and tell the doctor I have a great insurance. The Doctors will do every possible procedure. It is better to check.
CDC needs to employ developers and do the job internally.
It is nice to sue all of those companies for colluding. But can't you just import those drugs for less from India or other cheap drug producing country?
I am not sure the problem lies in manufacturing. The system is rigged between the insurance companies and the medical system and the middle men!!
Offering a cheaper cost, means more money for the middle men probably
I dont know if manufacturing is the problem. Cant you import drugs from India or other country with cheap off label drugs?
The system is built to prey on the sick, it has nothing to do with manufacturing.
I like his idea, but doubt it will work