What the paper says

Muruganandam Venkatachalam, M.Sc Digital Business, University of Salford, UK
6 days ago
4 min read

Application and Optimization Strategies of Cloud Services in Front end Engineering

Paper Under Review

Gu, Y. (2026). Application and optimization strategies of cloud services in front-end engineering. International Journal of Big Data Intelligent Technology, 7(1), 1–8. https://doi.org/10.38007/IJBDIT.2026.070101

Introduction

Cloud computing is a standard reference point for how software is built and delivered. The article maps how cloud infrastructure affects front-end performance, workflow, security, and architecture — claims this critique tests against the literature and direct CDN experience.

What the Paper Says

Gu (2026) argues cloud services benefit front-end engineering in four ways: CDNs and load balancing cut page-load times by 50–70%, citing AWS CloudFront's use across 100,000+ sites; CI/CD pipelines raise deployment frequency by over 30% and release efficiency by 40%; near-universal HTTPS, AWS IAM-style permissions, and GDPR/CCPA compliance secure data; and elastic compute, containers, and Kubernetes make systems more flexible, citing a Gartner reported 35% scaling gain. Three equations formalize these ideas, and Gu concludes cloud services make front-end systems faster, easier to build, more secure, and more flexible.

Critical Review: A Mini Literature Review

Where the paper's claims align with the literature

The core claims track the wider literature. Tyagi's (2020) CDN review finds edge caching and load balancing cut latency and improve scalability, supporting Gu's figures. Ccallo and Quispe-Quispe (2024) confirm CI/CD pipelines shorten release cycles — the same effect Gu reports. Figure 1's flow chart of the security and privacy protection process is also a genuine strength: laying out SSL/TLS, IAM, encryption, and GDPR/CCPA as one visual sequence communicates the security workflow more clearly than the prose does. Diagrams like this are exactly the kind of concrete artifact the paper could use more of.

Opportunities to strengthen the evidence

A key opportunity is methodological transparency. Gu (2026) reads like an empirical paper but states no methodology and no explanation of how its statistics were obtained. Figures like “over 100,000 websites” on CloudFront and a Gartner-attributed 35% scaling gain appear with no traceable source. For example a Google search put Akamai's count anywhere from roughly 18,500 companies, and Fastly's from about 748 customers — neither reflects the vendor's own figure. The three equations use notation of tested models with no derivation or validation, and the evidence leans almost entirely on AWS, with Cloudflare mentioned once and CDN companies like Fastly and Google Cloud CDN absent.

Additional considerations worth exploring

The paper treats cloud adoption as one-directional, with no mention of vendor lock-in, cost growth, or cold-start latency in server-less functions. Ccallo and Quispe-Quispe (2024) treat resource constraints as central to whether CI/CD gains materialize. Most benefits described apply equally to back-end systems.

A Practitioner's View: Metrics for Comparing CDN Vendors

The papers treatment of CDN vendors as interchangeable overlooks metrics that differentiate platforms. In my experience running Fastly and Akamai, Cache Hit Ratio (CHR) has run about 10% higher on Fastly, and PageSpeed testing has shown roughly a 20% page-load improvement on Fastly for the same site. Neither figure appears in Gu's paper, which treats CDN acceleration as one undifferentiated 50–70% gain regardless of vendor. The point is not that one platform is better; CHR and load-time deltas are exactly the comparative metric a paper on cloud optimization should use, rather than treating “the cloud” as a single stack.

A second axis is architectural: For example, Fastly's API-first model exposes CDN, edge compute, and WAF as APIs, and Varnish Control Language (VCL) lets engineers define edge logic as code — “edge as code” rather than configuration. Other CDN’s lean more on managed configuration, suiting teams without dedicated platform engineers. Gu (2026) paper never treats these design philosophies as a point of comparison.

Observability is a third axis: streaming logs in real time from the CDN, WAF, and edge services into enterprise platforms like Dynatrace and Splunk enables custom Real User Monitoring dashboards and Core Web Vitals tracking beyond a vendor's built-in reporting — a differentiator, not a ranking, since needs vary by team.

A fourth factor sits outside vendor choice: customer-side configurations and requirements. Configurations like TTL (time-to-live) settings determine cache duration at the edge — too conservative suppresses CHR, too aggressive risks stale content. Security policy works the same way: WAF rules, rate limiting, and bot management add edge processing, and poorly tuned rules introduce latency or block legitimate traffic. The paper treats provisioning as sufficient by itself, without acknowledging outcomes depend as much on configuration as on vendor.

The point is that CHR, edge-compute design, WAF integration, observability, and configuration choices are concrete axes for comparing CDN vendors — axes a paper on optimizing cloud services in front-end engineering should have used instead of treating cloud services as one category.

Overall Assessment

Gu (2026) is a readable orientation to cloud services in front-end engineering, correctly identifying categories the broader literature also treats as consequential. Its value is as an introductory survey rather than an evidence-based contribution, with room to grow on methodology, sourcing, and vendor-neutral comparison. Readers should treat its quantitative claims as illustrative and consult primary literature — Tyagi (2020), Ccallo and Quispe-Quispe (2024) — plus direct operational experience.

References

Ccallo, M., & Quispe-Quispe, A. (2024). Adoption and adaptation of CI/CD practices in very small software development entities: A systematic literature review. arXiv. https://doi.org/10.48550/arXiv.2410.00623

Tyagi, A. (2020). Optimizing digital experiences with content delivery networks: Architectures, performance strategies, and future trends. World Journal of Advanced Research and Reviews, 7(2), 401–417. https://doi.org/10.30574/wjarr.2020.7.2.0230