r/akashnetwork • u/Weak_Win_2540 • Nov 29 '21
๐จโ๐ป Developer Thoughts after my 3-week experience of Akash
I work as a (pretty ordinary) software engineer and have been trying out Akash for 3 weeks now on my free-time. I thought I'd share my experience to those who don't have the time to try Akash themselves.
Just a note: I had a limited time to research the topics concerned, please take this as a N=1 sample of random unskilled new user rather than justified criticism. Also, in my past experience most problems that I had were caused by my own error or misunderstanding, not by a bug in the service. In addition, I was (mostly) using Akashlytics Deploy, which isn't the same as the Akash network.
So here we go:
Overall hosting on Akash feels effortless and powerful, also private because I haven't given out any personal information. Based on my feelings, I'd prefer Akash to centralised services.
I enjoyed (and keep enjoying :)) the cheap price for hosting, although in my case and with my quick calculations the price seemed slightly higher than what was mentioned on Akashlytics price compare but still cheaper than its centralised counterparts. I'm not familiar how exactly the price is determined on Akash.
Akashlytics Deploy is excellent! It makes it easier to learn and understand the lease/deployment flow compared to the command line interface. Also, it calculates stuff like cost/month and time left for you, which is very helpful. Wish I could send AKT with Akashlytics Deploy, though.

The community on Discord is helpful though maybe not that big yet. Primary ways to look for help would be searching from Discord chats, maybe googling a bit and finally asking directly on Discord. There are still plenty of areas that haven't been well covered by documentation. I'd imagine that it's still a bit hard to do stuff on your own on Akash, unless you're an expert.
And here are some problems that I encountered.
Some network nodes seem slow to respond which can be frustrating until you learn to switch the node in the settings. When the network is working fast, using it feels pretty good though. When the it's slow, simply refreshing your wallet balance could take 5 seconds (fast being 0.3 ~ 0.5 seconds). The sluggishness was there with other deployment tools too, so that is not likely a problem of Akashlytics Deploy. It is hard to guess the reason. Maybe I'm physically far from most nodes? or some validators are running nodes with low specs?
After closing an old lease and creating a new with the same hostname, deployment wouldn't succeed for 12+ hours due to "hostname not allowed: Host already in use" error. That forced me to create a new subdomain and redirect the root there until the error vanished, otherwise there would have been downtime. So in the end, this got solved just by waiting.
At one point, I became unable to re-deploy and got a generic manifest error with no details. After 24 hours of persistently getting the same error, I decided to create a new lease and the same exact manifest worked there just fine (then closed the old lease). Luckily, you lose nothing for closing a lease, you only pay for the time the server was running + minimal transaction fees and you get the rest of your locked AKT back. Therefore, it's easy to play around with different setups. Making a new lease was my go-to whenever something wasn't working as I expected, kinda like rebooting the computer.
There was some issue of not getting any bids for one or two days, and on Discord it seemed like it was the case for others too. Maybe the network had temporarily run out of hosts? In that case, there should probably be some informative response.
I ended up giving up on HNS domains pretty fast, if I remember correctly, SSL with HNS domain is not well supported currently. Also, a 2-week auction time was quite a wait. Good thing I could insta-buy some random HNS domain for testing purposes on Namebase, but couldn't choose the domain name freely.
There was an apparent need for Cloudflare to get the domain root (e.g example.com) associated with the server's public address. For those willing to use a centralised service it isn't too bad and the setup was really quick. For the others, your only option may be to use a subdomain (e.g. app.example.com) to point to your akash server. E: Oh, also I think I quit HNS domains because I couldn't get the HNS domain root point to the server. I could only point a subdomain of the HNS domain to the server.
But these problems aren't anything that time won't fix. After all, Akash was released only half a year ago. Overall, the quality of the ecosystem seems good! I also understand and 100% agree that creating new features (roadmap 2022) is of much higher priority than polishing the current system. The competition in crypto is harsh, there is no time for resting or doing the wrong things.
If anyone is interested in what I was doing this whole time, I created a dashboard for crypto twitter follower growth (Github). By the way, the domain I originally wanted was crypto-twitter-dashboard.com, but Namecheap wouldn't let me easily take that and warned me of using "Twitter" in the domain. :) Therefore just gave in and took crypto-dashboard.info
