Devopsdays is self organising technical event by local community with support and guidelines from Devopsdays international organizations. After 10th years ago Devopsdays first initiated in Belgium, now Devopsdays event and movement has spread around the world. This years, Devopsdays 2019 held for two days in Jakarta, this was second times Jakarta hosted Devopsdays. With 14 speakers from various background and company covering topic about DevOps from managing people and machine. This years I have a chance to attend this event representing my company to learn more about DevOps. I have personal interest on this topics because it combining managing people, developing software, and IT operations with fast pace to give fast delivery to customer in the market. More information about Devopsdays from their website here and Devopsdays Jakarta 2019, also complete list of speakers here. Here some notes I’ve wrote from Devopsdays Jakarta 2019, and I combined and interpret from the speakers.

The Event

Devopsdays 2019 Jakarta held two days at BRI Corporate University Cilandak. Besides speakers there are open session, ignite session, and panel discussion. Open session is where topics divided into four, and audience are free to choose one of four topics available. Then ignite session are 3 speakers talking with presentation slide running automatically. Then the speaker are discussing in front of all audience in panel discussion session.

The DevOps

There are three keywords when it comes to DevOps. Collaborations, communications, and integrations. These three things that should be strengthen within teams in organizations. The point of the DevOps is shorten software development lifecycle with assistance of machine. But, DevOps is not about tools that the teams used to continuously integrate and deliver software. DevOps is a culture, a mindset that should be in everyone head.

An organizations that wants to shift they development method from traditional waterfall development should asses they IT Value Chain first to make sure that shifting needed. In order to compete with industry fast-paced development consideration to move to more faster delivery can’t be delayed anymore or some one will eat our cake. We know about agile software devlopment with scrum the must popular methodology. Scrum offer sprints that evaluated after two or three weeks. Scrum focus on the development side of the project. Then to make it faster and better we could use DevOps mindset to integrate with operations team. This is interesting because in many organizations, development and operation teams like two side of coins that have different perspective and their own ‘personal thought’ about the opposite team. Advancing development and operations with DevOps mindset and culture is something challenging but worth it. The DevOps model doesn’t require to create new division or team to handle ‘DevOps Process’. Back to the keyword ‘collaborations’, ‘communications’, and ‘integrations’, the DevOps is creating culture that everyone in the ‘Value chain’ or ‘delivery/development pipeline’ of module/features/project are responsible and have a sense of belonging to the project. This is the way of thinking and interact. Everyone must known each responsibility and willing to help each other.

I can vs I will

CI/CD

In DevOps, software must be delivered as fast as possible with high precision. There are some deployment strategy like red/black deployment or canary deployment. CI/CD (Continuous Integration/Continuous Delivery) is whole loop process of:

• Code
• Build
• Test
• Deploy
• Monitor
• and repeat…

Number one to three are covering CI process, and four and five covering CD process. This process repeat as soon as possible to get rapid feedback from customer and rapidly improve quality of the software. The idea of CI/CD when we develop software in a day, at the end of the day we commit the code and then the code will be build and deploy automatically to the production server within a minutes. If anything wrong happened to the code, we could rollback to the previous stable version.

Reference

The material of this post mainly comes from the speakers of the events. There I also get some reference that we could read it later to maximise our knowledge about software development and DevOps.

• The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations by Gene Kim, Jez Humble, Patrick Debois, and John Willis (Goodreads Review)
• DevOps for the Modern Enterprise: Winning Practices to Transform Legacy IT Organizations by Mirco Hering and Bhaskar Ghosh (Goodreads Review)
• The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win by Gene Kim, Kevin Behr, George Spafford (Goodreads Review)
• Mindset: The New Psychology of Success by Carol S. Dweck (Goodreads Review)
• Drive: The Surprising Truth About What Motivates Us by Daniel H. Pink (Goodreads Review)