just to be clear, I mean upvote over on <tracker.a...
# adobe
m
just to be clear, I mean upvote over on tracker.adobe.com ๐Ÿ˜„ (though the โž• here for visibility is definitely appreciated too)
๐Ÿ˜ 1
m
I'll mention it next product meeting too. There's a few things I'd like to see in the next push for the Builder product, maybe I can sneak this in.
๐Ÿ’ฏ 1
I also added a whale here for fun.
๐ŸŒŠ 1
๐Ÿ‘ 1
m
be interesting to run a poll in the cfml-general channel to see how many people run in containers vs right on the metal. dunno if Polly or some other slack plugin could be added to do that. might be a good carrot/stick to take to the product meeting. "uh, like 37% of our paying customers (in a totally scientific โ„ข๏ธ poll) can't use our new CF Builder... chop chop!" ๐Ÿ˜„
or maybe it's like 73% ๐Ÿคท
m
So, based on conversations I've had with our customers over the past 2 years, I've had ZERO who were using it in production. That's government, military, corporation. There's been one single customer who was looking to run in Docker, but they were running into issues (they were a mil client) with Docker not falling under their internal "allowed" lists. I have one customer who is education who runs all their development in Docker, then pushes out to local cloud that is run by their campus IT. They literally implemented that for the first time in October of last year.
Now, is this GOOD? No. I think Docker is a fantastic tool, and can be a part of a very efficient CI/CD workflow and software provisioning setup.
But the reality is that the smaller shops are really the ones making the case for this, and the big folks will follow-on, kind of like they always do. It is steering ships. The bigger the ship, the slower the turn.
m
re: ship size - totally. I think writing's on the wall for containers, and eventually enough people with Docker experience will filter into the bigger ships and start looking at the old guards like ๐Ÿคจ you... don't use containers here, huh? and help them start the turning process
m
Yes, this. I think domain knowledge will need to filter in.
There's still some fear about just exactly how things work. It is also on us at Adobe to help, by doing more education and supporting and loudly encouraging use of CF in containers.
m
agreed - excellent support, docs/guides, etc. will help, as will language like "if you're still running CF uncontainerized" vs "if you're trying to run CF in the Dockers, or something" ๐Ÿ˜„ Would love to see demos from the CF team just naturally show starting CF in a routine container before digging into subject matter, etc.
but I also realize Adobe itself is a big ship ๐Ÿ™‚
m
We all out here runnin in teh dockerz ๐Ÿ˜‰