I honestly believe it could’ve done better if it wasn’t under Justin No Fun’s leadership.
I’d recommend using redis. In app caching can cause unexpected behavior to cache objects as they are modified between requests. You will need a solid in app caching architecture in order to make sure it works well. Redis not only works really well but also comes with cool features such as TTL. Spinning a redis instance is super tiny and optimized you could fit it in the same instance with your node app.
I expected it to be easier to produce block. "Just a small 5% increase every 5 days and we're golden". Boy where we wrong. After 7 months operation we finally produced our first block. Reward was decent, but until that first block you'll need a lot of patience. It takes some effort updating every now and then. So can't say for sure what you'll make. But we have a "very small" pool in comparison to others. But a lot bigger than 1k. So, it would be a good learning experience to set it up for sure. And thats your biggest value to be gained here I guess.
Interesting! is running a node different from running a Stake pool?
Helped me easily send money!
You don't have a bank account?
I do, I use crypto to send money abroad.
The nfts I've earned from staking have earned me so much I can't warrant buying other coins anymore
This is interesting, care to elaborate?
It's the right software/middleware to make 50 million documents searchable in seconds.
But if you think about it as a database or tell other technical people it's a database they will make incorrect assumptions about how it works and how safe the data is.
Almost everything you would expect to be true about an RDBMS is not true about Elasticsearch. It is not relational, it is not normalized, it is not ACID transactional, it is not centralized, it replicates data. If you need any of these properties then you still need a database in addition to a search index, and this is a very common use case.
Couldn’t agree more! To add more to this excellent answer, all operations that involve insert/update/delete records should come from an ACID db. For example if you need to update user data, then check user exist, and then update user data all using an ACID db, then have a way to sync to ES. I see a common mistake where engineers check user exist from ES data then update user data in an ACID db.
It is a full node, you shouldn’t use it unless you need to submit transactions directly to the network without using a third party node.
I am ok with it because I can submit transactions through the network. It took me in mid 2022 around 1.5 days to sync the entire node (65gb+ data) and 14gb+ ram used. Just a pro tip, I recommend 32gb ram and at least 256 ssd hard drive.
