So they build, they open source, they gain contributions from the community while sharing and eventually they shine. Well, that's script that the success stories happen...and keep happening.
Traditional enterprise solutioning and architecting are not that sexy, sometimes, as they're closed and have to mark "confidential" everywhere. And the adoption process may be very long and may not happen for some areas for ever for some reason.
Yes, we also can't survive without open source components as it's ubiquitous. But if the decision of purchasing commercial products is easier to make, sometimes the management may still go that way as consideration of risks (well, whatever they're) will always get into the mind first.
Now the goal for me is very straightforward: keep my hands dirty by exploring a "dream" workflow of DevOps even we can't fully utilize all the components by a daily basis.
I call it "from code to online services".
I know it's not new for some people and yes, I have to admit that it's a big topic.
But I'm going to walk it through with some topics like:
- My experiments of DevOps - Environment (see post here)
- My experiments of DevOps - Development of RESTful Web Services by Spring Boot, Jersey, Swagger (see post here)
- My experiments of DevOps - Continuous Integration
- Run Maven + Jenkins In Docker Container (see post here)
- Integrated CI Solution With Jenkins + Maven + docker-maven-plugin + Private Docker Registry, in Docker Containers! (see post here)
- My experiments of DevOps - Continuous Deployment (see post here)
And eventually the idea may look like this:
Okay, let's do it!... and appreciate any comments.
EDIT: As of today, 21 Oct 2016, this series of experiments has been completed. I may try more options for the DevOps exercises to gain more practices for sharing...
The World Wide Web permits you to work together from any piece of the world. Your physical area, with the exception of few cases is not that essential since you direct your business on the web.
ReplyDeletesearch firms