Go Best Practices – Interfaces, Packages and APIs
- 1. Author Date Go best practices Go naviro
- 2. Founder of Encore André Eriksson Coder. Ex-Spotifier. Puppy caretaker.
- 3. Founder of Encore André Eriksson Coder. Ex-Spotifier. Puppy caretaker.
- 4. Simplicity
- 5. Simplicity
- 6. Complexity
- 7. Complexity
- 13. "The state or quality of being intricate or complicated." What is complexity?
- 14. "Complexity is anything related to the structure of a software system that makes it hard to understand and modify the system." What is complexity? — A Philosophy of Software Design
- 16. The Complexity Equation "The sum of (the complexity of each part times the fraction of time spent developing that part)"
- 18. Human working memory can only hold a few (3-4) items at a time. Chunking
- 19. M D P H D R S V P C E O I H O P Chunking
- 20. MD PHD RSVP CEO IHOP Chunking
- 21. Modular Design
- 24. Systems should be designed by breaking them down into smaller parts, or modules
- 25. We can keep breaking things down
- 27. Application Everything your application does Systems Large, independent parts of the application
- 28. Application Everything your application does Systems Large, independent parts of the application Services Parts of a system that are separated by a network boundary
- 29. Systems Large, independent parts of the application Services Parts of a system that are separated by a network boundary Components A service is made up of one or more components Packages A component is made up of Go packages
- 30. Services Parts of a system that are separated by a network boundary Components A service is made up of one or more components Packages A component is made up of Go packages Types, Functions, etc Parts that make up a package
- 31. How we break things down matters a great deal
- 32. Interfaces
- 35. "A point where two systems, subjects, organizations, etc. meet and interact."
- 36. "A point where two systems, subjects, organizations, etc. meet and interact."
- 37. "A point where two systems, subjects, organizations, etc. meet and interact."
- 38. "A device or program enabling a user to communicate with a computer"
- 40. To properly divide our application into modules, we need to think about the interfaces between modules.
- 45. Best Practice #1 Great interfaces require thinking ahead.
- 46. Interface Design
- 52. Deep Module
- 53. Deep Module Shallow Module
- 54. Deep Module Shallow Module ?
- 55. Best Practice #2 Great modules are deep.
- 57. Deep modules isolate the caller from something
- 58. Deep modules isolate the caller from something
- 59. Deep modules isolate the caller from something
- 60. Deep modules isolate the caller from something
- 61. Deep modules isolate the caller from design decisions
- 67. Interfaces solve problems for the consumer
- 68. Favor the consumer over the provider
- 69. Simple interface over simple implementation
- 70. Design interfaces together with consumers
- 71. Test your designs with real-world use cases
- 72. Best Practice #3 Great modules isolate complexity.
- 73. Quiz Time!
- 75. When to split a package?
- 76. When to split a package? Minimize total complexity
- 77. When to split a package? • Minimize total complexity Best information hiding
- 78. When to split a package? • • Minimize total complexity Best information hiding Fewest dependencies
- 79. When to split a package? • • • Minimize total complexity Best information hiding Fewest dependencies Deepest interfaces
- 82. Good
- 83. Good Bad
- 85. Best Practice #Bonus Everything is a trade-off.
- 89. • • • • Create backend services and call APIs with a single line of code Automatically sets up your cloud infrastructure Built-in state of the art debugging tools Handles any scale, out of the box Superpowers
- 90. • • • • Startups building web or mobile apps Want to focus on building their product May not have experienced backend developers Want a more enjoyable development experience Who is it for?
- 91. LiveDemo