michaelgv

I’ve always said to hire the people who can do what we need as a business, regardless of their gender

State is much less important to track. It’s easier to do, the real challenge is garbage collection - you need it, but you don’t want to collect too much in memory. That’s why Redis is a great tool for our edge servers.

Its a pain to code. I’ve done it, and I hated every second of it. Keeping data in sync with dynamic data in near real-time is terrible.

I wrote the CDN in Go, with Redis and a smaller go-powered daemon to retrieve assets every 20 seconds, sync them to a local storage drive, and after 5 days retrieve again - or, if there is no requests within 48 hours, clear the unused items.

Then I setup a system that if one edge requests an “unpopular” file, it’ll ping a simple REST API and have all the other edges pull that file, this allowing the edges to stay “one step ahead” of the user load

Just be careful, understand that if you do a PULL only CDN, you're not going to gain big benefits. If you do want a pull only CDN, have a background task runner to retrieve the files, and update them locally.

Are you designing this CDN to pull from origin, cache temporarily? Or to pull from local file and put strong cache on it?

If you need a hand let me know, I’ve built pretty large CDNs before (10M r/s at peak)

As someone who just recently CDN hell, and rebuilt our entire CDN network from the ground up (software and hardware), I was wondering why you picked RoR?

Does that make them “Professional Dicks”?

I’d be open to this if it was built in Firefox and let you run the models on your own machine instead of blindly trusting a third party.

I imagine that when you request data deleted it’s only anonymized, and the actual learning data is kept.

Precisely the key, you need in my opinion:

1. Someone you can trust 2. Someone you’re not afraid to speak up with or against, without fear of repercussion personally within reason (ie, if you call each other crap every day, you’re not a good match most of the time)

I’ve searched local circles to see if there’s someone I’m not best friends with, someone I can argue with, with no long term feelings in the line, and can feel I trust.

Instead of asking me to complete some boring challenge, bring me into your office, and let me help solve a real issue you’re facing, then at least we both don’t waste our time on challenges that only prove you have free time on your hands.

I received one also, unfortunately I don’t have a co-founder but have been seeking one out

Didn’t know the Git trick, goodbye gitkraken!

My plans for future cloud platforms are to have the ability to create your own platform file, that’ll house all the required code to get it running, and then having a simple command to install them, ie...

ignite install —platform {platform_name}

All platform code will be saved in your home directory under a folder called .ignite, ie: /home/Michael/.ignite/platforms/Heroku ...etc

This new platform design will be in the next update, and you’ll be able to generate a base template by doing...

ignite create —provider {provider_name}

Then in terms of sharing the provider file, and all its sub files, you would do the same ignite share command, with a flag of —provider, and then it’s a matter of sharing and installing it.

Apex is very good, but I draw the line when it comes to being reproducible universally, the goal of ignite is to be an AIO package that can manage configuration, dependencies, and deployment without having to create complex structures for deployment/sharing/etc, and the key factor is everything that is created must be reproducible regardless of platform, IDE, etc. and that’s why Ignite exists, to help take away that pain and just have a very simple CLI do the tasks automatically