feat(repo): refactor blob storage pkg

[cyberhorsey]

This Pr brings Dani's blob-catcher software up to speed with our existing architectural patterns., fixed some bugs, and cleans up the code, as well as fixes logging.

It initializes an ethclient / db connection once, rather than for every event it finds, and as well, it gets events in batches (as before, it was getting infinite number of block data at once, which would cause it to crash if too many blocks). Then, when it is caught up, it subscribes to new blocks.

@adaki2004 can i take out MongoDB and make it MySQL? we already use MySQL in production, dont see the need for two different database. Or is there a reason we use Mongo here?

[m3shm]

What u mean by WIP

[cyberhorsey]

What u mean by WIP

work in progress. who are you?

[davidtaikocha]

@adaki2004 can i take out MongoDB and make it MySQL? we already use MySQL in production, dont see the need for two different database. Or is there a reason we use Mongo here?

imo we should also use MySQL for this service, can't any reason to maintain a new type of database?

[cyberhorsey]

@adaki2004 can i take out MongoDB and make it MySQL? we already use MySQL in production, dont see the need for two different database. Or is there a reason we use Mongo here?

imo we should also use MySQL for this service, can't any reason to maintain a new type of database?

don't think so, it was just started with Mongo. I will swap it out for MySQL.

[adaki2004]

@adaki2004 can i take out MongoDB and make it MySQL? we already use MySQL in production, dont see the need for two different database. Or is there a reason we use Mongo here?

imo we should also use MySQL for this service, can't any reason to maintain a new type of database?

don't think so, it was just started with Mongo. I will swap it out for MySQL.

yep, made more sense starting with it (as discussed in taiko discord, horizontal scaling, no need for relational DB) but since we already have an infra for a db which is mysql, makes more sense to re-use it!