search

HTTPArchive / almanac.httparchive.org

HTTP Archive's annual "State of the Web" report made by the web community
https://almanac.httparchive.org
Apache License 2.0
614 stars 176 forks source link

CDN 2021 #2159

Closed rviscomi closed 2 years ago

rviscomi commented 3 years ago

Part IV Chapter 21: CDN

CDN illustration

If you're interested in contributing to the CDN chapter of the 2021 Web Almanac, please reply to this issue and indicate which role or roles best fit your interest and availability: author, reviewer, analyst, and/or editor.

Content team

Lead Authors Reviewers Analysts Editors Coordinator
@Navaneeth-akam @Navaneeth-akam @boosef @jzyang @keane234 @paulcalvano @jzyang @rviscomi
Expand for more information about each role - The **[content team lead](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Content-Team-Leads'-Guide)** is the chapter owner and responsible for setting the scope of the chapter and managing contributors' day-to-day progress. - **[Authors](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Authors'-Guide)** are subject matter experts and lead the content direction for each chapter. Chapters typically have one or two authors. Authors are responsible for planning the outline of the chapter, analyzing stats and trends, and writing the annual report. - **[Reviewers](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Reviewers'-Guide)** are also subject matter experts and assist authors with technical reviews during the planning, analyzing, and writing phases. - **[Analysts](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Analysts'-Guide)** are responsible for researching the stats and trends used throughout the Almanac. Analysts work closely with authors and reviewers during the planning phase to give direction on the types of stats that are possible from the dataset, and during the analyzing/writing phases to ensure that the stats are used correctly. - **[Editors](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Editors'-Guide)** are technical writers who have a penchant for both technical and non-technical content correctness. Editors have a mastery of the English language and work closely with authors to help wordsmith content and ensure that everything fits together as a cohesive unit. - The **[section coordinator](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Section-Leads'-Guide)** is the overall owner for all chapters within a section like "User Experience" or "Page Content" and helps to keep each chapter on schedule. _Note: The time commitment for each role varies by the chapter's scope and complexity as well as the number of contributors._ For an overview of how the roles work together at each phase of the project, see the [Chapter Lifecycle](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Chapter-Lifecycle) doc.

Milestone checklist

0. Form the content team

1. Plan content

2. Gather data

3. Validate results

4. Draft content

5. Publication

Chapter resources

Refer to these 2021 CDN resources throughout the content creation process:

📄 Google Docs for outlining and drafting content 🔍 SQL files for committing the queries used during analysis 📊 Google Sheets for saving the results of queries 📝 Markdown file for publishing content and managing public metadata

boosef commented 3 years ago

I can help review and/or edit! :)

Navaneeth-akam commented 3 years ago

I would like to be an author/co-author for this chapter

rviscomi commented 3 years ago

Hi @Navaneeth-akam thanks for your interest in this chapter! I've tentatively put you down as a reviewer as we wait for more interest from authors. Could you tell us about your experience with the CDN space?

jzyang commented 3 years ago

I'd like to sign up for reviewer and editor.

rviscomi commented 3 years ago

📟 paging 2019 contributors: @andydavies @colinbendell @yoavweiss @paulcalvano @pmeenan @raghuramakrishnan71

Would any of you be interested to contribute to the 2021 chapter? I'd especially like to see more 2019/2020 authors become 2021 reviewers to help ease the transition and similarly I think prior reviewers would make great 2021 authors, being familiar with the process already. And prior analysts would make excellent 2021 analysts 😁

Or is there anyone new you'd like to see?

rviscomi commented 3 years ago

@ianand @boosef were either of you interested in authoring this chapter?

rviscomi commented 3 years ago

⚠️ Still looking for more contributors to make this chapter viable, specifically authors and analysts. If we're unable to staff the chapter by May 31 we may have to close it and focus our efforts on other chapters.

ianand commented 3 years ago

@rviscomi def considering it. will have an answer to you before the deadline. was also considering the jamstack or performance chapters as well.

rviscomi commented 3 years ago

@ianand ok sounds great. Of the two chapters, Jamstack is the only other one in urgent need of an author. The Performance chapter is pretty well staffed.

Navaneeth-akam commented 3 years ago

Hi @Navaneeth-akam thanks for your interest in this chapter! I've tentatively put you down as a reviewer as we wait for more interest from authors. Could you tell us about your experience with the CDN space?

Hi @rviscomi , I've been in Akamai (leader in CDN technology) for close to 10yrs now and have worked as an implementation specialist for Akamai's CDN products ( for 4yrs), partly worked for the cloud security space in Akamai and also as a pre-sales engineer (for 5yrs). During this time, i have interacted with other players in CDN space (like Amazon Cloudfront, Cloudflare, BitGravity etc.,), the different architectures of CDN setup (centralized v/s distributed), experienced/involved in the evolution of CDN landscape from a simple "cache and deliver" network to a cloud security and serverless edge compute platform....which is where most CDN platforms today are evolving into and becoming an integral part of application architecture.

rviscomi commented 3 years ago

@Navaneeth-akam thanks for your interest in authoring this chapter! As the content team lead, you'll be responsible for the scope and direction of the chapter and keeping it on schedule. We automatically monitor the staffing and progress of each chapter based on the state of the initial comment so please keep that updated as you add new contributors and meet each milestone.

We've created a Google Doc for this chapter, which you're encouraged to use to collaborate with the content team on the initial outline, metrics, and ultimately the final draft.

Next steps for this chapter are:

There's not currently a section coordinator for this chapter, so I'll be periodically checking in with you directly to make sure the chapter is staying on schedule. Reach out here in this issue if you have any questions about the process.

More information about the content team lead and author roles and responsibilities are available for reference in the wiki if needed.

To anyone else interested in contributing to this chapter, please comment below to join the team!

rviscomi commented 3 years ago

@Navaneeth-akam @boosef @jzyang please be sure to request edit access to the CDN chapter doc and begin outlining the chapter content. The due date to have the outline complete is June 15 to ensure that we have enough time to update the testing pipeline with any additional metrics as needed before the crawl begins on July 1.

@Navaneeth-akam I've also sent you an invite to join the Almanac team on GitHub. You can accept by visiting https://github.com/HTTPArchive. Membership gives you the ability to update the top comment to keep the list of contributors and completed milestones up to date. Doing so helps us monitor each chapter's progress at a glance in #2179. 🙏

@HTTPArchive/analysts this chapter is also in need of an analyst, any help would be greatly appreciated!

Navaneeth-akam commented 3 years ago

@rviscomi Thanks for the details. I think I have received the edit access for Google Doc. Will be adding the list of topics for this chapter. I see that we are still missing an analyst for this chapter. While I'm trying to see if anyone who has been analyst before can help with it, it would be great if you have any suggestions here.

jzyang commented 3 years ago

I've already checked my access earlier and put my name down for Reviewer, I believe. :)

On Mon, Jun 7, 2021 at 2:17 AM Navaneeth @.***> wrote:

@rviscomi https://github.com/rviscomi Thanks for the details. I think I have received the edit access for Google Doc. Will be adding the list of topics for this chapter. I see that we are still missing an analyst for this chapter. While I'm trying to see if anyone who has been analyst before can help with it, it would be great if you have any suggestions here.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HTTPArchive/almanac.httparchive.org/issues/2159#issuecomment-855760936, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUDCLZSZJFWP7CDKZF563TTRSFEDANCNFSM43UFN3FA .

colinbendell commented 3 years ago

I'm happy to be a reviewer as well.

On Mon, Jun 7, 2021 at 11:33 AM jzyang @.***> wrote:

I've already checked my access earlier and put my name down for Reviewer, I believe. :)

On Mon, Jun 7, 2021 at 2:17 AM Navaneeth @.***> wrote:

@rviscomi https://github.com/rviscomi Thanks for the details. I think I have received the edit access for Google Doc. Will be adding the list of topics for this chapter. I see that we are still missing an analyst for this chapter. While I'm trying to see if anyone who has been analyst before can help with it, it would be great if you have any suggestions here.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/HTTPArchive/almanac.httparchive.org/issues/2159#issuecomment-855760936 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AAUDCLZSZJFWP7CDKZF563TTRSFEDANCNFSM43UFN3FA

.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HTTPArchive/almanac.httparchive.org/issues/2159#issuecomment-856040719, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMMERLY6VAAT5HPQ7DNOSLTRTRDVANCNFSM43UFN3FA .

rviscomi commented 3 years ago

Hey @Navaneeth-akam, could you give us a status update on the outline? It's looking like there are a few good topics as of now, but I'm not sure if you're still working on it. We were hoping to have it done by today. Could you check off Milestone 1 above when you're satisfied with it? Thanks!

rviscomi commented 3 years ago

@Navaneeth-akam just following up on the state of the outline. How's it going, and is there anything we can do to help?

rviscomi commented 3 years ago

@HTTPArchive/analysts this is the only chapter still without any analysts. Is anyone able to take this one on? 🙏

keane234 commented 3 years ago

Hi, I can helo for the review too.

Navaneeth-akam commented 3 years ago

@rviscomi : I had a chat with @paulcalvano few weeks back and he will help us with analysis on this. I have also updated few milestones based on current progress

Navaneeth-akam commented 3 years ago

Hi, I can helo for the review too.

Thanks @keane234 !!! Will update you in the list of reviewers

rviscomi commented 3 years ago

👋 Hi @Navaneeth-akam @paulcalvano, just checking in on the chapter progress. How is the analysis coming along?

rviscomi commented 3 years ago

Unchecking Milestone 2 until the draft PR is created

rviscomi commented 3 years ago

@Navaneeth-akam @paulcalvano adding the ASAP label back since Milestone 2 is long overdue (creating the draft PR was due on June 30). Any update on the analysis?

Also, @Navaneeth-akam do you still need additional contributors? If not you can remove the "help wanted" labels from the issue.

rviscomi commented 3 years ago

⛔ @Navaneeth-akam @paulcalvano this chapter is at serious risk of missing the launch. The analysis work for Milestone 3 was due yesterday but I'm not seeing any signs that it was ever started. I don't see a plausible way for this chapter to meet Milestone 4 (writing, reviewing, and editing the chapter) by the October 31 deadline unless the analysis is completely done by the end of next week. Are you both able to commit to that timeline? Otherwise we may need to close this chapter and focus on getting the viable chapters ready for launch, which I would hate to do.

paulcalvano commented 3 years ago

Hey @rviscomi , @Navaneeth-akam . I'll be working on the analysis for this today/tomorrow, so should have some progress to share shortly. Sorry for the delay!

jzyang commented 3 years ago

@rviscomi Well, I reached out to @Navaneeth-akam in June about this over Slack, after seeing no movement. He said he'd have something mid-June but I never heard back from him again with any other updates. I've checked back on the doc pages in August but I haven't seen any movements. I'm still available to help review this and other chapters, but nothing I've signed up for seemed to have texts available for review. @paulcalvano I don't think you indicated you had time to write anything this year though. Is that still true?

paulcalvano commented 3 years ago

@jzyang - I synced up with @Navaneeth-akam last week and we reviewed the queries that I'd be rerunning from 2019, and some new ones I needed to write. I've been the blocker on getting the analysis done - so apologies for that. Navaneeth is still planning on writing the chapter. I'm happy to help out wherever needed too.

jzyang commented 3 years ago

@paulcalvano good to hear from you! Yeah, let me know when you need my services. I'm on-call next week, starting Monday, so I will be busy but I should be available again the Monday after next.

rviscomi commented 3 years ago

Thank you both for the updates, and I'm glad to see the PR open now to track the queries. I'm optimistic that we can get this chapter back on track in time for launch.

Navaneeth-akam commented 3 years ago

@rviscomi : my apologies for not responding here. Have been busy for quite sometime. Paul has provided his analysis and last few queries are pending. I'll work on the draft ASAP and expedite the steps here to meet the deadline

Navaneeth-akam commented 3 years ago

@boosef @jzyang @keane234 : can you guys suggest some time next week to setup a call and start reviewing the draft? I have started drafting the CDN chapter and will be working on it over the weekend to have it available for the call.

boosef commented 3 years ago

@Navaneeth-akam nice! anytime on Monday, or sometime in the evening (IST) on Tuesday/Wednesday works for me!

Navaneeth-akam commented 3 years ago

@boosef : will wait for response from @jzyang and @keane234 to fix up a time :)

jzyang commented 3 years ago

Oh sorry, I just saw this. I already started making comments and some changes to the doc. I'm planning to finish my first round by end of day. I'm available for a call but I'm on PST time. I guess I can do Tues 8:30-9:30AM PST and 10:30AM-12PM PST (I believe that 9-10PM and 11PM-12:30AM IST) and I'm free on Wed from 9-10AM PST and 11AM-12PM PST. Tuesday I must end exactly at 9:30AM for a team meeting. I prefer Wed though. I don't relish waking up at 7:30AM on Tues to get ready for work.

On Thu, Oct 28, 2021 at 11:20 PM Navaneeth @.***> wrote:

@boosef https://github.com/boosef : will wait for response from @jzyang https://github.com/jzyang and @keane234 https://github.com/keane234 to fix up a time :)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HTTPArchive/almanac.httparchive.org/issues/2159#issuecomment-954461480, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUDCL4RWEBHALWROKXCG43UJI4KXANCNFSM43UFN3FA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

jzyang commented 3 years ago

Oh, and I guess I'm also available after 8PM PST Tuesday (since I'm at the office that day and that's usually when I get home) and I'm available after 6PM on Wednesday.

On Sun, Oct 31, 2021 at 9:10 PM Julia Yang @.***> wrote:

Oh sorry, I just saw this. I already started making comments and some changes to the doc. I'm planning to finish my first round by end of day. I'm available for a call but I'm on PST time. I guess I can do Tues 8:30-9:30AM PST and 10:30AM-12PM PST (I believe that 9-10PM and 11PM-12:30AM IST) and I'm free on Wed from 9-10AM PST and 11AM-12PM PST. Tuesday I must end exactly at 9:30AM for a team meeting. I prefer Wed though. I don't relish waking up at 7:30AM on Tues to get ready for work.

On Thu, Oct 28, 2021 at 11:20 PM Navaneeth @.***> wrote:

@boosef https://github.com/boosef : will wait for response from @jzyang https://github.com/jzyang and @keane234 https://github.com/keane234 to fix up a time :)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HTTPArchive/almanac.httparchive.org/issues/2159#issuecomment-954461480, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUDCL4RWEBHALWROKXCG43UJI4KXANCNFSM43UFN3FA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Navaneeth-akam commented 3 years ago

Thanks @jzyang ! I have to write one more section in the google doc. I'll be writing it during evening hours in India today. In the meanwhile, you can review and edit rest of the sections. @boosef @keane234 : you guys can also review and add your comments in the google doc. If you have issues accessing the doc, let me know.

Navaneeth-akam commented 3 years ago

@jzyang : I have reviewed your comments and edits. The draft has been updated with the same. Would be helpful if you can verify the edits. Also, i have added the 2 sections to the draft (HTTP/2 and HTTP/3 Adoption and Conclusion). Please review the same.

boosef commented 3 years ago

@Navaneeth-akam I don't have edit access to the doc yet, so I'll leave some of my feedback here - I have a few minor suggestions that I can make in-line once the doc permissions have been modified. :)

boosef commented 3 years ago

Ok, yay. I now have access! (thanks @rviscomi 😁)

@Navaneeth-akam - I've gone through about half the document for now, will do the rest tomorrow. I've made all my edits in "Suggesting" mode, so I'm sorry if the number of comments seem a little overwhelming! Most of them are very minor edits, but I figured I'd start with the proofreading while going through the content. :)

Something I noticed was that the order in which topics are covered doesn't quite match what's mentioned in the Outline page - I know you're still working on the doc though, so let's chat and see if things need to be reordered/added once you're done? Miiight just be easier to do that part on a call, but happy to do this async also if that's more convenient for everyone. :)

Navaneeth-akam commented 3 years ago

@Navaneeth-akam I don't have edit access to the doc yet, so I'll leave some of my feedback here - I have a few minor suggestions that I can make in-line once the doc permissions have been modified. :)

  • I think it would be nice to have a section on how CDNs are still relevant even though most cloud platforms now have global pops, autoscale functionality etc. - perhaps pointing to the stats we have on perf, with and without CDNs (where can I find this data, btw? It's mentioned in the sheet, but I don't know where the graphs/tables actually are) would help here.
  • There's mention of Brotli and how CDNs help with with image and video management, serverless compute and web security, but no mention of why or what value users get from using that kind of functionality at the edge. Is this out of scope for the doc?
  • Along with TLS1.3 and h2, worth talking about how helpful CDNs have been in IPv6 adoption also.

@boosef : Thanks for your suggestions. Here are my responses:

  1. Since the crawling for web almanac is executed using a single node in US west coast, its a single point test if we have to measure performance. This off course has its limitations and the results may not be true representation of the performance impact each CDN is adding. Hence, to be fair and neutral on this, we are not including any performance data.
  2. Topics like serverless compute, Image and video management, web security are areas which we found is difficult to get info on by looking at only request-response parameters. The data we have today is based on the crawls that were executed. That limits the scope of what we can write about and how much info CDN providers are able to expose in public requests. For contect, we did explore option to send CDN specific debug headers in request to expose some data in response, but not every CDN supports such mechanism. Over that, for security reasons CDN's do block such attempts without the right authorizations. Hence, we dropped it.
  3. Brotli assessment is in the works. I'm waiting for analysis data to come in to write about it. Thats work in progress and will be covered :)
  4. Good suggestion on IPv6 adoption analysis. Totally missed this one. I'm checking with Paul (analyst) if we have the data for this. WIll keep you posted on this
Navaneeth-akam commented 3 years ago

Ok, yay. I now have access! (thanks @rviscomi 😁)

@Navaneeth-akam - I've gone through about half the document for now, will do the rest tomorrow. I've made all my edits in "Suggesting" mode, so I'm sorry if the number of comments seem a little overwhelming! Most of them are very minor edits, but I figured I'd start with the proofreading while going through the content. :)

Something I noticed was that the order in which topics are covered doesn't quite match what's mentioned in the Outline page - I know you're still working on the doc though, so let's chat and see if things need to be reordered/added once you're done? Miiight just be easier to do that part on a call, but happy to do this async also if that's more convenient for everyone. :)

Thanks for reviewing @boosef! I'll go thru the suggestions in google doc. Yes, the order of the topic may not match the outline I came up with. Quite a few topics went out of contention after we worked on technical feasibility to cover them. Hence, you see this discrepancy :)

Navaneeth-akam commented 3 years ago

@paulcalvano : let me know once we have the results for the last set of queries?

@rviscomi : we are in the final leg of the draft. The current draft is reviewed by @boosef and @jzyang. Their suggestions and recommendations were discussed and incorporated. Once the last few results of queries are in place, I'll draft the final piece for reviewing and editing.

Navaneeth-akam commented 3 years ago

@jzyang @boosef : I have drafted a new section in CDN Chapter for "Brotli Adoption". Please review and comment on the same. Also, i have made an addition to "CDN Adoption" section with new data of CDN adoption based on site popularity. Do review that section as well :)

jzyang commented 2 years ago

@Naveen Sharma @.***> should we be reviewing in the Google doc or should be do it in the git? I suggest git so we can get you closer to completion.

On Mon, Nov 15, 2021 at 5:26 AM Navaneeth @.***> wrote:

@jzyang https://github.com/jzyang @boosef https://github.com/boosef : I have drafted a new section in CDN Chapter for "Brotli Adoption. Please review and comment on the same.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HTTPArchive/almanac.httparchive.org/issues/2159#issuecomment-968909187, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUDCL5CDMZHPFBTG53W2FTUMEDBNANCNFSM43UFN3FA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

jzyang commented 2 years ago

Oh darn, I tagged the wrong person. @Navaneeth-akam https://github.com/Navaneeth-akam see previous comment. Sorry for the confusion @Naveen Sharma @.***> , please ignore!

On Mon, Nov 15, 2021 at 11:04 AM Julia Yang @.***> wrote:

@Naveen Sharma @.***> should we be reviewing in the Google doc or should be do it in the git? I suggest git so we can get you closer to completion.

On Mon, Nov 15, 2021 at 5:26 AM Navaneeth @.***> wrote:

@jzyang https://github.com/jzyang @boosef https://github.com/boosef : I have drafted a new section in CDN Chapter for "Brotli Adoption. Please review and comment on the same.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HTTPArchive/almanac.httparchive.org/issues/2159#issuecomment-968909187, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUDCL5CDMZHPFBTG53W2FTUMEDBNANCNFSM43UFN3FA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Navaneeth-akam commented 2 years ago

@jzyang : lets finish off the content in Google doc as i'm more comfortable modifying and editing it there. Once the doc is finalized, then we can submit it to git in one go

jzyang commented 2 years ago

@Navaneeth-akam https://github.com/Navaneeth-akam done.

On Mon, Nov 15, 2021 at 6:54 PM Navaneeth @.***> wrote:

@jzyang https://github.com/jzyang : lets finish off the content in Google doc as i'm more comfortable modifying and editing it there. Once the doc is finalized, then we can submit it to git in one go

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HTTPArchive/almanac.httparchive.org/issues/2159#issuecomment-969744665, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUDCL4ZYZHM36KDB46NUEDUMHBYHANCNFSM43UFN3FA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Navaneeth-akam commented 2 years ago

@jzyang @boosef : More edits and corrections made to the google doc draft. There were few charts that needed some correction and @paulcalvano helped with it today. I might have to do one more correction since one of the chart data might change. Will keep you guys posted on it

Navaneeth-akam commented 2 years ago

@jzyang : thanks for reviewing and editing. I have looked at your corrections and accepted them as required. @boosef : let me know once you do a final review of the draft. @paulcalvano : I know you are our analyst, but it would be great if you can read the draft and give me your thoughts :) @rviscomi : I'm happy with the content for CDN chapter. When we get final comments from @boosef , we should be good to merge this for publishing.