acache.io/index.html at main · always-cache/acache.io · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
<!DOCTYPE html>
<html>
<meta charSet="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">

<head>
  <title>acache.io - 100% cache hit rate at the edge</title>
</head>
<style>
  :root {
    --nord0: #2e3440;
    --nord0-a: #2e344080;
    --nord1: #3b4252;
    --nord2: #434c5e;
    --nord3: #4c566a;
    --nord4: #d8dee9;
    --nord5: #e5e9f0;
    --nord6: #eceff4;
    --nord7: #8fbcbb;
    --nord8: #88c0d0;
    --nord9: #81a1c1;
    --nord10: #5e81ac;
    --nord11: #bf616a;
    --nord12: #d08770;
    --nord13: #ebcb8b;
    --nord14: #a3be8c;
    --nord15: #b48ead;

    --color-bg: var(--nord0);
    --color-fg: var(--nord6);
    --color-body: var(--nord1);
    --color-accent: var(--nord11);

    --font-text: -apple-system, BlinkMacSystemFont, avenir next, avenir, segoe ui, helvetica neue, helvetica, Ubuntu, roboto, noto, arial, sans-serif;
    --font-heading: var(--font-mono);
    --font-mono: Menlo, Consolas, Monaco, Liberation Mono, Lucida Console, monospace;

    --max-width: 1080px;
    --margin: 2rem;
    --margin-extra: max(calc(var(--margin) * 4), 20vh);
    --margin-more: calc(var(--margin) * 4);
    --margin-double: calc(var(--margin) * 2);
    --margin-half: calc(var(--margin) / 2);

    --shadow: 0 0.25rem 0.5rem var(--nord0-a);
  }

  body {
    padding: 0;
    margin: 0;
    font-family: var(--font-text);
    background: var(--color-bg);
    color: var(--color-fg);
  }

  h1,
  h2,
  main>h3 {
    font-family: var(--font-heading);
  }

  header {
    background: var(--color-bg);
    padding: var(--margin-extra) clamp(2rem, -6rem + 20vw, 6rem);
    contain: layout;
  }

  h1,
  h1+p {
    max-width: max-content;
    margin-inline: auto;
  }

  h1 {
    font-size: clamp(2.5rem, 2rem + 2.5vw, 5rem);
  }

  header p {
    font-size: clamp(1.25rem, 1.15rem + 0.5vw, 1.75rem);
    line-height: 1.75;
  }

  code {
    background: var(--color-accent);
    font-weight: 700;
    padding: 0.25ch 0.5ch;
    margin-inline-end: 0.5ch;
  }

  main {
    padding-inline: max(var(--margin), calc(50% - var(--max-width) / 2));
    line-height: 1.5;
    background: var(--color-body);
    contain: layout;
  }

  h2 {
    text-align: center;
    margin-block: var(--margin-more) var(--margin-double);
    border-bottom: 1px solid var(--color-accent);
    padding-bottom: 0.5em;
  }

  h3 {
    margin-block: var(--margin-double) var(--margin);
  }

  a {
    color: inherit;
  }

  .center {
    width: max-content;
    max-width: 100%;
    margin-inline: auto;
    box-sizing: border-box;
  }

  .cards {
    margin: 0;
    padding: 0;
    list-style: none;
    display: grid;
    grid-template-columns: repeat(auto-fit, minmax(min(100%, 300px), 1fr));
    gap: var(--margin);
  }

  .card {
    background: var(--color-bg);
    padding: var(--margin);
    box-shadow: var(--shadow);
  }

  .card--alt {
    background: var(--nord4);
    color: var(--nord0);
    box-shadow: 0 0.75rem 1rem var(--nord0);
    padding: 2rem;
    padding: clamp(2rem, 1rem + 5vw, 3rem);
  }

  .card> :first-child {
    margin-top: 0;
  }

  .card> :last-child {
    margin-bottom: 0;
  }

  details {
    margin-block: var(--margin);
  }

  summary {
    font-size: 1.125rem;
    cursor: pointer;
  }

  .cta {
    font-family: var(--font-heading);
    text-align: center;
    display: block;
    margin-block: var(--margin-double) var(--margin-more);
  }
</style>

<body>
  <header>
    <h1>Proactive caching for the web</h1>
    <p>
      <code>acache</code>
      is a new type of CDN enabling a 100% cache hit rate at the edge
    </p>
  </header>
  <main>
    <h2>Features</h2>
    <ul class="cards">
      <li class="card">
        <h3>Proactive caching</h3>
        <p>Your content is always fresh in the cache. Instead of purging expiring content, it is updated from the
          origin. Your content is always served from the cache - and always fresh.</p>
      </li>
      <li class="card">
        <h3>On-demand updates</h3>
        <p>When content is updated, you can notify our CDN of the changes either via special HTTP headers or PURGE
          requests. Or just update everything at once when your are finished with your changes.</p>
      </li>
      <li class="card">
        <h3>Cache everything</h3>
        <p>All of your content is cached according to the HTTP caching specification (RFC 9111). But you also have the
          possibility to cache any other request, such as POST requests. So you can cache e.g. your GraphQL queries or
          complex POST calculations.</p>
      </li>
    </ul>
    <h3 class="center">Other features</h3>
    <ul class="center">
      <li>HTTP/2</li>
      <li>Automatic SSL</li>
      <li>Page Rules</li>
      <li>Instant purge</li>
      <li>CNAME configuration (with redirects)</li>
      <li>Root domain configuration</li>
      <li>HTTP caching standard compliance</li>
      <li>Brotli compression <em>(coming soon)</em></li>
      <li>Image optimization <em>(coming soon)</em></li>
      <li>IPv6 <em>(coming soon)</em></li>
    </ul>
    <h2>Use cases</h2>
    <ul class="cards">
      <li class="card">
        <h3>Create a static version of your site</h3>
        <p>We never evict (invalidate in HTTP caching speak) content from the cache. Rather, all content is kept in the
          cache until instructed otherwise. This means you can e.g. take your origin server completely offline without
          worrying about the availability of your site.</p>
        <em>Example customer: SaaS company spinning up their WordPress instance about once per month to make changes to
          their marketing site.</em>
      </li>
      <li class="card">
        <h3>Cache complex queries and API responses</h3>
        <p>We cache all read requests - including POST requests that only read content. If a response is the same every
          time and causes no side effects, it will be served from cache. This means you can enjoy lightning-fast speeds
          even for e.g. GraphQL queries and complex API requests.</p>
        <em>Example customer: 3D modeling company caching gigabytes of renders based on dozens of different inputs.</em>
      </li>
      <li class="card">
        <h3>Update dynamic content on demand</h3>
        <p>Sometimes content or data changes, in which case we update the cache where needed. The next time someone
          requests the changed content, the updates will already be in the cache. This means you can cache even the most
          dynamic content while always keeping everything up to date.</p>
        <em>Example customer: Financial services company keeping their customer portal with slow 3rd party dependencies
          entirely in cache.</em>
      </li>
    </ul>
    <h2>Frequently Asked</h2>
    <details class="card">
      <summary>I'm trying out your CDN, but my PageSpeed Insights performance score doesn't change - why?</summary>
      <p>
        In short, because the tests do not really measure network performance. Also, site performance depends on a lot
        of other factors as well, such as the amount of images and JavaScript loaded.
      </p>
      <p>
        PageSpeed Insights (i.e. Lighthouse) and other similar tools artificially slow down the network while testing a
        site, so you won't necessarily see the (very real) network performance improvements in these tools. The best way
        to test your site is to simply browse it yourself and see the difference.
      </p>
      <p>
        One way to see the network performance of your site is to check the Chrome User Experience reports (CrUX) e.g.
        by checking your site on <a href="https://pagespeed.web.dev" target="_blank">PageSpeed Insights</a>. A Content
        Delivery Network will directly impact the "Time To First Byte (TTFB)" metric seen in under "Discover what your
        real users are experiencing". This metric shows how long it takes your server to start responding to a real user
        request, and improvements here will translate to better performance directly.
      </p>
    </details>
    <details class="card">
      <summary>How can I be sure that my site will always be online after I switch to acache.io?</summary>
      <p>
        You don't. Sometimes entire networks or datacenters go down, and this is no different for acache.io. However, we
        have servers all around the world, many layers of monitoring, and many layers of fallbacks in case of issues.
        Our servers are located in the most secure and reliable datacenters available. We do have a 100% uptime
        guarantee (Service Level Agreement), and if we do not hit that we'll pay you back x10.
      </p>
    </details>
    <details class="card">
      <summary>How do I know my forms won't stop working or you won't cache pages for logged in users?</summary>
      <p>
        Our caching system is compliant with the HTTP caching standard (<a href="https://www.rfc-editor.org/rfc/rfc9111"
          target="_blank">RFC 9111</a>), which means we do not cache things your server tells us not to cache. As a
        general rule, things that cause side effects (e.g. change data, interact with another system such as email
        signups, and so on) are never served from the cache. Authenticated requests (with the "Authentication" HTTP
        header) are also never served from cache, and servers such as WordPress will tell us in the response not to
        cache responses that are authenticated via a cookie - e.g. the admin pages.
      </p>
      <p>
        Having said that, it is of course possible that servers do not follow the HTTP standards, which might lead to
        caching content that should not be cached. In these cases you can leverage our Page Rules to manually add the
        desired caching behavior for any page or other URL.
      </p>
    </details>
    <h2>Contact</h2>
    <strong class="cta"><a href="mailto:me@ericselin.dev">me@ericselin.dev</a></strong>
  </main>
</body>

</html>