scale.bythebay.io: Vincent Marquez Interview
Recording: scale.bythebay.io: Vincent Marquez Interview
[Music] hi my name is Vincent Marquez I work for Verizon Labs and I'm a lead software engineer designing safe api's for people to use scaling scaling issues are always a problem dealing with Brack back pressure is probably the biggest problem we've had to think about over and over because there's not really a right answer it's all about trade-offs so deciding when to when to exhibit back pressure and when to be fully asynchronous and and not exhibit back pressure is kind of one of those issues we've we've gone back and forth on and it depends on the service and depends on the what kind of guarantees you want to have [Music] yeah I think as we we go into a microservices era we're gonna see more and more issues with service discovery with versioning and with incompatible api's so I would love to see people solve that problem right now there hasn't been really been a clear winner and how we do this kind of this kind of a you know large-scale micro-services architecture where everything's talking everything and deployments are constantly happening and there's different versions of different services that need have dependencies on other versions of different services and that's going to be a key issue for the industry to figure out in the next couple years [Music] so functional programming has been fantastic for Verizon I can say that of the software we've shipped the issues have been 99.9% performance related and scaling related rather than tracking down exceptions or tracking down null pointers or having invalid business logic our software just works and then the the next challenge is making it scale and making it fast but in terms of having to to be woken up in the middle of night because someone forgot to check if something returned the right results just I don't see it happening anymore we've had huge gains in productivity because of it people sleep better and let's us think about problems in a larger scale we're able to think about how is this gonna affect the system performance wise latency rise rather than worrying about if our codes actually just gonna work when we deploy it I love talking to people in the hallways I get to go up to people who I've read their blogs or read their books and get to ask them questions I get to argue with them about interesting ideas they have that I don't agree with have conversations about about different trade-offs that are making in their company things that are happy with with functional programming things they wish would improve and just those kind of conversations are invaluable