2016: DbOps definition
- Mercurial (TortoiseHg) vs Git (SourceTree)
- Redgate (Source Control, DLM Automation Suite)
- TFS Build vNext (2015)
- Database unit/integration tests
- Octopus Deploy
- TFS Release Management (2015)
Infrastruture as Code
- Powershell DSC
- Azure Resource Manager
During 2016 the main focus around DevOps was the its definition. My DevOps definition was built around databases operations and development (hence the title “DbOps”).
The plan was to cover the 3 stages of the deployment pipeline: source control, continuous integration and continuous deliver. And include infrastructure.
- Source Control
- Continued to use Flyway with Git, abandoning Mercurial.
- Unfortunately, I did not had lot of time and opportunities to use Redgate Source Control and ReadyRoll.
- Continuous Integration
- Went full gas with TFS (and VSTS) for building process.
- Tried tSQLt and DbFit. tSQLt suits best my use cases because allows to write unit tests using T-SQL and for that reason it’s more powerful than DbBit.
- Continuous Delivery
- Made the first approach to TFS/VSTS Release.
- Still preferring Octopus Deploy when compared with above one.
- Infrastructure as Code
- ARM templates (and PowerShell) became the only way to create and manage Azure resources.
- Made the first approach to Chef and Puppet. They are both very powerful and similar, but in my point of view Chef can be more friendly when learning.
At professional level, after more the 3 and half years I left Celfinet and joined Basecone. It was the right time for me to leave and start a new adventure.
Also, 2016 was my year as rookie speaker. It was great to share my talks, to learn with attendees and other speakers, to feel the community spirit.
In October 2016 it happened the first DevOps Porto community event/meetup. This community, created by me and my friend Miguel Alho, have the purpose to share, discuss and promote the DevOps culture, values and practices. For me was a big personal achievement.