Blog

Notes from the field – Spring Boot at Tesla and New Relic

I have written and spoken about Java’s staying power a lot over the years. It continues to be a thing. The rise of cloud native companies, disrupting industries, was seen by some as presaging the end of Java. But when startups grow up they turn into Java shops, or at least start extensively using Java. Why would a startup, built from the ground up to take advantage of the latest technologies for competitive advantage, even consider using Java? Apart from a couple of decades of virtual machine optimisation, a huge skills base, libraries for everything, and the fact it can be used to be build maintainable code, I mean. Our programming language rankings consistently show Java’s strength. One of the things that RedMonk identified some time ago is that frameworks drive programming language adoption. Without Rails, Ruby would never have grown so explosively. Node.js has a new framework of choice seemingly every week.

Recently Spring and Spring Boot have emerged as the key frameworks driving Java forward. Developer interest is off the charts. But alongside the data, a good anecdote or two can be helpful in understanding the landscape. A couple of stories caught my eye recently.

The first concerns New Relic, which was looking for a framework that best suited a containerised, microservices framework. New

How We Chose an Application Framework for New Relic Alerts. Here are the criteria New Relic used it its decision making:

  1. Extensibility: Spring Boot uses convention over configuration, but customization is straightforward. (For example, we use Jetty over the default Tomcat container.)
  2. Reduced friction: The framework handles boilerplate configuration and setup, such as logging, configuration, security, etc. That helps the team focus on business logic instead of plumbing.
  3. Pragmatism: The core offering focuses on currently adopted technologies for integrations and doesn’t try to predict needs that might arrive years in the future. It leaves bleeding-edge extensions up to the community.
  4. Familiarity with the underlying technology: Spring Boot is built on top of the Spring Framework and Java, both of which are strong suits of our team.
  5. Support: There’s an active open-source developer community for Spring Boot, and it’s backed by Pivotal, which has a vested interest in improving and expanding the framework.

Spring Boot also meets our criteria for containerization listed above:

  • Easy builds: For application building, it provides first-class Gradle build support out of the box.
  • Self-contained distributions: It produces an executable JAR file with all dependencies included, so there’s just one executable JAR to deploy.
  • Simple application execution: The executable JAR does not require additional commands or permissions to run.
  • Supportability: For support, it provides a collection of “actuator” HTTP endpoints that expose environment/configuration information, health status, runtime stats, and other data.

New Relic has been around since 2008, so it’s not exactly a new company. But it was built for and on the cloud.

So what about another company of note – Tesla? Tesla is a very cool company, making a huge impact. A few months back I was in Germany for an IBM IoT event and was lucky enough to sit with a number of German auto industry people at dinner. Not one of them was dismissive of Tesla. The threat is real, and they know it. Circling the wagon isn’t going to work. Tesla is a profoundly disruptive company. With car-as-a-service business models, and autonomous vehicles, the revolution is coming, and it is going to be electrified.

Tesla’s Mission is to accelerate the world’s transition to sustainable energy. Can you please just hurry up with that, Mr Musk?

I saw this pointer to a Tesla job ad for a software engineer to work on the company’s customer facing apps.

Here are some the requirements:

  • 6 to 10 Years of experience in web application design and development
  • Experience with micro-services architectures, Docker eco-system and API first approach with hands-on expertise in developing rest APIs supporting multiple versions
  • Hands-on design and development for customer facing applications that require high availability, concurrency, multi-tenancy, high scalability for a large global user base
  • Strong Core Java Experience with Expertise in enterprise Java technology eco-system including Spring Boot, JPA/Spring Data, maven, JUnit
  • Strong SQL Experience (MySQL, PostgreSQL, MSSQL)
  • Strong Web Services Experience (SOAP/REST)
  • Spring Experience (Spring Boot, Spring Batch)

Bottom line – there are some really interesting opportunities for Java developers out there. In the case of Tesla world-changing, even. Spring Boot is part of the skill set.

This piece can be read as a companion to my recent post about Dell, Pivotal and Digital Transformation. Being able to point at digital natives like New Relic and Tesla using your software makes it easier to convince enterprises of the value of making similar technical decisions.

 

 

full disclosure: Pivotal is a client. Opinions are our own.

(Read this and other great posts  @ RedMonk)

Infosys gives up its American Dream

Once dubbed the “Indian Accenture”, being the Indian heritage outsourcer with the high-end reputation, the firm now finds itself enduring, perhaps, the most difficult period of its history – and it could be poised to get a hell of a lot worse.

Vishal Sikka brought energy, fresh ideas, hope… and a Silicon Valley mindset to its leadership when he came aboard amidst his Design Thinking and jeans-to-work attitude just three years ago.  However, all Sikka’s energetic ideas and innovations have been largely forgotten over the past year, as the public spat with Founder Narayana Murthy gathered irritating momentum and completely slammed the brakes on the momentum Sikka had sparked.  Sikka had woken Infosys up to its potential and the Founders were more obsessed with his use of the corporate jet than making the acquisitions the firm needs to be competitive.

From the poster boys for innovative offshoring, epitomized in Thomas Friedman’s seminal “The World is Flat” through to the constant public interventions in corporate affairs by Murthy, Infosys has had a bumpy ride over the last decade of its short history. And to magnify its issues, all of Murthy’s interventions have been played out in public, with the Indian press the grateful recipient of endless reams of news fodder being provided by this corporate soap opera.

Vishal Sikka’s resignation grinds to a halt this public transition from the Founders’ generation to becoming a “normal” corporate company. Without a doubt, this episode will find its way into economics textbooks for future students to learn the lessons in strategy, corporate governance and beyond. However, at least decisive action has been taken, and Murthy and his founders can try and restore a stability that makes ends this public drama. This is just such a bad time to go through such a strategic leadership nightmare, when competition is at its most severe, with too many suppliers chasing too few contracts and margins under extreme pressure.  This is especially troubling when you consider Sikka has kept the revenue and profitability ship progressing well, maintaining profit margins close to 25% and revenue growth over 5%, even at a time when the industry growth is flat and political stances towards offshoring are heated, with several US deals being awarded to “Western” suppliers:

 

 

So what are the lessons that can be learned from all this?

Murthy is the dominant father figure of Infosys and he has made that very clear with his actions. As founding CEO, he is synonymous with the early success, the culture but, more crucially, with the decision-making at Infosys. When SD Shibullah, another of the Founders, took over it was difficult for him to step out of Murthy’s shadow. Shibullah’s “Infosys 3.0” strategy was designed to address the over-dependence on the US market (see interview) and rebalance the portfolio by building out IP-based platforms, namely the EdgeVerve portfolio. But he took also the bold step to sign the first Intelligent Automation partnership with IPsoft at the time. Yet, the sales engine continued to stutter which remained the dominant feature of Infosys recent history.

This provides the background to the stage on which Vishal stepped, when he was appointed CEO in June 2014 (see post). Vishal was not only the first “outsider” but more importantly not part of the Founders’ generation to take over the reins at Infosys. Being Indian, yet working in California with a strong product background from his time at SAP he ticked a lot of the boxes in order to return Infosys to its erstwhile glory as the beacon for innovation that Thomas Friedman had so eloquently and prominently described. Vishal’s strategy focused on aligning Infosys around automation and AI to re-emphasize the heritage in innovation and Design Thinking, but also to boost the balance sheet as the industry is going through the secular shift towards non-linear growth and outcome based offerings. This was underpinned by an influx of executives from SAP that were meant in particular to help driving the platform and product business.

However, the narratives around automation and AI were never succinctly explained and, more importantly, not driven consistently through the organizations. For instance, the teams at EdgeVerve were waiting for guidance from the teams at Mana and vice versa. And without consistent narratives, it was difficult for the sales teams to leverage those capabilities in client discussions. Similarly, Mana was announced with great fanfare as the answer to all automation challenges. What Mana actually is, is a compelling analytics engine. It took another Confluence (Infosys’ main customer event) this year to finally launch a holistic automation framework called Nia. But at this year’s Confluence, Vishal appeared to HfS as being despondent and at times disconnected leaving us to speculate that he might resign or is being pushed to step aside. Yet, when he did at this conference an AI tutorial, he appeared to have his old sparkle back. Innovation and discussions with thought-leaders seem to be his passion. And his passion offered something different to an often guarded corporate world.

Undoubtedly, current clients will have questions about where this leaves them. Not only was the firm’s latest CEO the driving force behind the firms shift to analytics, automation, and AI, but Vishal’s appointment also saw the CEO’s office take personal responsibility for key clients in a bid to strengthen relationships and develop and solidify revenues from current client engagements. The whole corporate strategy will change dramatically, should the new incumbent come in with different ideas, and in the process likely shake and disrupt progress to solidify client relationships.

The Bottom-line: Re-igniting the sales and marketing engine is critical

Infosys has to reignite the sales and marketing engine and prove it has genuine distinctiveness when competing with the likes of Accenture, Cognizant, TCS, HCL and Wipro. Clients need to know what Infosys stands for, and why they should pay the top dollars to invest in this company, when there is so much intense competition making more impressive noises at present. While Vishal Sikka hit the ground running with a whole suite of ideas and innovations, these have largely dissipated over the past year amidst the public infighting. Without consistent financial performances, all the innovations will more or less evaporate and Infy will be left battling it out for low-margin transactional IT contracts.  Infosys 4.0 (or whatever it ends up being called) needs a new dynamic CEO, it needs an aggressive sales leader, and a CMO that can articulate what the company is trying to do next and what it stands for. Merely parroting the insufferable fluff about digital and outcomes will not work – Infosys needs to lead India’s innovation, not merely to make up the numbers.

On the positive side, any incoming CEO will have a strong set of assets to build on, which have enjoyed significant investment. First and foremost, Infosys analytics and data management prowess, strong products including Finnacle as well as many automation assets integrated into the Nia framework.  There has also been solid investments in its US delivery, most notably in Indianapolis and Texas.  However, Vishal’s resignation is likely to complete the power shift back to Bangalore. Many of the California-based executives will either jump ship or be pushed out very quickly. The crucial question though is whether the group of Founders will continue to interfere in public or whether they finally take a back seat and demonstrate confidence in any incoming CEO and his executive team. If the latter is not being addressed, any new king will wear very old clothes.

(Cross-posted @ Horses for Sources)