Robot | Path | Permission |
GoogleBot | / | ✔ |
BingBot | / | ✔ |
BaiduSpider | / | ✔ |
YandexBot | / | ✔ |
User-agent: * Disallow: Sitemap: |
Title | David |
Description | I’m David Xia. I write software and occasionally |
Keywords | N/A |
WebSite | davidxia.com |
Host IP | 185.199.111.153 |
Location | - |
Site | Rank |
US$1,003,924
Last updated: 2023-05-07 12:59:56
davidxia.com has Semrush global rank of 10,542,937. davidxia.com has an estimated worth of US$ 1,003,924, based on its estimated Ads revenue. davidxia.com receives approximately 115,838 unique visitors each day. Its web server is located in -, with IP address 185.199.111.153. According to SiteAdvisor, davidxia.com is safe to visit. |
Purchase/Sale Value | US$1,003,924 |
Daily Ads Revenue | US$927 |
Monthly Ads Revenue | US$27,801 |
Yearly Ads Revenue | US$333,612 |
Daily Unique Visitors | 7,723 |
Note: All traffic and earnings values are estimates. |
Host | Type | TTL | Data |
davidxia.com. | A | 1798 | IP: 185.199.111.153 |
davidxia.com. | A | 1798 | IP: 185.199.108.153 |
davidxia.com. | A | 1798 | IP: 185.199.109.153 |
davidxia.com. | A | 1798 | IP: 185.199.110.153 |
davidxia.com. | NS | 1800 | NS Record: dns2.registrar-servers.com. |
davidxia.com. | NS | 1800 | NS Record: dns1.registrar-servers.com. |
davidxia.com. | MX | 1800 | MX Record: 5 alt2.aspmx.l.google.com. |
davidxia.com. | MX | 1800 | MX Record: 1 aspmx.l.google.com. |
davidxia.com. | MX | 1800 | MX Record: 10 aspmx2.googlemail.com. |
davidxia.com. | MX | 1800 | MX Record: 10 aspmx3.googlemail.com. |
davidxia.com. | MX | 1800 | MX Record: 5 alt1.aspmx.l.google.com. |
davidxia.com. | TXT | 1799 | TXT Record: keybase-site-verification=yJtVH3J8Mex1PB3zzY8F0YORKGA1DG38kGkgE1dHpRo |
davidxia.com. | TXT | 1799 | TXT Record: v=spf1 include:_spf.google.com ~all |
davidxia.com. | TXT | 1799 | TXT Record: google-site-verification=Mjb7Ejl9iNJPfQIDcBl0-_iYndl1VcahrjUh2civg8s |
Toggle navigation David Xia About Work Contact Benchmarking Kafka and Google Cloud Pub/Sub Latencies August 18, 2021 | By David Xia I’m helping a recently acquired team at work figure out if they can migrate from Kafka to Google Cloud Pub/Sub. Part of the exploration was figuring out the change in latencies, if any, from switching. The team’s production setup is like this. They paid an external company called Confluent to run a managed Kafka cluster in AWS Oregon. This is the same region where this team ran all their backend services. Part of their migration also involves switching their workloads from AWS Oregon to GCP us-central1. If they choose to migrate to Pub/Sub, their services will be publishing and subscribing to messages across cloud providers and regions. So my latency benchmarks took that into account. All their services are written in Golang. Services run as containers in AWS Elastic Container Service. I defined latency as the time elapsed from when a message is published |
HTTP/1.1 301 Moved Permanently Server: GitHub.com Content-Type: text/html Location: https://www.davidxia.com/ X-GitHub-Request-Id: D1B0:8D42:32485A:6D02C5:617A0884 Content-Length: 162 Accept-Ranges: bytes Date: Thu, 28 Oct 2021 02:18:44 GMT Via: 1.1 varnish Age: 0 Connection: keep-alive X-Served-By: cache-stl4825-STL X-Cache: MISS X-Cache-Hits: 0 X-Timer: S1635387525.783018,VS0,VE33 Vary: Accept-Encoding X-Fastly-Request-ID: b7a220a3adced1128363f4201c42f52c520007ba HTTP/2 200 server: GitHub.com content-type: text/html; charset=utf-8 last-modified: Wed, 18 Aug 2021 14:07:13 GMT access-control-allow-origin: * etag: "611d1411-e4df" expires: Thu, 28 Oct 2021 02:28:44 GMT cache-control: max-age=600 x-proxy-cache: MISS x-github-request-id: CB2C:602E:6FE801:ADFFAD:617A0884 accept-ranges: bytes date: Thu, 28 Oct 2021 02:18:44 GMT via: 1.1 varnish age: 0 x-served-by: cache-chi21122-CHI x-cache: MISS x-cache-hits: 0 x-timer: S1635387525.915904,VS0,VE26 vary: Accept-Encoding x-fastly-request-id: 43e7c3f2d709c4c92edf7bc4bf709e1ddff46cb0 content-length: 58591 |
Domain Name: DAVIDXIA.COM Registry Domain ID: 1556153945_DOMAIN_COM-VRSN Registrar WHOIS Server: whois.namecheap.com Registrar URL: http://www.namecheap.com Updated Date: 2021-04-19T06:35:05Z Creation Date: 2009-05-19T02:06:17Z Registry Expiry Date: 2022-05-19T02:06:17Z Registrar: NameCheap, Inc. Registrar IANA ID: 1068 Registrar Abuse Contact Email: abuse@namecheap.com Registrar Abuse Contact Phone: +1.6613102107 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Name Server: DNS1.REGISTRAR-SERVERS.COM Name Server: DNS2.REGISTRAR-SERVERS.COM DNSSEC: unsigned >>> Last update of whois database: 2021-09-15T20:31:11Z <<< |