# Production deployment **URL:** \ **Category:** Using FoundationDB\ **Created:** [June 20, 2018, 12:17am UTC](https://forums.foundationdb.org/t/production-deployment/522 "2018-06-20T00:17:52Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![amirouche](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/amirouche/32/2096_2.png) [@amirouche](https://forums.foundationdb.org/u/amirouche)\ **Post date:** [October 12, 2021, 9:51am UTC](https://forums.foundationdb.org/t/production-deployment/522/8 "2021-10-12T09:51:41Z")
> [@baiwfg2](#): > > use machine resources efficiently to achieve best performance. There is trick that was used by many existing FDB users: do not shoot for the best bare performance (e.g. transaction latency) from the start. Instead 1) benchmark your setup a) bare fdb cluster b) and, application using fdb cluster, 2) [secure monitoring](https://forums.foundationdb.org/t/what-do-you-monitor/184) (e.g. AFAIU available disk space is very top priority) 3) configure the backup system 4) and plan and script a recovery plan. > Make it work, make it right, then make it fast FDB provides an awesome potential for growth both from a number of user perspective, AND from a product feature perspective, there is a clear way to scale-up, but to scale-up you need to deliver, and FDB is also great to deliver complex features even without SQL layer. Getting a good grasp on the public interface whatever the programming language is very economical. --- _[View the full topic](https://forums.foundationdb.org/t/production-deployment/522)._