Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Surviving Your Tech Stack

51 Aufrufe

Veröffentlicht am

presented at Web Unleashed 2019
For more info see https://fitc.ca/event/webu19/

Kevin Daly RBC Ventures

Every developer has faced the difficult choice of deciding what tech stack they should use for a new project. Should you use the latest tech or something that everyone knows? Which framework is the best for your team? To survive your tech stack, developers must make trade-offs with developing on new tech stacks and the ability to maintain and scale their applications.

In this presentation, you’ll learn how to evaluate your tech stack and understand the pros and cons of using bleeding edge technology. Using his past experiences, Kevin will also share his lessons learned and how his team tackles managing their tech stack today.

Veröffentlicht in: Technologie
  • Als Erste(r) kommentieren

  • Gehören Sie zu den Ersten, denen das gefällt!

Surviving Your Tech Stack

  1. 1. Surviving your StackMAGING RETIREMENTWeb Unleashed 2019 – September Kevin Daly - Lead Digital Architect – RBC Ventures kevin.daly@rbc.com https://www.linkedin.com/in/kevin-daly-50247a1b/ @therealkedaly
  2. 2. 2 Who am I? Lead Digital Architect for RBC Ventures • Architecture team is responsible for advising all Ventures on architecture • Encouraging and influencing best practices for Ventures Experienced cloud architect with over 20 years experience I’ve been building software and systems since I was 15
  3. 3. 3 Why should you listen to me? • Because I know everything! I’ve been doing this for years!
  4. 4. 4 You shouldn’t! Your decisions should be based on •Cost •Talent / Personnel•Use cases•Data
  5. 5. 5 You shouldn’t! NOT! • Because some guy at a conference said so • You read a blog on the internet • LinkedIn or some other tech giant is using it!
  6. 6. What is RBC Ventures
  7. 7. PROPRIETARY REWARDS INNOVATIVE PRODUCT LEADER PERSONALIZED ADVICE DATA AND TECHNOLOGY SCALE STRATEGIC PARTNERSHIPS RBC’s digitally-enabled relationship bank delivers considerably more value for clients DIVERSIFIED DISTRIBUTION $ $ $ 7 RBC starts with a better bank
  8. 8. RBC Ventures goes beyond banking to deliver unique value for all Canadians BUSINESS MOBILITY CONSUMER HOME $ $ $ DIVERSIFIED DISTRIBUTION STRATEGIC PARTNERSHIPS PERSONALIZED ADVICE DATA AND TECHNOLOGY SCALE PROPRIETARY REWARDS INNOVATIVE PRODUCT LEADER 8 WELLNESS Now, we’re moving beyond traditional banking
  9. 9. Keeping you in the know on the little things Making renting hassle free for renters and landlords Making moving hassle free Connecting consumers to trusted contractors Helping Canadian SMEs sell in China Helps entrepreneurs start their business Digital glovebox and servicing for car owners 9 Home search, reimagined BUSINESS MOBILITY CONSUMER HOME WELLNESS Tracking taxes for the self-employed BOOMERANG Helping retirees make connections Securing sale-by-owner payments Snapshot of ventures Helping Canadians make better spending decisions Helping you get more value Helping newcomers be successful in Canada Finding dream jobs for recent graduates Amplifying value for Canadians Making living with friends stress free Earn cashback at local merchants Public transit arrival times and locations
  10. 10. Things to consider Let’s get started!
  11. 11. 11 So what is a stack?
  12. 12. 12 So what is a stack? A software stack is a group of programs that work in tandem to produce a result or achieve a common goal. https://www.techopedia.com/definition/27268/software-stack
  13. 13. 13 My view of a stack Users •Build/Test •Develop•Commit •Runtime Environment• • ••Commit •Build/Test •Deploy ••Runtime Environmen t
  14. 14. 14 Stack as culture •People •Technology•Process
  15. 15. 15 So how do you choose a stack?
  16. 16. 16 You are not Google! https://blog.bradfieldcs.com/you-are-not-google-84912cf44afb
  17. 17. 17 A Cautionary Tale (The Hype Machine)
  18. 18. 18 Build powerful reactive, concurrent, and distributed applications more easily
  19. 19. 19 akka is cool!
  20. 20. 20 akka is state of the art! • Cool languages like Scala • Functional! • Reactive! • Concurrent! • Distributed! • We could run it on our Kubernetes cluster • Build out an AI System maybe • Kafka Cluster • maybe even build a Block Chain !
  21. 21. 21 But… • Distributed Applications are hard • Actors are a pretty new pattern • Clusters have some maintenance and support issues • Nobody at this company understood how this thing worked and the guy who wrote it left the company.
  22. 22. 22 So Why? • 100’s per second 100 * 60 seconds is = 6,000 per minute X 60 minutes 360,000 per hour X 24 hours 8,640,000 documents per day
  23. 23. 23 8,640,000
  24. 24. 24 8,640,000
  25. 25. 25 8,640,000 1,000,000
  26. 26. 26 8,640,000 1,000,000
  27. 27. 27 8,640,000 1,000,000 500,000
  28. 28. 28 8,640,000 1,000,000 500,000
  29. 29. 29 8,640,000 1,000,000 500,000 10,000
  30. 30. 30 8,640,000 1,000,000 500,000 10,000 90 % Market penetration
  31. 31. 31 Process
  32. 32. 32
  33. 33. 33 Let’s talk product market fit and MVP
  34. 34. 34 AND BREAK THINGS!
  35. 35. 35
  36. 36. 36 Can you do both?
  37. 37. 37 People
  38. 38. 38 Ventures Reference Architecture
  39. 39. 39 Ventures Tech Stack
  40. 40. 40 Why did we choose this architecture? •People•Process•Technology • Hire talent easily Identify talent and hire from larger talent pool • Transferable internal skills Developers can support and switch teams as needed. • Simple Easily understood development stack • Rapid development cycle • Able to leverage open source and tech community •People •Technology•Process • Use leading technology AWS Cloud • Be scalable and versatile PostGres is an extremely versatile database. • Full Stack Development • Find support and knowledge NodeJS has a great community
  41. 41. 41 Lessons Learned “The good stuff” •Productivity + Cost •Job Candidate Availability•Consistency•Agility •Flexibility
  42. 42. 42 Lessons Learned “Gotchas” WTF Is a Full Stack Developer? What Happens with a partial product market fit? Technical Debt? Node Stack doesn’t fit every use case?
  43. 43. 43 Takeaways Understand your scale from a most pessimistic to a most optimistic view Don’t over engineer! Know the size of your market Avoid the hype machine!
  44. 44. 44 And the most Important Takeaway •People •Technology•Process
  45. 45. 45 Well Almost… Final Thought Dogmatically pursing a stack as a single source of truth is a recipe for disaster!
  46. 46. 46 Kevin Daly Lead Digital Architect for RBC Ventures Connect with me Email - kevin.daly@rbc.com LinkedIn - https://www.linkedin.com/in/kevin-daly-50247a1b/ @therealkedaly

×