|
@copyconstruct | |||||
|
What are the biggest pain points you believe tooling can address in the next decade (2020-2029)?
I’ll go first:
- CI/CD. Jenkins is currently the CI gold standard and it’s a very low bar.
- Easier abstractions and paradigms for building infra. Kube is too low level + complex.
|
||||||
|
||||||
|
Cindy Sridharan
@copyconstruct
|
23. pro |
|
What I mean by “paradigms” is basically this:
Right now the compute spectrum is a bit of an embarrassment of immature riches; as an industry we need to innovate, experiment and educate more on how to pick the right compute option for the wide variety of workloads we already run.
|
||
|
|
||
|
Cindy Sridharan
@copyconstruct
|
23. pro |
|
How can FaaS be leveraged better and applied to existing problems to get better outcome? twitter.com/copyconstruct/…
Can traditional “PaaS” development be rethought from the ground up, given the low level primitives we now have (bare metal servers in the cloud, VMs, FaaS etc).
|
||
|
|
||
|
Cindy Sridharan
@copyconstruct
|
23. pro |
|
How awesome would it be if I as a developer didn’t have to fuck around with kubectl, terraform, cloud tooling etc.
If instead, the PaaS would let me choose where to run my app based on *app leve concerns* like latency, CPU usage, RPS, traffic patterns (bursty vs sustained) etc.
|
||
|
|
||
|
Cindy Sridharan
@copyconstruct
|
23. pro |
|
And transparently run my workload wherever it’s best suited to be run - be it in “containers” or in VMs or compiled down as a wasm instance and run on the “edge” in CDN POPs or by invoking a lambda function.
With all the debuggability and observability baked in out of the box.
|
||
|
|
||
|
Mark Collier 柯理怀
@sparkycollier
|
23. pro |
|
Have you looked at @ZuulCI ?
The Openstack community built it to handle thousands of developers contributing, with gated testing on patches, and it’s now used by BMW, Volvo and others + additional OSS projects at OpenDev.org (& the review workflow leverages gerrit).
|
||
|
|
||
|
Cindy Sridharan
@copyconstruct
|
23. pro |
|
Nope, but looks interesting. Definitely will look deeper, thanks.
|
||
|
|
||
|
Iheanyi Ekechukwu
@kwuchu
|
23. pro |
|
I hope GitHub Actions becomes the gold standard. 👀
|
||
|
|
||
|
Cindy Sridharan
@copyconstruct
|
23. pro |
|
Sure, for folks who can/want to outsource all their CI to GitHub or if Actions becomes something on-prem users can have access to or get to run themselves.
|
||
|
|
||
|
James Meickle
@jmeickle
|
23. pro |
|
A tool for doing feature branch work across code, infra, and data simultaneously and in prod. Right now this needs either highly skilled and high access employees, or a tremendous internal tooling investment across a dozen tools and the entire stack.
|
||
|
|
||
|
Steven Armstrong
@Steve9Armstrong
|
23. pro |
|
It exists and is called @ZuulCI
|
||
|
|
||