![]() A big welcome to the 866 of you are new this week. In this issue we’ve got some beefy servers, some rebellion against traditional CS curriculum, and a new breakthrough at the Mark Twain School of Data Science. Welcome to #112.
Who’s a beefy boy? The truth about the edgeFly.io went through the trouble of raising a series B just to get some coverage for their edge-y (😉) hot takes in TechCrunch (it worked). Fresh off that high that only comes with $25 milli hitting the bank account, CEO Kurt Mackey looked that TC When we think of The Edge™️, most developers are talking about CDNs for static assets that have lightweight compute offerings. But even the most “cutting edge” compute offerings still have to go on a road trip to Virginia just to get some data. That’s where Fly wants to shake things up. So what exactly does Fly do that’s different?
Bottom Line: Fly is spending that new bread on the beefiest servers in the game so you can run your application at the edge and not have to half-app it. So far, the results are looking pretty impressive.
“I still think it needs more pop” [sponsored] Bugherd will break you out of the infinite feedback loopDante’s 8th level of Dev Hell: trying to get feedback on a website from a big team. You create the new landing page and send it to your manager, who gives you feedback and sends it to the VP, who also gives you feedback and “CC’s a few more stakeholders” who also give you feedback… for eternity. Thankfully, there’s BugHerd:
It saves a lot of time and is our favorite way to work with QA teams, outside clients, or contractors. Check it out – and see why over 10,000 companies use it.
Business in the front… Party in the back endFor years now, the JavaScript community has had an irrational love for NoSQL and document oriented databases. But, did you ever wonder…why? My running theory is that it’s our collective haphazard rebellion against anything found in traditional CS curriculum, but there might be another reason. Why did relational databases go out of style? When Node.js first came out, it specialized (lol) in fast I/O and was good at building things like chat apps. The problem, among others, was that traditional databases were limited to a small number of concurrent connections. In order to have more connections, you needed more memory (i.e. “scaling vertically”) and eventually scaling becomes an issue. NoSQL databases have a more limited data structure, which enable them to scale horizontally (i.e. adding more database “nodes” to the “cluster”). But they come with their own tradeoffs. NoSQL DB’s work well when you understand your app’s access patterns — but for many apps, they have multiple clients that have different data needs (something a SQL query can handle well). So why are they making a comeback now?
Bottom Line: Like everything in tech (and fashion), databases are coming full circle. The good news is that Database Design & Development course you bought on Udemy for $4.99 in 2015 is still up to date. JobsFull-stack software engineer at PhantomPhantom is looking for fullstack engineers who enjoy massive ownership and freedom, and who want to work with a variety of technologies, including React, TypeScript, Postgres, Docker, and more. You’ll be owning features on their web platform and working closely with the founders to improve the product. The role is fully remote. JS Quiz — Sponsored by StreamStream is the #1 chat platform out there. It’s used by small startups and giants like Adobe, Soundcloud and Match-dot-com. What order will this code log?
Cool Bits
JS Quiz Solution — Sponsored by StreamWhat order will this code log?
If you chose The answer is Shout out to the Doctor for the source. |