Over the last few weeks, we have been publishing a few articles about the Live DevOps Innovation Platform, and how we built it. But I’d like to take the opportunity to share some of the benefits that we, as Sandhata consultants, have seen – so far – as a result of building this new DevOps platform and the application Sandhata Bank.
We recently announced the arrival of our Live DevOps Innovation Platform built in-house here at Sandhata. I wanted to share some of the tools we have used for it so far, as well as my personal experiences on this platform, as it has been very interesting and a big learning experience for me.
Choices shape and define us. Past choices mould us into who we are today and the ones we make today shape who we become tomorrow. In this blog post, I will share a brief story of how my career choices have helped shape me into who I am today. After all, aren’t we are all ultimately responsible for our own actions?
DevOps is becoming a key element of business transformation for enterprises, as the speed of their development and release processes are critical to business success. But committing to embarking on a DevOps journey is just the first step. While some companies have been able to successfully embrace the culture change which underlies DevOps, others have experienced growing pains – especially when it comes to handling database tensions.
Having worked in the development side of projects for so long, donning a tester’s hat for some projects at my current workplace was a new experience, nevertheless a useful one. It was almost like starting from scratch. I always had this idea that testing was largely a manual process. Yes, I knew there was automation testing and I was aware of tools such as HPQC, QTP and so on. But, having never used them before, I was not sure how they were leveraged to test the multitude of requirements. So, here go a few of my observations when performing a tester role.
Results reporting is one of the key stages in the testing phase where the interested project participants or the stakeholders are presented with information on the test progress. Although many of the test automation tools have inbuilt reporting capability, the information may either be too low-level or technical, or it may not be fully relevant for management. As part of test process improvement, I’m working on a requirement to present the test results in an efficient way, so the management can visualise the current status of testing or the overall status for a test cycle, and make decisions accordingly.
Having worked with some of the popular EAI tools like TIBCO BW, Vitria Businessware and SAP PI, it’s time for me now to familiarize myself with something from the IBM product catalogue as well. IIB – IBM Integration Bus. It is the next product offering from IBM in the ESB range; an extension to Websphere Message Broker and Websphere ESB. Going forward, users of Websphere ESB and Message Broker, would have to migrate to IIB. So, here’s few of my initial thoughts when working with IIB.