An essential for me
Overall Satisfaction with Cloudflare
For the main use case, we use Cloudflare as our DNS manager and main proxy for the most important domains and subdomains.
For secondary cases we use it to build reverse proxies for some "embedded" apps and to handle specific use cases like sitemap generation, connecting to GEO monitors and others
For secondary cases we use it to build reverse proxies for some "embedded" apps and to handle specific use cases like sitemap generation, connecting to GEO monitors and others
Pros
- DNS Management
- DDoS prevention
- Low latency implementations
Cons
- Interacting with logs usually requires setting up an extraction, doing simple queries on them could be out-of-the-box
- AI crawlers/bots monitoring can also use a better UX and allow for better drill downs
- It could have better tutorials for things like storage and workers
- Has being a key factor to stop possible attacks or malicious requests
- Has saved engineering time when mitigating attacks in a fast way
- Has helped reducing engineering time needed to build custom apps without using a subdomain
Cloudflare initial implementation is really straightforward and usually can be done by mid engineers without a lot of knowledge in infrastructure (at least the one related to DNS management and basic DDoS and WAF configuration)
Probably for more specific use cases (like building reverse proxies) a more experimented engineer would be needed.
Probably for more specific use cases (like building reverse proxies) a more experimented engineer would be needed.
Do you think Cloudflare delivers good value for the price?
Yes
Are you happy with Cloudflare's feature set?
Yes
Did Cloudflare live up to sales and marketing promises?
Yes
Did implementation of Cloudflare go as expected?
Yes
Would you buy Cloudflare again?
Yes


Comments
Please log in to join the conversation