1. Where to start
2. Prepare for growth
3. How to maintain
Slide 5
Slide 5 text
Multi-billion-euro companies started in a garage.
1. Where to start
Slide 6
Slide 6 text
Have a product idea
What are the needs
What are the constraints
Data processing software
Scale to millions of processings
Already a legacy version
Context
Context | Validate the idea | Technical choices
Slide 7
Slide 7 text
Define a minimal version
Implement a prototype
Verify the feasibility
Make technical choices
Validate the idea
Context | Validate the idea | Technical choices
Slide 8
Slide 8 text
Use well-known open-source tools
Community support, Stack Overflow goldmine
Online free courses, tutorials
Easier recruitment & onboarding
Technical choices
Context | Validate the idea | Technical choices
Slide 9
Slide 9 text
Context | Validate the idea | Technical choices
Language trends
Slide 10
Slide 10 text
Use well-known open-source tools
Choose Go
Created for cloud computing
Designed for concurrency
Technical choices
Context | Validate the idea | Technical choices
Slide 11
Slide 11 text
“My first implementation was in Ruby, but
when I re-implemented in Go I was able
to take advantage of concurrency to get
a 20x performance improvement.”
https://tinyurl.com/cncf-devstats
Q&A with DevStats creator Łukasz Gryglicki
Context | Validate the idea | Technical choices
Slide 12
Slide 12 text
Use well-known open-source tools
Choose Go
Perfect for cloud computing
Designed for concurrency
Easy to learn
Technical choices
Context | Validate the idea | Technical choices
Slide 13
Slide 13 text
Matthias Endler - https://endler.dev/
Context | Validate the idea | Technical choices
Slide 14
Slide 14 text
Use well-known open-source tools
Choose Go
Perfect for cloud computing
Designed for concurrency
Easy to learn
Great community
Technical choices
Context | Validate the idea | Technical choices
Slide 15
Slide 15 text
Women Who Go
Context | Validate the idea | Technical choices
Gophercon Europe
Slide 16
Slide 16 text
Use well-known open-source tools
Choose Go
Perfect for cloud computing
Designed for concurrency
Easy to learn
Great community
Plethora of resources
Technical choices
Context | Validate the idea | Technical choices
Slide 17
Slide 17 text
Do
Verify the feasibility
Get the big picture
Explore your options
Make rational choices
Use existing tools
Don't
Start coding on day 1
Limit to your knowledge
Follow trends
Reinvent the wheel
Where to start
Context | Validate the idea | Technical choices
Slide 18
Slide 18 text
2. Prepare for growth
Let's get billions of users and raise a series A!
Let's become a unicorn!
Slide 19
Slide 19 text
Restart from scratch
Early mistakes make a better product
Define teams and communication channels
Streamlining
Streamlining | Separate Responsibilities | Automate everything
Slide 20
Slide 20 text
“Any organization that designs a system
will produce a design whose structure is
a copy of the organization's
communication structure.”
Mel Conway's law
Streamlining | Separate Responsibilities | Automate everything
Slide 21
Slide 21 text
Clear boundaries
Clear contracts
User-oriented APIs
Separate responsibilities
Streamlining | Separate Responsibilities | Automate everything
Slide 22
Slide 22 text
Publish
Represent Protocols
Streamlining | Separate Responsibilities | Automate everything
You make it, you run it.
Streamlining | Separate Responsibilities | Automate everything
https://tinyurl.com/ci-cd-pipeline
Slide 25
Slide 25 text
Streamlining | Separate Responsibilities | Automate everything
Orchestrated containers
Slide 26
Slide 26 text
Streamlining | Separate Responsibilities | Automate everything
Cloud or premises?
Slide 27
Slide 27 text
Automate everything
Streamlining | Separate Responsibilities | Automate everything
Slide 28
Slide 28 text
Automate everything
Human time is money
Streamlining | Separate Responsibilities | Automate everything
Slide 29
Slide 29 text
Automate everything
Human time is money
Repeating is boring
Streamlining | Separate Responsibilities | Automate everything
Slide 30
Slide 30 text
Automate everything
Human time is money
Repeating is boring
Repeating is boing
Streamlining | Separate Responsibilities | Automate everything
Slide 31
Slide 31 text
Automate everything
Human time is money
Repeating is boring
Repeating is error-prone
Streamlining | Separate Responsibilities | Automate everything
Slide 32
Slide 32 text
Human time is money
Repeating is boring
Repeating is error-prone
Setup Continuous Integration & Continuous Delivery
Automate everything
Streamlining | Separate Responsibilities | Automate everything
Slide 33
Slide 33 text
Streamlining | Separate Responsibilities | Automate everything
https://katalon.com/resources-center/blog/ci-cd-pipeline
Slide 34
Slide 34 text
CI/CD pipelines with Go
Streamlining | Separate Responsibilities | Automate everything
Format
Lint
Tests
Coverage
Benchmark
gofmt
golangci-lint
go test
go test -cover
go test -bench=.
Slide 35
Slide 35 text
Human time is money
Repeating is boring
Repeating is error-prone
Setup Continuous Integration &
Continuous Delivery
Test at different levels
Automate everything
Streamlining | Separate Responsibilities | Automate everything
F1
Streamlining | Separate Responsibilities | Automate everything
Performance & load tests
Slide 38
Slide 38 text
Do
Separate responsibilities
Own your code
Write tests early
Setup CI/CD pipelines
Don't
Redeploy everything as you go
Rely on manual actions
Stuff the monolith turkey
Prepare for growth
Streamlining | Separate Responsibilities | Automate everything
Slide 39
Slide 39 text
3. How to maintain
Slide 40
Slide 40 text
Shoveling the
snow forward
Pelleter en avant
https://ferd.ca/on-technical-debt-shoveling-forward.html
Refactoring is mandatory | Monitoring
Slide 41
Slide 41 text
The software needs to grow as you learn
Dedicate time for housekeeping
Stay up to date with dependency versions
Work iteratively, in small steps
Refactoring is mandatory
Refactoring is mandatory | Monitoring
Do
Setup thresholds for alerts
Keep track of technical debt
Don't
Suppose bugs never happen
How to maintain
Refactoring is mandatory | Monitoring
Slide 44
Slide 44 text
Conclusion
Slide 45
Slide 45 text
Conclusion
Choose Go to leverage its simplicity and scalability
Automation is a priority and well-invested money
Make your domain clear with low cognitive load
Allocate time for housekeeping