Do we have to change our applications to use Silk?
No. Silk sits between your databases and the cloud’s native infrastructure, and databases connect to it over standard iSCSI built into the operating system. Teams lift and shift existing applications and can optimize them before, during or after migration.
Which clouds and databases does Silk support?
Silk runs on AWS, Microsoft Azure and Google Cloud, deployed from the cloud marketplaces into your own account. It accelerates I/O-intensive databases such as Microsoft SQL Server, Oracle and PostgreSQL, and the applications built on them.
How can Silk be faster and less expensive at the same time?
Native clouds tie storage performance to VM size and disk tier, so teams overprovision to get I/O. Silk decouples the two: you right-size VMs and database licenses for the application, and data reduction lowers the capacity you pay for. In Forrester’s study, the composite organization cut cloud storage costs by 50%.¹
Can analytics, dev/test and AI use production data without slowing production?
Yes. Silk creates space-efficient, application-consistent copies of production data in minutes. They run alongside production at full speed without affecting the production system or duplicating storage.
What happens when the underlying cloud infrastructure fails?
Silk’s scale-out architecture has no single controller to fail. It detects infrastructure issues and repairs itself transparently to the workload, supports multi-zone designs, and recovers from logical corruption or ransomware in minutes rather than hours.
How do we prove the performance in our own environment?
Start with a proof of concept on your own workloads. Silk architects help size the environment and test it under realistic load and failure conditions.