Operations | Monitoring | ITSM | DevOps | Cloud

Despite all the hype from the big cloud providers the truth is that most organisations rely on hybrid infrastructures now and will do so for the foreseeable future. Typically, this includes on-premises infrastructure and at least two public cloud providers. This is not a step on a journey to being 100 per cent cloud, it is the strategic destination many have chosen.

Cloud computing can bring many benefits to financial services companies such as increased speed and agility, easier innovation and scalability. It is no wonder then that cloud adoption is set to continue increasing with 54% of financial services companies expected to have more than half of their entire IT footprint in public clouds in the next five years. However, despite the benefits that this can bring for financial services, it also brings a new set of challenges for financial market stability.

The demand for cloud services is rising. Databases have been popular tools for a long time. However, the landscape is changing, with cloud databases becoming increasingly popular.

This is the second post in a 2 part blog series on debugging, monitoring and tracing NodeJS Lambda applications. If you haven’t yet seen part 1, check it out here (it’s a great read!) Now let’s get back into our post with one of the most commonly experienced issues when it comes to Lambda functions, Cold Starts.

IT is now seen as integral to business rather than a cost center ripe for layoffs. Technology, people, and culture are worth protecting during economic contractions. A recent piece in Silicon Angle by Paul Gillin said out loud what I see firsthand: Cloud spending seems immune to budget reductions during contractions in the economy.