Verified Commit 711e170e authored by MrMan's avatar MrMan

More writing

parent adc1102a
......@@ -297,19 +297,11 @@ Heroku burst onto the scene in 2007 offering exactly this premise -- you provide
What if there was an easier way to isolate processes running on a machine *without* spinning up a complete VM.
# The Present - Container Orchestration #
Now that we have containers everywhere, how can we treat a group of machines as just a blob of resources for running containers?
# The Present - Container Orchestration (continued) #
## Kubernetes ##
# The Future #
## So where are backends going now/next? ##
# The Future - Less server-side rendering #
# The Future - More client-side rendering #
TODO
......@@ -320,6 +312,14 @@ Why?
- More efficient use of available resources on client devices
- Faster iteration for separate teams
# The Future - Container Orchestration #
Now that we have containers everywhere, how can we treat a group of machines as just a blob of resources for running containers?
Why?
- Consistent management of a pool of servers
# The Future - Functions as a Service #
TODO
......@@ -359,7 +359,7 @@ No one knows what the future will actually hold, but most of it is here, it's ju
\tiny
* https://en.wikiquote.org/wiki/William_Gibson
\* https://en.wikiquote.org/wiki/William_Gibson
# The End #
......@@ -377,3 +377,5 @@ I run a couple very small consultancies to support businesses in Japan and the U
- GAISMA G.K. (https://gaisma.co.jp)
- VADOSWARE LLC (https://vadosware.io)
Need help getting your organization to the future? I can help with that.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment