Podchaser Logo
Home
Episode 3 - Food for thought

Episode 3 - Food for thought

Released Tuesday, 19th May 2015
Good episode? Give it some love!
Episode 3 - Food for thought

Episode 3 - Food for thought

Episode 3 - Food for thought

Episode 3 - Food for thought

Tuesday, 19th May 2015
Good episode? Give it some love!
Rate Episode

On the heels of launching his new service, CTO of MapleDaniel Cowgill sits down with Chris and Jeff to discuss the tech that went intolaunching a vertically integrated food delivery service.

The website is down

The financial district inManhattanis the current delivery zone for Maple

Maple uses Go and MongoDB

Dan’s only prior restaurant experience

I don’t want to taco ‘bout it

Other food delivery companies are trying different spins on delivery.Sprig has surge pricing andMunchery delivers food cold

Casper delivers mattresses by bike messenger in New YorkCity

Maple’s javascript frontend is using Reactand some Mithril internally

Deciding how to deliver their food in the most efficient way possible is morecomplex than just the travelling salesmanproblem

Maple ruled out using scala early on

Leaving node

Go doesn’t have generics

Nginx uses round-robin for loadbalancing bydefault

Maple is using Linode for now

Show More
Rate

Join Podchaser to...

  • Rate podcasts and episodes
  • Follow podcasts and creators
  • Create podcast and episode lists
  • & much more

Episode Tags

Do you host or manage this podcast?
Claim and edit this page to your liking.
,

Unlock more with Podchaser Pro

  • Audience Insights
  • Contact Information
  • Demographics
  • Charts
  • Sponsor History
  • and More!
Pro Features