hassanmurtaza.com | Hassan Murtaza

Robots.txt Information

Robot	Path	Permission
GoogleBot	/	✔
BingBot	/	✔
BaiduSpider	/	✔
YandexBot	/	✔
User-agent: * Disallow: /wp-admin/ Allow:

Meta Tags

Title	Hassan Murtaza - DevOps & AWS
Description	Hassan Murtaza — AWS DevOps Professional and OpenSorcerer (pun intended) Hassan Murtaza — AWS DevOps Professional and OpenSorcerer (pun intended) ?. ? Home ? About ✉️ Contact Ingest Millions of Messages in the Queue using Serve
Keywords	N/A

Server Information

WebSite	hassanmurtaza.com
Host IP	104.21.89.238
Location	United States

Related Websites

                        Site
                        Rank
                    

More to Explore

hassanmurtaza.com Valuation

US$1,124

Last updated: 2023-05-11 06:28:40

hassanmurtaza.com has Semrush global rank of 0. hassanmurtaza.com has an estimated worth of US$ 1,124, based on its estimated Ads revenue. hassanmurtaza.com receives approximately 129 unique visitors each day. Its web server is located in United States, with IP address 104.21.89.238. According to SiteAdvisor, hassanmurtaza.com is safe to visit.

Traffic & Worth Estimates

Purchase/Sale Value	US$1,124
Daily Ads Revenue	US$1
Monthly Ads Revenue	US$31
Yearly Ads Revenue	US$373
Daily Unique Visitors	8
Note: All traffic and earnings values are estimates.

DNS Records

Host	Type	TTL	Data
hassanmurtaza.com.	A	299	IP: 104.21.89.238
hassanmurtaza.com.	A	299	IP: 172.67.191.237
hassanmurtaza.com.	AAAA	299	IPV6: 2606:4700:3034::6815:59ee
hassanmurtaza.com.	AAAA	299	IPV6: 2606:4700:3036::ac43:bfed
hassanmurtaza.com.	NS	86400	NS Record: amanda.ns.cloudflare.com.
hassanmurtaza.com.	NS	86400	NS Record: phil.ns.cloudflare.com.

HtmlToTextCheckTime:2023-05-11 06:28:40

Hassan Murtaza — AWS DevOps Professional and OpenSorcerer (pun intended) ?. ? Home ? About ✉️ Contact Ingest Millions of Messages in the Queue using Serverless Comment While working on one of the Serverless projects, We came across a problem where I needed to ingest millions of messages from an external API to Azure Storage Queue. We made a series of changes in my approach to reach the solution which worked for us and I believe it can be helpful to anyone who’s struggling with the same problem. We started with the approach where we were executing the Serverless function through the HTTP endpoint. We call it an Ingestion Function . The ingestion function would then hit an external API to get the messages and try to ingest it in Queue. Here is how my initial architecture looked like: If you see the architecture diagram, the single ingestion function is a bottleneck as it can only scale up-to specific limits. Also, we’re not utilizing the strength of the actual serverless function, which

HTTP Headers

HTTP/1.1 301 Moved Permanently
Date: Thu, 04 Nov 2021 05:55:55 GMT
Connection: keep-alive
location: https://hassanmurtaza.com/
CF-Cache-Status: DYNAMIC
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=iAnZ4S8w3ZyRKOv0wPUsm8Q%2FwsAsDOeg8z5Tvsfrc0oGlir4Zwyr7dwzcXPH01w3b7vAjaC3RsQmZzefgnbm67vAbaWEwXEywZ63FoPqF8E2NxAqvGplmxRIry1iywx5vmE9tg%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
Server: cloudflare
CF-RAY: 6a8b98a0e9002c6c-ORD
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400, h3-28=":443"; ma=86400, h3-27=":443"; ma=86400

HTTP/2 200 
date: Thu, 04 Nov 2021 05:55:56 GMT
content-type: text/html; charset=UTF-8
link: ; rel="https://api.w.org/"
vary: Accept-Encoding
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400, h3-28=":443"; ma=86400, h3-27=":443"; ma=86400
x-litespeed-cache: hit
cf-cache-status: DYNAMIC
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=kIp4ccjxRpvGFvYh6xGqeY9LWVkUA24xBvQ3zhvkgx7TH8upAdDWQHEt%2BLqQ9%2Fl37ueoyB2bPtMl1IgShaIOySjR6Tm6Gm4rX6tWoZXFhEJ4g4wbVqHUuGyETSiMk%2FMex2kVgg%3D%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 6a8b98a23edec560-ORD

hassanmurtaza.com Whois Information

Domain Name: HASSANMURTAZA.COM
Registry Domain ID: 2179661307_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.cloudflare.com
Registrar URL: http://www.cloudflare.com
Updated Date: 2021-08-08T23:06:19Z
Creation Date: 2017-10-27T09:18:43Z
Registry Expiry Date: 2022-10-27T09:18:43Z
Registrar: CloudFlare, Inc.
Registrar IANA ID: 1910
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: AMANDA.NS.CLOUDFLARE.COM
Name Server: PHIL.NS.CLOUDFLARE.COM
DNSSEC: unsigned
>>> Last update of whois database: 2021-12-22T07:52:28Z <<<

hassanmurtaza.com valuation and analysis