SlideShare a Scribd company logo

Building a full-stack app with Golang and Google Cloud Platform in one week

D
Dr. Felix Raab

This document discusses building a full-stack application called MemeMail using Golang and Google Cloud Platform within one week. It describes choosing Google Cloud over other cloud providers for its ease of use. It then discusses the frontend implementation using Vue.js with a simple state mutation approach. The backend is built with Golang on App Engine using Cloud services like Datastore and Cloud Build for CI/CD. It emphasizes keeping the architecture simple rather than over-engineering for an MVP within a tight deadline.

Software
Related topics:
Google Cloud Platform • Software Engineering • Software Architecture
1 of 120
Download to read offline
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
Memes in the Cloud – Building a full-stack app with Golang and Google Cloud Platform in one week Dr. Felix Raab | Head of Engineering @ KI Labs Munich | ki-labs.com f.raab@kigroup.de | medium.com/@fe9lix
SCOPE OF TALK
SCOPE OF TALK Case Study Project idea and journey for an MVP finished within one week
SCOPE OF TALK Case Study Project idea and journey for an MVP finished within one week Software Engineering for Cloud Apps The “full” stack: Frontend, Backend, Build, Deployment, Logging… Towards the end of the talk: Software Engineering practices in Go
SCOPE OF TALK Case Study Project idea and journey for an MVP finished within one week Software Engineering for Cloud Apps The “full” stack: Frontend, Backend, Build, Deployment, Logging… Towards the end of the talk: Software Engineering practices in Go Memes At the heart of the app itself – consequently, Memes to illustrate some opinionated views
BACK AT MY PREVIOUS EMPLOYER… Hours claiming – trying not get “shitlisted”… because the boss would be notified!
Building a full-stack app with Golang and Google Cloud Platform in one week
Building a full-stack app with Golang and Google Cloud Platform in one week
Idea – Every Friday… Schedule an hours claim reminder mail containing a meme, to myself.
Building a full-stack app with Golang and Google Cloud Platform in one week
Building a full-stack app with Golang and Google Cloud Platform in one week
FIRST: HOW TO CHOOSE A CLOUD? …when you can start from scratch – no corporate constraints, no restrictions, no Frankfurt.
LOOK AT THE HISTORY OF CLOUD COMPANIES
LOOK AT THE HISTORY OF CLOUD COMPANIES
LOOK AT THE HISTORY OF CLOUD COMPANIES
LOOK AT THE HISTORY OF CLOUD COMPANIES
LOOK AT THE HISTORY OF CLOUD COMPANIES MICROSOFT AZURE
LOOK AT THE HISTORY OF CLOUD COMPANIES MICROSOFT AZURE AMAZON WEB SERVICES
LOOK AT THE HISTORY OF CLOUD COMPANIES MICROSOFT AZURE AMAZON WEB SERVICES GOOGLE CLOUD PLATFORM
LOOK AT THE HISTORY OF CLOUD COMPANIES MICROSOFT AZURE AMAZON WEB SERVICES GOOGLE CLOUD PLATFORM Enterprise
LOOK AT THE HISTORY OF CLOUD COMPANIES MICROSOFT AZURE AMAZON WEB SERVICES GOOGLE CLOUD PLATFORM Enterprise Ops
LOOK AT THE HISTORY OF CLOUD COMPANIES MICROSOFT AZURE AMAZON WEB SERVICES GOOGLE CLOUD PLATFORM Enterprise Ops S(R)E
–Brave New Geek “Multi-Cloud Is a Trap” https://bravenewgeek.com/multi-cloud-is-a-trap/
WORKS LIKE YOU WOULD EXPECT IT…
WORKS LIKE YOU WOULD EXPECT IT… Service Offerings used to build MemeMail
WORKS LIKE YOU WOULD EXPECT IT… Service Offerings used to build MemeMail More on that later…
WORKS LIKE YOU WOULD EXPECT IT… Service Offerings used to build MemeMail More on that later… API access, permissions, config…
WORKS LIKE YOU WOULD EXPECT IT… Service Offerings used to build MemeMail More on that later… CI/CD API access, permissions, config…
WORKS LIKE YOU WOULD EXPECT IT… Service Offerings used to build MemeMail More on that later… CI/CD Database (NoSQL document store) API access, permissions, config…
WORKS LIKE YOU WOULD EXPECT IT… Service Offerings used to build MemeMail More on that later… CI/CD Database (NoSQL document store) Object Storage (Blobs…) API access, permissions, config…
WORKS LIKE YOU WOULD EXPECT IT… Service Offerings used to build MemeMail More on that later… CI/CD Database (NoSQL document store) Object Storage (Blobs…) Task Queue (with scheduling!) API access, permissions, config…
WORKS LIKE YOU WOULD EXPECT IT… Service Offerings used to build MemeMail More on that later… CI/CD Database (NoSQL document store) Object Storage (Blobs…) Task Queue (with scheduling!) Logging… API access, permissions, config…
The Frontend – Diving into the world of JavaScript? https://exceptionnotfound.net/big-ball-of-mud-the-daily-software-anti-pattern/
THE FULLSTACK IN GO – SO HOW ABOUT WEBASSEMBLY (WASM)?
NO! BECAUSE…
NO! BECAUSE…
NO! BECAUSE… Readability, Debugging, Size…
 (but maybe in the future)
NO WEBASSEMBLY. MAYBE ELM THEN?
NO! BECAUSE… Learning curve, different paradigm, transpiling to JS, libraries… – remember, we have one week to finish!
VANILLA JS (ES 6)! 
 BUT WHICH FRAMEWORK?
RESIST THE TEMPTATION TO…
RESIST THE TEMPTATION TO…
RESIST THE TEMPTATION TO… Also, do not use Github Stars as your only criterion! Popularity is one thing…
HOW TO CHOOSE
HOW TO CHOOSE 1) Does it solve your problem in a simple way? Rendering the frontend and adding interaction without sprinkling jQuery calls throughout your code base.
HOW TO CHOOSE 1) Does it solve your problem in a simple way? Rendering the frontend and adding interaction without sprinkling jQuery calls throughout your code base. 2) Look at the quality of the documentation! Because you need to read it and be able to understand it – quickly!
VUE.JS SEEMS TO MATCH. BUT WHICH ARCHITECTURE?
SO MANY APPROACHES… …MVVM, Flux, Redux, SAM, ELM Architecture…? What is the essence?
Building a full-stack app with Golang and Google Cloud Platform in one week
STATE MUTATION
STATE MUTATION Take notice when somebody tells you that you should or can entirely avoid mutating state.
MUTATING STATE. HERE’S HOW…
MUTATING STATE. HERE’S HOW… 1) Put your entire app state into a single model Avoid primitive obsession – use proper objects! This is your single source of truth.
MUTATING STATE. HERE’S HOW… 1) Put your entire app state into a single model Avoid primitive obsession – use proper objects! This is your single source of truth. 2) Dispatch Actions from the UI to trigger a state mutation Do not yet mutate the state in the action itself! Actions are intents with payloads.
MUTATING STATE. HERE’S HOW… 1) Put your entire app state into a single model Avoid primitive obsession – use proper objects! This is your single source of truth. 2) Dispatch Actions from the UI to trigger a state mutation Do not yet mutate the state in the action itself! Actions are intents with payloads. 3) Accept or reject the state mutation in your model At the end of your (async.) action, “commit” / “propose” a new value to the model.
MUTATING STATE. HERE’S HOW… 1) Put your entire app state into a single model Avoid primitive obsession – use proper objects! This is your single source of truth. 2) Dispatch Actions from the UI to trigger a state mutation Do not yet mutate the state in the action itself! Actions are intents with payloads. 3) Accept or reject the state mutation in your model At the end of your (async.) action, “commit” / “propose” a new value to the model. 4) Update the UI when the state changes Derive the state to render from your model, e.g. by UI bindings.
VUEX.JS KIND OF SUPPORTS THAT PATTERN
–Ryan Dahl “[...] if you’re building a server, I can’t imagine using anything other than ” THE BACKEND.
HOW TO BUILD?
HOW TO BUILD? Go 1.11 Because Go Modules!
HOW TO BUILD? Go 1.11 Because Go Modules! Docker To be flexible with Go versions
 Multi-stage build!
HOW TO BUILD? Go 1.11 Because Go Modules! Docker To be flexible with Go versions
 Multi-stage build! entr + Makefile No Rake, Grunt, Gulp, NPM, Yarn – Makefile + Bash Script fine! Check entrproject.org
APP ENGINE – START SIMPLE
APP ENGINE – START SIMPLE
APP ENGINE – START SIMPLE App Engine Flex You can migrate to Kubernetes (GKE) later if you wish to – but for your MVP, don’t waste time managing a cluster.
APP ENGINE – START SIMPLE App Engine Flex You can migrate to Kubernetes (GKE) later if you wish to – but for your MVP, don’t waste time managing a cluster. Use defaults Start with App Engine default options and auto-scaling. Nobody knows how much traffic you will get. Watch and see what happens.
SEPARATE THE FRONTEND AND BACKEND?
YES AND NO!
YES AND NO! Expose your services as API to the frontend Frontend is rendered via a Go template. On that rendered page, a Single Page App can run in memory and call your backend API. Use Go templates for other static pages. Makes routing easier.
YES AND NO! Expose your services as API to the frontend Frontend is rendered via a Go template. On that rendered page, a Single Page App can run in memory and call your backend API. Use Go templates for other static pages. Makes routing easier. But no need to create two deployment units No need for premature optimisation (scaling). One Go binary is simpler than two Go binaries! 
 Static assets are loaded from the file system in your container.
CI/CD
CI/CD Google Cloud Build Will trigger and deploy when you push to your Git repo. Maintaining your own Jenkins server and setting up a build pipeline can be more time-consuming than you might think.
CI/CD Google Cloud Build Will trigger and deploy when you push to your Git repo. Maintaining your own Jenkins server and setting up a build pipeline can be more time-consuming than you might think. App Engine Deployment Straightforward versioning and service concept via DNS – version.service.appname Promoting app to production, traffic splitting etc. – 
 supported out of the box
Building a full-stack app with Golang and Google Cloud Platform in one week
Building a full-stack app with Golang and Google Cloud Platform in one week
The cloud can be mean and slow.
PLAYGROUNDS SAVE TIME Create a GCP “Playground” project Got stuck with Cloud Datastore (vs. Cloud Firestore) and 
 Cloud Tasks (only certain EU region). Led me to test service offerings first via playground.
WHICH ARCHITECTURE – ONIONS AND HEXAGONS?
SO MANY LAYERS AND CONCEPTS Also, ask yourself : Is there a rich domain? Or are you really building a CRUD app?
Building a full-stack app with Golang and Google Cloud Platform in one week
Building a full-stack app with Golang and Google Cloud Platform in one week
Take notice when nobody tells you to separate functionality into lots and lots of really small methods and delegating objects.
A QUESTION OF PHILOSOPHIES?
A QUESTION OF PHILOSOPHIES?
A QUESTION OF PHILOSOPHIES? Robert Martin (Uncle Bob) http://2017.agilesummit.gr/speakers/uncle-bob/
A QUESTION OF PHILOSOPHIES? John Ousterhout https://www.youtube.com/watch?v=bmSAYlu0NcY Robert Martin (Uncle Bob) http://2017.agilesummit.gr/speakers/uncle-bob/
DEEP VS SHALLOW MODULES
DEEP VS SHALLOW MODULES Shallow ModuleDeep module Interface Functionality
DEEP VS SHALLOW MODULES Shallow Module “The best modules are deep: they allow a lot of functionality to be accessed through a simple interface. A shallow module is one with a relatively complex interface, but not much functionality: it doesn’t hide much complexity.” 
 – From A Philosophy of Software Design, John Ousterhout Deep module Interface Functionality
EXAMPLE OF A DEEP MODULE Meme Image Generation Package “meme”, image.go: Simple interface, a lot of functionality.
PASS-THROUGH CODE TENDS TO BE SHALLOW – BUT HOW MUCH SEPARATION?
Building a full-stack app with Golang and Google Cloud Platform in one week
Separate the outside from the inside Kind of onion, just fewer layers
Separate the outside from the inside Kind of onion, just fewer layers Outside (package http) Protocol, routing (gorilla/mux), handlers
Separate the outside from the inside Kind of onion, just fewer layers Outside (package http) Protocol, routing (gorilla/mux), handlers Inside (package meme) Core, your actual (business) functionality
WHAT ABOUT INTERFACES?
IMPLICIT INTERFACE CONFORMANCE
IMPLICIT INTERFACE CONFORMANCE Awesome Golang feature, but here…
IMPLICIT INTERFACE CONFORMANCE Awesome Golang feature, but here…
IMPLICIT INTERFACE CONFORMANCE Awesome Golang feature, but here…
IMPLICIT INTERFACE CONFORMANCE Awesome Golang feature, but here… To be able to inject a different implementation, you would need to either create an interface that mirrors the datastore api or create a generic interface -> shallow wrapper
IMPLICIT INTERFACE CONFORMANCE Awesome Golang feature, but here… To be able to inject a different implementation, you would need to either create an interface that mirrors the datastore api or create a generic interface -> shallow wrapper Have a look at google/go-cloud for unstructured binary storage (supports GCP and AWS)
STRONGER ARGUMENT FOR AN INTERFACE?
STRONGER ARGUMENT FOR AN INTERFACE? Logging Needed almost everywhere! But Go’s default logging has limitations.
STRONGER ARGUMENT FOR AN INTERFACE? Logging Needed almost everywhere! But Go’s default logging has limitations. Even better: Structured Logging Implicit conformance to uber-go/zap for structured logging
STRONGER ARGUMENT FOR AN INTERFACE? Logging Needed almost everywhere! But Go’s default logging has limitations. Even better: Structured Logging Implicit conformance to uber-go/zap for structured logging
HOW TO HANDLE CROSS- CUTTING CONCERNS…?
CONTEXT OBJECT PATTERN
CONTEXT OBJECT PATTERN Reduce coupling of method parameters Instead of passing the logger through method parameters, pass a Go context object through middleware.
CONTEXT OBJECT PATTERN Reduce coupling of method parameters Instead of passing the logger through method parameters, pass a Go context object through middleware.
CONTEXT OBJECT PATTERN Reduce coupling of method parameters Instead of passing the logger through method parameters, pass a Go context object through middleware. Still not ideal, but good enough? Also see: https://medium.com/@gosamv/using-gos-context-library-for-logging-4a8feea26690
FINALLY, BEING CONSISTENT…
FINALLY, BEING CONSISTENT…
FINALLY, BEING CONSISTENT… Strong Consistency After creating, the user should see the most recent list of meme reminders 
 (strong consistency supported by Cloud Datastore)
FINALLY, BEING CONSISTENT… Strong Consistency After creating, the user should see the most recent list of meme reminders 
 (strong consistency supported by Cloud Datastore) Eventual Consistency Meme detail view might not have been generated and stored yet – 
 but you can always apologise to the user. Eventual consistency is often fine.
CONCLUSION
CONCLUSION Keep it simple (but not stupid!) Reduce the number of “things” you need to deal with – both from an architecture and a product perspective.
CONCLUSION Keep it simple (but not stupid!) Reduce the number of “things” you need to deal with – both from an architecture and a product perspective. Challenge existing “best practices” Have you been brainwashed by cargo cults in the past? The “best” practices always depend on the context and scope.
CONCLUSION Keep it simple (but not stupid!) Reduce the number of “things” you need to deal with – both from an architecture and a product perspective. Challenge existing “best practices” Have you been brainwashed by cargo cults in the past? The “best” practices always depend on the context and scope. Develop end-to-end Allows you to make better decisions for the entire system – and to iterate quickly for your MVP!
Building a full-stack app with Golang and Google Cloud Platform in one week

More Related Content

PDF
Rethinking Angular Architecture & Performance
Mark Pieszak
 
PDF
Finding the sweet spot - blending the best of native and web
Shawn Jansepar
 
KEY
Developing for Remote Bamboo Agents, AtlasCamp US 2012
Atlassian
 
KEY
AtlasCamp US 2012 Keynote, Jean-Michel Lemieux
Atlassian
 
PDF
How to build a social network on Serverless (AWS Community Summit)
Yan Cui
 
PDF
Serverless in Production, an experience report (AWS UG South Wales)
Yan Cui
 
PDF
Evolving Mobile Architectures
sgleadow
 
PDF
Building Hybrid Apps with Ember
jakecraige
 
Rethinking Angular Architecture & Performance
Mark Pieszak
 
Finding the sweet spot - blending the best of native and web
Shawn Jansepar
 
Developing for Remote Bamboo Agents, AtlasCamp US 2012
Atlassian
 
AtlasCamp US 2012 Keynote, Jean-Michel Lemieux
Atlassian
 
How to build a social network on Serverless (AWS Community Summit)
Yan Cui
 
Serverless in Production, an experience report (AWS UG South Wales)
Yan Cui
 
Evolving Mobile Architectures
sgleadow
 
Building Hybrid Apps with Ember
jakecraige
 

What's hot (20)

PDF
Designing Forge UI: A Story of Designing an App UI System
Atlassian
 
PPTX
Appcelerator Titanium Intro
Nicholas Jansma
 
PDF
Snappy Means Happy: Performance in Ember Apps
Matthew Beale
 
PDF
Developing PWAs and Mobile Apps with Ionic, Angular, and JHipster - Devoxx Mo...
Matt Raible
 
PDF
Serverless in production, an experience report (FullStack 2018)
Yan Cui
 
PDF
Surviving Serverless Testing: The ultimate Guide
OPEN KNOWLEDGE GmbH
 
PPTX
The Open-source Eclipse Plugin for Force.com Development, Summer ‘14
Salesforce Developers
 
PDF
Forge App Showcase
Atlassian
 
PDF
Appcelerator Titanium Intro (2014)
Nicholas Jansma
 
PPTX
Phonegap Day 2016: Ember/JS & Hybrid Apps Tips
Alex Blom
 
PDF
Step by Step Guide on Lazy Loading in Angular 11
Katy Slemon
 
PPTX
Put iOS and Android on the same Wavelength with Serverless Microservices
Neil Power
 
PPTX
Angular vs react vs vue
Sina Mirhejazi
 
PPTX
Ember Conf 2016: Building Mobile Apps with Ember
Alex Blom
 
PDF
Build social network in 4 weeks
Yan Cui
 
PDF
An Exploration of Cross-product App Experiences
Atlassian
 
PDF
Front End Development for Back End Developers - Devoxx UK 2017
Matt Raible
 
PDF
FaaS or not to FaaS. Visible and invisible benefits of the Serverless paradig...
Vadym Kazulkin
 
PDF
Ember At Scale
Chad Hietala
 
PDF
Adopting Java for the Serverless world at Serverless Meetup New York and Boston
Vadym Kazulkin
 
Designing Forge UI: A Story of Designing an App UI System
Atlassian
 
Appcelerator Titanium Intro
Nicholas Jansma
 
Snappy Means Happy: Performance in Ember Apps
Matthew Beale
 
Developing PWAs and Mobile Apps with Ionic, Angular, and JHipster - Devoxx Mo...
Matt Raible
 
Serverless in production, an experience report (FullStack 2018)
Yan Cui
 
Surviving Serverless Testing: The ultimate Guide
OPEN KNOWLEDGE GmbH
 
The Open-source Eclipse Plugin for Force.com Development, Summer ‘14
Salesforce Developers
 
Forge App Showcase
Atlassian
 
Appcelerator Titanium Intro (2014)
Nicholas Jansma
 
Phonegap Day 2016: Ember/JS & Hybrid Apps Tips
Alex Blom
 
Step by Step Guide on Lazy Loading in Angular 11
Katy Slemon
 
Put iOS and Android on the same Wavelength with Serverless Microservices
Neil Power
 
Angular vs react vs vue
Sina Mirhejazi
 
Ember Conf 2016: Building Mobile Apps with Ember
Alex Blom
 
Build social network in 4 weeks
Yan Cui
 
An Exploration of Cross-product App Experiences
Atlassian
 
Front End Development for Back End Developers - Devoxx UK 2017
Matt Raible
 
FaaS or not to FaaS. Visible and invisible benefits of the Serverless paradig...
Vadym Kazulkin
 
Ember At Scale
Chad Hietala
 
Adopting Java for the Serverless world at Serverless Meetup New York and Boston
Vadym Kazulkin
 
Ad

Similar to Building a full-stack app with Golang and Google Cloud Platform in one week (20)

KEY
Single Page Applications - Desert Code Camp 2012
Adam Mokan
 
PDF
Building Enterprise Grade Front-End Applications with JavaScript Frameworks
FITC
 
PDF
System design for Web Application
Michael Choi
 
KEY
20120306 dublin js
Richard Rodger
 
PDF
Client Server Web Apps with JavaScript and Java Rich Scalable and RESTful 1st...
zubinrlondoit
 
PDF
Tech Thursdays: Building Products
Hayden Bleasel
 
PPTX
Node Summit 2016: Web App Architectures
Chris Bailey
 
ODP
Path Dependent Development (PyCon AU)
ncoghlan_dev
 
PDF
React Native for Business Solutions: Building Scalable Apps for Success
Amelia Swank
 
PDF
Jose l ugia 6 wunderkinder, momenta
apps4allru
 
PPTX
Introduction to GoLang
NVISIA
 
KEY
TxJS 2011
Brian LeRoux
 
PDF
Client Server Web Apps with JavaScript and Java 1st Edition Casimir Saternos
tomeooakesrq
 
PDF
Lessons learned from building Demand Side Platform
bbogacki
 
PPTX
20 Tips for Building a Scalable and Robust Node.js Stack that Developers Love
Patrick Steele-Idem
 
PDF
Build your cross-platform service in a week with App Engine
Jl_Ugia
 
PDF
Product! - The road to production deployment
Filippo Zanella
 
PDF
Code In The Cloud 1st Edition Mark C Chucarroll
atassubhag
 
PDF
JavaScript Application Design A Build First Approach 1st Edition Nicolas Beva...
rcfbour9744
 
PPT
The economies of scaling software - Abdel Remani
jaxconf
 
Single Page Applications - Desert Code Camp 2012
Adam Mokan
 
Building Enterprise Grade Front-End Applications with JavaScript Frameworks
FITC
 
System design for Web Application
Michael Choi
 
20120306 dublin js
Richard Rodger
 
Client Server Web Apps with JavaScript and Java Rich Scalable and RESTful 1st...
zubinrlondoit
 
Tech Thursdays: Building Products
Hayden Bleasel
 
Node Summit 2016: Web App Architectures
Chris Bailey
 
Path Dependent Development (PyCon AU)
ncoghlan_dev
 
React Native for Business Solutions: Building Scalable Apps for Success
Amelia Swank
 
Jose l ugia 6 wunderkinder, momenta
apps4allru
 
Introduction to GoLang
NVISIA
 
TxJS 2011
Brian LeRoux
 
Client Server Web Apps with JavaScript and Java 1st Edition Casimir Saternos
tomeooakesrq
 
Lessons learned from building Demand Side Platform
bbogacki
 
20 Tips for Building a Scalable and Robust Node.js Stack that Developers Love
Patrick Steele-Idem
 
Build your cross-platform service in a week with App Engine
Jl_Ugia
 
Product! - The road to production deployment
Filippo Zanella
 
Code In The Cloud 1st Edition Mark C Chucarroll
atassubhag
 
JavaScript Application Design A Build First Approach 1st Edition Nicolas Beva...
rcfbour9744
 
The economies of scaling software - Abdel Remani
jaxconf
 
Ad

Recently uploaded (20)

PDF
Internet Downloader Manager (IDM) Crack 6.42 Build 42 Updates Latest 2025
itskinga12
 
PDF
System and Network Administraation Chapter 3
jaramharo
 
PDF
EN-Survey-Report-SAP-LeanIX-EA-Insights-2025.pdf
deepakkhaitan3
 
PPTX
Reimagine Home Health with the Power of Agentic AI​
AutomationEdge Technologies
 
PPTX
Operating system designcfffgfgggggggvggggggggg
rmskumara09
 
PDF
System and Network Administration Chapter 2
jaramharo
 
PDF
Audit Checklist Design Aligning with ISO, IATF, and Industry Standards — Omne...
rohnjim07
 
PPTX
Essential Infomation Tech presentation.pptx
pradeepjava2016
 
PPTX
Agentic AI : A Practical Guide. Undersating, Implementing and Scaling Autono...
IT IDOL Technologies
 
PPTX
history of c programming in notes for students .pptx
Vijayakumari829030
 
PDF
Softaken Excel to vCard Converter Software.pdf
markwillsonmw004
 
PDF
Design an Analysis of Algorithms II-SECS-1021-03
DilanEscobar1
 
PPTX
Odoo POS Development Services by CandidRoot Solutions
CandidRoot Solutions Private Limited
 
PDF
Upgrade and Innovation Strategies for SAP ERP Customers
Virendra Rai, PMP
 
PDF
How to Migrate SBCGlobal Email to Yahoo Easily
raymondjones7273
 
PDF
How Creative Agencies Leverage Project Management Software.pdf
Orangescrum
 
PDF
Adobe Illustrator 28.6 Crack My Vision of Vector Design
ghrom2211g
 
PDF
Which alternative to Crystal Reports is best for small or large businesses.pdf
Varsha Nayak
 
PDF
Wondershare Filmora 15 Crack With Activation Key [2025
ghrom2211g
 
PDF
Nekopoi APK 2025 free lastest update
umarali35kp
 
Internet Downloader Manager (IDM) Crack 6.42 Build 42 Updates Latest 2025
itskinga12
 
System and Network Administraation Chapter 3
jaramharo
 
EN-Survey-Report-SAP-LeanIX-EA-Insights-2025.pdf
deepakkhaitan3
 
Reimagine Home Health with the Power of Agentic AI​
AutomationEdge Technologies
 
Operating system designcfffgfgggggggvggggggggg
rmskumara09
 
System and Network Administration Chapter 2
jaramharo
 
Audit Checklist Design Aligning with ISO, IATF, and Industry Standards — Omne...
rohnjim07
 
Essential Infomation Tech presentation.pptx
pradeepjava2016
 
Agentic AI : A Practical Guide. Undersating, Implementing and Scaling Autono...
IT IDOL Technologies
 
history of c programming in notes for students .pptx
Vijayakumari829030
 
Softaken Excel to vCard Converter Software.pdf
markwillsonmw004
 
Design an Analysis of Algorithms II-SECS-1021-03
DilanEscobar1
 
Odoo POS Development Services by CandidRoot Solutions
CandidRoot Solutions Private Limited
 
Upgrade and Innovation Strategies for SAP ERP Customers
Virendra Rai, PMP
 
How to Migrate SBCGlobal Email to Yahoo Easily
raymondjones7273
 
How Creative Agencies Leverage Project Management Software.pdf
Orangescrum
 
Adobe Illustrator 28.6 Crack My Vision of Vector Design
ghrom2211g
 
Which alternative to Crystal Reports is best for small or large businesses.pdf
Varsha Nayak
 
Wondershare Filmora 15 Crack With Activation Key [2025
ghrom2211g
 
Nekopoi APK 2025 free lastest update
umarali35kp
 

Building a full-stack app with Golang and Google Cloud Platform in one week

  • 1. Memes in the Cloud – Building a full-stack app with Golang and Google Cloud Platform in one week Dr. Felix Raab | Head of Engineering @ KI Labs Munich | ki-labs.com [email protected] | medium.com/@fe9lix
  • 3. SCOPE OF TALK Case Study Project idea and journey for an MVP finished within one week
  • 4. SCOPE OF TALK Case Study Project idea and journey for an MVP finished within one week Software Engineering for Cloud Apps The “full” stack: Frontend, Backend, Build, Deployment, Logging… Towards the end of the talk: Software Engineering practices in Go
  • 5. SCOPE OF TALK Case Study Project idea and journey for an MVP finished within one week Software Engineering for Cloud Apps The “full” stack: Frontend, Backend, Build, Deployment, Logging… Towards the end of the talk: Software Engineering practices in Go Memes At the heart of the app itself – consequently, Memes to illustrate some opinionated views
  • 6. BACK AT MY PREVIOUS EMPLOYER… Hours claiming – trying not get “shitlisted”… because the boss would be notified!
  • 9. Idea – Every Friday… Schedule an hours claim reminder mail containing a meme, to myself.
  • 12. FIRST: HOW TO CHOOSE A CLOUD? …when you can start from scratch – no corporate constraints, no restrictions, no Frankfurt.
  • 13. LOOK AT THE HISTORY OF CLOUD COMPANIES
  • 14. LOOK AT THE HISTORY OF CLOUD COMPANIES
  • 15. LOOK AT THE HISTORY OF CLOUD COMPANIES
  • 16. LOOK AT THE HISTORY OF CLOUD COMPANIES
  • 17. LOOK AT THE HISTORY OF CLOUD COMPANIES MICROSOFT AZURE
  • 18. LOOK AT THE HISTORY OF CLOUD COMPANIES MICROSOFT AZURE AMAZON WEB SERVICES
  • 19. LOOK AT THE HISTORY OF CLOUD COMPANIES MICROSOFT AZURE AMAZON WEB SERVICES GOOGLE CLOUD PLATFORM
  • 20. LOOK AT THE HISTORY OF CLOUD COMPANIES MICROSOFT AZURE AMAZON WEB SERVICES GOOGLE CLOUD PLATFORM Enterprise
  • 21. LOOK AT THE HISTORY OF CLOUD COMPANIES MICROSOFT AZURE AMAZON WEB SERVICES GOOGLE CLOUD PLATFORM Enterprise Ops
  • 22. LOOK AT THE HISTORY OF CLOUD COMPANIES MICROSOFT AZURE AMAZON WEB SERVICES GOOGLE CLOUD PLATFORM Enterprise Ops S(R)E
  • 23. –Brave New Geek “Multi-Cloud Is a Trap” https://bravenewgeek.com/multi-cloud-is-a-trap/
  • 24. WORKS LIKE YOU WOULD EXPECT IT…
  • 25. WORKS LIKE YOU WOULD EXPECT IT… Service Offerings used to build MemeMail
  • 26. WORKS LIKE YOU WOULD EXPECT IT… Service Offerings used to build MemeMail More on that later…
  • 27. WORKS LIKE YOU WOULD EXPECT IT… Service Offerings used to build MemeMail More on that later… API access, permissions, config…
  • 28. WORKS LIKE YOU WOULD EXPECT IT… Service Offerings used to build MemeMail More on that later… CI/CD API access, permissions, config…
  • 29. WORKS LIKE YOU WOULD EXPECT IT… Service Offerings used to build MemeMail More on that later… CI/CD Database (NoSQL document store) API access, permissions, config…
  • 30. WORKS LIKE YOU WOULD EXPECT IT… Service Offerings used to build MemeMail More on that later… CI/CD Database (NoSQL document store) Object Storage (Blobs…) API access, permissions, config…
  • 31. WORKS LIKE YOU WOULD EXPECT IT… Service Offerings used to build MemeMail More on that later… CI/CD Database (NoSQL document store) Object Storage (Blobs…) Task Queue (with scheduling!) API access, permissions, config…
  • 32. WORKS LIKE YOU WOULD EXPECT IT… Service Offerings used to build MemeMail More on that later… CI/CD Database (NoSQL document store) Object Storage (Blobs…) Task Queue (with scheduling!) Logging… API access, permissions, config…
  • 33. The Frontend – Diving into the world of JavaScript? https://exceptionnotfound.net/big-ball-of-mud-the-daily-software-anti-pattern/
  • 34. THE FULLSTACK IN GO – SO HOW ABOUT WEBASSEMBLY (WASM)?
  • 37. NO! BECAUSE… Readability, Debugging, Size…
 (but maybe in the future)
  • 39. NO! BECAUSE… Learning curve, different paradigm, transpiling to JS, libraries… – remember, we have one week to finish!
  • 40. VANILLA JS (ES 6)! 
 BUT WHICH FRAMEWORK?
  • 43. RESIST THE TEMPTATION TO… Also, do not use Github Stars as your only criterion! Popularity is one thing…
  • 45. HOW TO CHOOSE 1) Does it solve your problem in a simple way? Rendering the frontend and adding interaction without sprinkling jQuery calls throughout your code base.
  • 46. HOW TO CHOOSE 1) Does it solve your problem in a simple way? Rendering the frontend and adding interaction without sprinkling jQuery calls throughout your code base. 2) Look at the quality of the documentation! Because you need to read it and be able to understand it – quickly!
  • 47. VUE.JS SEEMS TO MATCH. BUT WHICH ARCHITECTURE?
  • 48. SO MANY APPROACHES… …MVVM, Flux, Redux, SAM, ELM Architecture…? What is the essence?
  • 51. STATE MUTATION Take notice when somebody tells you that you should or can entirely avoid mutating state.
  • 53. MUTATING STATE. HERE’S HOW… 1) Put your entire app state into a single model Avoid primitive obsession – use proper objects! This is your single source of truth.
  • 54. MUTATING STATE. HERE’S HOW… 1) Put your entire app state into a single model Avoid primitive obsession – use proper objects! This is your single source of truth. 2) Dispatch Actions from the UI to trigger a state mutation Do not yet mutate the state in the action itself! Actions are intents with payloads.
  • 55. MUTATING STATE. HERE’S HOW… 1) Put your entire app state into a single model Avoid primitive obsession – use proper objects! This is your single source of truth. 2) Dispatch Actions from the UI to trigger a state mutation Do not yet mutate the state in the action itself! Actions are intents with payloads. 3) Accept or reject the state mutation in your model At the end of your (async.) action, “commit” / “propose” a new value to the model.
  • 56. MUTATING STATE. HERE’S HOW… 1) Put your entire app state into a single model Avoid primitive obsession – use proper objects! This is your single source of truth. 2) Dispatch Actions from the UI to trigger a state mutation Do not yet mutate the state in the action itself! Actions are intents with payloads. 3) Accept or reject the state mutation in your model At the end of your (async.) action, “commit” / “propose” a new value to the model. 4) Update the UI when the state changes Derive the state to render from your model, e.g. by UI bindings.
  • 57. VUEX.JS KIND OF SUPPORTS THAT PATTERN
  • 58. –Ryan Dahl “[...] if you’re building a server, I can’t imagine using anything other than ” THE BACKEND.
  • 60. HOW TO BUILD? Go 1.11 Because Go Modules!
  • 61. HOW TO BUILD? Go 1.11 Because Go Modules! Docker To be flexible with Go versions
 Multi-stage build!
  • 62. HOW TO BUILD? Go 1.11 Because Go Modules! Docker To be flexible with Go versions
 Multi-stage build! entr + Makefile No Rake, Grunt, Gulp, NPM, Yarn – Makefile + Bash Script fine! Check entrproject.org
  • 63. APP ENGINE – START SIMPLE
  • 64. APP ENGINE – START SIMPLE
  • 65. APP ENGINE – START SIMPLE App Engine Flex You can migrate to Kubernetes (GKE) later if you wish to – but for your MVP, don’t waste time managing a cluster.
  • 66. APP ENGINE – START SIMPLE App Engine Flex You can migrate to Kubernetes (GKE) later if you wish to – but for your MVP, don’t waste time managing a cluster. Use defaults Start with App Engine default options and auto-scaling. Nobody knows how much traffic you will get. Watch and see what happens.
  • 69. YES AND NO! Expose your services as API to the frontend Frontend is rendered via a Go template. On that rendered page, a Single Page App can run in memory and call your backend API. Use Go templates for other static pages. Makes routing easier.
  • 70. YES AND NO! Expose your services as API to the frontend Frontend is rendered via a Go template. On that rendered page, a Single Page App can run in memory and call your backend API. Use Go templates for other static pages. Makes routing easier. But no need to create two deployment units No need for premature optimisation (scaling). One Go binary is simpler than two Go binaries! 
 Static assets are loaded from the file system in your container.
  • 71. CI/CD
  • 72. CI/CD Google Cloud Build Will trigger and deploy when you push to your Git repo. Maintaining your own Jenkins server and setting up a build pipeline can be more time-consuming than you might think.
  • 73. CI/CD Google Cloud Build Will trigger and deploy when you push to your Git repo. Maintaining your own Jenkins server and setting up a build pipeline can be more time-consuming than you might think. App Engine Deployment Straightforward versioning and service concept via DNS – version.service.appname Promoting app to production, traffic splitting etc. – 
 supported out of the box
  • 76. The cloud can be mean and slow.
  • 77. PLAYGROUNDS SAVE TIME Create a GCP “Playground” project Got stuck with Cloud Datastore (vs. Cloud Firestore) and 
 Cloud Tasks (only certain EU region). Led me to test service offerings first via playground.
  • 79. SO MANY LAYERS AND CONCEPTS Also, ask yourself : Is there a rich domain? Or are you really building a CRUD app?
  • 82. Take notice when nobody tells you to separate functionality into lots and lots of really small methods and delegating objects.
  • 83. A QUESTION OF PHILOSOPHIES?
  • 84. A QUESTION OF PHILOSOPHIES?
  • 85. A QUESTION OF PHILOSOPHIES? Robert Martin (Uncle Bob) http://2017.agilesummit.gr/speakers/uncle-bob/
  • 86. A QUESTION OF PHILOSOPHIES? John Ousterhout https://www.youtube.com/watch?v=bmSAYlu0NcY Robert Martin (Uncle Bob) http://2017.agilesummit.gr/speakers/uncle-bob/
  • 87. DEEP VS SHALLOW MODULES
  • 88. DEEP VS SHALLOW MODULES Shallow ModuleDeep module Interface Functionality
  • 89. DEEP VS SHALLOW MODULES Shallow Module “The best modules are deep: they allow a lot of functionality to be accessed through a simple interface. A shallow module is one with a relatively complex interface, but not much functionality: it doesn’t hide much complexity.” 
 – From A Philosophy of Software Design, John Ousterhout Deep module Interface Functionality
  • 90. EXAMPLE OF A DEEP MODULE Meme Image Generation Package “meme”, image.go: Simple interface, a lot of functionality.
  • 91. PASS-THROUGH CODE TENDS TO BE SHALLOW – BUT HOW MUCH SEPARATION?
  • 93. Separate the outside from the inside Kind of onion, just fewer layers
  • 94. Separate the outside from the inside Kind of onion, just fewer layers Outside (package http) Protocol, routing (gorilla/mux), handlers
  • 95. Separate the outside from the inside Kind of onion, just fewer layers Outside (package http) Protocol, routing (gorilla/mux), handlers Inside (package meme) Core, your actual (business) functionality
  • 98. IMPLICIT INTERFACE CONFORMANCE Awesome Golang feature, but here…
  • 99. IMPLICIT INTERFACE CONFORMANCE Awesome Golang feature, but here…
  • 100. IMPLICIT INTERFACE CONFORMANCE Awesome Golang feature, but here…
  • 101. IMPLICIT INTERFACE CONFORMANCE Awesome Golang feature, but here… To be able to inject a different implementation, you would need to either create an interface that mirrors the datastore api or create a generic interface -> shallow wrapper
  • 102. IMPLICIT INTERFACE CONFORMANCE Awesome Golang feature, but here… To be able to inject a different implementation, you would need to either create an interface that mirrors the datastore api or create a generic interface -> shallow wrapper Have a look at google/go-cloud for unstructured binary storage (supports GCP and AWS)
  • 103. STRONGER ARGUMENT FOR AN INTERFACE?
  • 104. STRONGER ARGUMENT FOR AN INTERFACE? Logging Needed almost everywhere! But Go’s default logging has limitations.
  • 105. STRONGER ARGUMENT FOR AN INTERFACE? Logging Needed almost everywhere! But Go’s default logging has limitations. Even better: Structured Logging Implicit conformance to uber-go/zap for structured logging
  • 106. STRONGER ARGUMENT FOR AN INTERFACE? Logging Needed almost everywhere! But Go’s default logging has limitations. Even better: Structured Logging Implicit conformance to uber-go/zap for structured logging
  • 107. HOW TO HANDLE CROSS- CUTTING CONCERNS…?
  • 109. CONTEXT OBJECT PATTERN Reduce coupling of method parameters Instead of passing the logger through method parameters, pass a Go context object through middleware.
  • 110. CONTEXT OBJECT PATTERN Reduce coupling of method parameters Instead of passing the logger through method parameters, pass a Go context object through middleware.
  • 111. CONTEXT OBJECT PATTERN Reduce coupling of method parameters Instead of passing the logger through method parameters, pass a Go context object through middleware. Still not ideal, but good enough? Also see: https://medium.com/@gosamv/using-gos-context-library-for-logging-4a8feea26690
  • 114. FINALLY, BEING CONSISTENT… Strong Consistency After creating, the user should see the most recent list of meme reminders 
 (strong consistency supported by Cloud Datastore)
  • 115. FINALLY, BEING CONSISTENT… Strong Consistency After creating, the user should see the most recent list of meme reminders 
 (strong consistency supported by Cloud Datastore) Eventual Consistency Meme detail view might not have been generated and stored yet – 
 but you can always apologise to the user. Eventual consistency is often fine.
  • 117. CONCLUSION Keep it simple (but not stupid!) Reduce the number of “things” you need to deal with – both from an architecture and a product perspective.
  • 118. CONCLUSION Keep it simple (but not stupid!) Reduce the number of “things” you need to deal with – both from an architecture and a product perspective. Challenge existing “best practices” Have you been brainwashed by cargo cults in the past? The “best” practices always depend on the context and scope.
  • 119. CONCLUSION Keep it simple (but not stupid!) Reduce the number of “things” you need to deal with – both from an architecture and a product perspective. Challenge existing “best practices” Have you been brainwashed by cargo cults in the past? The “best” practices always depend on the context and scope. Develop end-to-end Allows you to make better decisions for the entire system – and to iterate quickly for your MVP!