Last weekend I participated in a workshop where Peter H Diamandis described what Moonshot means. To better understand, I take his picture.
Many times organizations looking for 10% cost saving, 10% improvement, but how about 10x?
I studied organizations for many years, and I concluded that most organizations are not open to Moonshot changes. The reason simple, if you make 10x changes, then your next year's target will be the same. If you have a manager who works at your current company for a longer time, you could find more difficulty! He/she will not be able to describe to his/her boss why didn't do this before if it is possible.
To be able to utilize these solutions, you need to be on a green organization evolutionary level.
The video above gives you answers, why chasing profit on a lower level of evolution will not give the same results as at a more evolved organization.
After this introduction, I now turn to the main topic of this article.
In the past decade, I had a lot of work designing a database consolidation platform. Now, technology reached a new level, which gives exceptional possibilities! New servers can host 1 petabyte NVMe disks. If we are talking about Oracle RDBMS, you can use great solutions like Flashgrid.
Network operation costs significant time in response time. You can utilize low latency networks like Infiniband, but it will still use time. One strategy could be if you can serve requests from local storage. Just think about you can buy enterprise storage, but its interface, which connects to the server, still costs time. You can utilize NVMe instead of SSD in the storage, but the interconnect latency will much higher. Here we arrive at the next mindset! Simplification! Try to eliminate as many layers as you can! Every layer carries a level for error, and it can fail — less level of layers, less error possibility, and faster error detection.
Use hardware level functions always as you can!
An excellent example is the new NVIDIA Bluefield network adapter, which can take significant time-consuming tasks.
And I kept the last the most significant of all! Don't be afraid to utilize an open-source database! There you have the full control of these possibilities!
I know this is the hardest! You need to take responsibility! Much more comfortable having a phone number you can ask in case of error, and you can point fingers, but I have bad news! In the end, none of your customers will care about whose fault is the service outage; you will be responsible! If you are responsible, not more comfortable to have full control? If you have an engineering background and a creative problem-solving mindset, you will be in a better situation!