Read the latest blogs, news and views from Infomentum. (17)

It had been coming for a long time…

At the end of every month, developers scrambled to complete their timesheets, while the operations team were breathing down their necks, threatening them with sticks to get it done - and done right. The developers were left wondering why operations wanted their time logs so desperately. Surely they already knew what they had been working on? The operations team were scratching their heads as to why the developers didn’t do it; they had been reminded at the end of every month like clockwork, yet every month the same story. It was hugely frustrating for both sides, and was approaching boiling point. As soon as the Customer Experience team had a break between projects, we knew this was a top internal issue that had to be solved.

I’ve wanted to write something about Infomentum's scrum board since its inception in late 2012. Now seemed as good a time as any to share the story...

During an end of sprint retrospective, one of our developers Jakub said “I'm bored of the board.” That didn’t surprise me.

In the 'What are microservices (part 3)' we touched different approaches to building a microservices architecture. In this final post of series on microservices, I will discuss those approaches in more details. 

Wait! Have you read 'What are microservices' blog posts part 1 and part 2? You need to cover those out before reading on.

When it comes to microservices, the million dollar question is: “How do I decompose my monolith into microservices?”. Well, as you can imagine this can be done in many ways, and here I will be suggesting some guidelines.

I'm an Integration Consultant and part of Infomentum's wider integration team. As well as being a MuleSoft trainer, I'm a certified MuleSoft developer and an Oracle SOA suite specialist.

I’m going to pick up from last week’s post when we discussed the microservices definition, and looked at the alternative approach to microservices, aka the monolith. Make sure you read that before carrying on with this post.

Why is the microservices approach different? Let’s explore the main features one by one.

The discussion on microservices has exploded recently. It’s been heralded as the future. But is it really so new, or something more familiar than we think?

Well, let’s start by setting the scene; what are microservices?

Oracle Code Conferences started in March this year, in the red city itself - San Francisco. The event is doing the rounds worldwide, and I attended my local one in London last week with my Infomentum Colleagues. My initial thought was that it was really interesting to see how Oracle is attracting a different audience this time around; more technical oriented attendees, with a bigger spectrum of technical skills.

Infomentum are announcing a new partnership to help their customers to reach their Corporate Social Responsibility (CSR) objectives.

The digital transformation consultancy are proud to collaborate with Transcendent Media Capital, a global company, which specialises in the development of International Social Ventures (ISVs) between corporations and non-governmental organisations (NGOs) to tackle global issues.

In the words of Annie Dillard, “If we are blinded by darkness, we are also blinded by light”. Paradoxically, being in the light and having too many ideas can be as fruitless as being in the dark and having none. These were the opening words of Professor Verganti’s talk at Oracle’s Modern Business Experience London conference, which caught my attention. Two minutes in, I had my notepad out. For a long time, I had been a believer of ‘the more, the merrier’ when it comes to ideas, and had somehow paid no attention to how that compromises quality and value.