Nathan Selikoff on Omnimodal's real-time tech stack
1 hour 27 minutes Posted May 8, 2019 at 10:00 am.
– Overview of Omnimodal's tech stack
– Omnimodal's mission: to help cities manage transportation demand
– How to ingest open transportation data and present it in real time
– How graphics-heavy OpenGL and C++ apps can benefit from web tooling
– Why state machines are used in both video game and web development
– How JavaScript UI development compares to other paradigms
– Why Ember and Rails were chosen for Omnimodal's technology needs
– Using a prediction engine to improve on transportation schedules
How Omnimodal gets data from its hardware trackers to the Rails server
– How services like Heroku and PubNub, custom AWS code, and the concept of a Data Lake help address scalability issues
– How deploys are coordinated across multiple services
What the development process looks like for a multi-service tech stack
– What the complexity breakdown is between Omnimodal's frontend and backend
– Lessons learned on authentication while using Auth0
Lessons learned on data modeling
– Tech choices, escape hatches, what's worked, and what hasn't
– Things Nathan loves about Ember, and things that are challenging
0:00
1:27:53
Show notes
Topics include:Links:Nathan on TwitterOmnimodal.ioPubNubGTFS feed specificationAmazon KinesisAmazon ElastiCacheAWS AppSyncAuth0
This podcast uses Simplecast for stats, and dynamic audio. Learn more on this podcast's About tab. Dynamic Audio may cause this episode's timestamps to be slightly off.