🗂 Link: ‘Rijksoverheid al 4 jaar in de clinch met Oracle’

According to the confidential memo, Oracle’s routine tactic is to threaten based on incompliance and to maximize potential licensing issues. After that, software licenses and the looming costs of such licenses can be negotiated from such a beaten problem. The result can then be a relatively better than expected amount for the shocked customer, but is not a low amount.

Source: ‘Rijksoverheid al 4 jaar in de clinch met Oracle’

Link: Oracle’s Georges Saab on the Impact of Faster Java Releases

When the new six-month cadence was announced there was some talk about “release fatigue.” Have you seen that in the Java community?
It’s sort of like asking, if your kids had Christmas twice a year, do you think they’d experience “Christmas fatigue?” The parents might, I guess. What I’m hearing people say now is that they are seeing so much evidence that updating to 9 and finding the move to 10 and 11 so smooth, they’re excited about the new cadence and what’s coming down the pike.

Source: Oracle’s Georges Saab on the Impact of Faster Java Releases

Link: Oracle swings axe on cloud infrastructure corps amid possible bloodbath at Big Red

These US-based layoffs are part of a broad round of job cuts around the globe this month, said to range from 500 to 14,000 at the database giant. The biz employs about 140,000 worldwide.

All the articles say it’s in the cloud business.

Source: Oracle swings axe on cloud infrastructure corps amid possible bloodbath at Big Red

Link: The computational legacy is Oracle’s cloud opportunity today

The company said it was saving most of its cloud-native announcements for KubeCon in December, but highlighted its new managed Kubernetes service (OKE, launched in May), platinum-level membership in the Cloud-Native Computing Foundation and growing support of open source projects (e.g., Fn, a functions project; Terraform for Oracle Cloud orchestration) as evidence that it has turned over a new, developer-friendly leaf. Oracle acknowledges a credibility gap with developers, but notes that it is at the start of making a transition similar to the one Microsoft has largely accomplished. As part of this effort, it may pursue acquisitions that give it access to customers that will help change Oracle’s image and shift the culture within the company (perhaps similar to what IBM is hoping to accomplish by buying Red Hat).
Original source: The computational legacy is Oracle’s cloud opportunity today

Link: Amazon move off Oracle caused Prime Day outage in warehouse

The outage, which lasted for hours on Prime Day, resulted in over 15,000 delayed packages and roughly $90,000 in wasted labor costs, according to the report. Those costs don’t include all the lost hours spent by engineers troubleshooting and fixing the errors or any potential lost sales.

I assume Amazon has, and will save much more than that by moving off Oracle.
Original source: Amazon move off Oracle caused Prime Day outage in warehouse

Link: Oracle Gets Cloudy: What’s Behind Their Change in Financial Reporting?

“Oracle did announce during the earnings call that cloud revenue was $1.7B for the quarter, but failed to break that out between SaaS and the combined IaaS and PaaS, as was previously reported. Also, with BYOL, it is impossible to know if customers are using those licenses in the cloud or on-prem, thereby obfuscating their cloud performance, which is now the number one factor in determining Oracle’s success against its peers. Oracle is claiming customers are deploying BYOL licenses in the cloud immediately, or have plans to do so in the near future, but it is impossible to know for sure.”

Vendors switching from on-prem to public cloud is hella hard, often deadly.
Original source: Oracle Gets Cloudy: What’s Behind Their Change in Financial Reporting?

Link: CIOs planning to snub Oracle for other cloudy vendors – analyst

“Murphy has told clients that a survey of 154 CIOs revealed negative spending intentions towards Oracle, with CNBC reporting that his note said just 2 per cent of respondents said Oracle was their most integral vendor for cloud computing. In contrast, 27 per cent chose Microsoft and 12 per cent opted for Oracle CTO Larry Ellison’s cloudy nemesis Amazon. The analyst’s note added that CIOs have told the analysts they are migrating off Big Red and onto Microsoft SQL Server, Amazon databases and PostgreSQL.”
Original source: CIOs planning to snub Oracle for other cloudy vendors – analyst

Link: Happy as Larry: Why Oracle won the Google Java Android case • The Register

“To sum up, then: Google knew it needed a licence, didn’t get one, and tried to bluff it out.”
Original source: Happy as Larry: Why Oracle won the Google Java Android case • The Register

Link: “Google’s use of the Java API packages was not fair,” appeals court rules

I’ve never understood what’s going on here. I think it’s that Google decided to arrange Android SDK’s like Java API’s.
Original source: “Google’s use of the Java API packages was not fair,” appeals court rules

Link: “Google’s use of the Java API packages was not fair,” appeals court rules

I’ve never understood what’s going on here. I think it’s that Google decided to arrange Android SDK’s like Java API’s.
Original source: “Google’s use of the Java API packages was not fair,” appeals court rules

Link: As it shifts cloud focus to platform services, Oracle tries to hold on to its database legacy

‘“the way Oracle plans on differentiating itself from Amazon is by offering a complete suite of platform services at a higher level than infrastructure services,” Ellison said. Open-source databases like MySQL and MongoDB have become very popular with developers in the cloud era, but there are still lots of companies running Oracle databases on their own hardware as well as companies that want to maintain application compatibility with Oracle but through Oracle’s cloud services.’
Original source: As it shifts cloud focus to platform services, Oracle tries to hold on to its database legacy

Link: Oracle expands its autonomous technology across its cloud platform

“In a nutshell, Oracle Autonomous Cloud Platform will aim to automate patching, tuning and even data integration across its portfolio. Oracle’s return on investment pitch is that its autonomous platform frees up technology talent for higher-value tasks.”
Original source: Oracle expands its autonomous technology across its cloud platform

Hardware layoffs at Oracle

Oracle claims the company isn’t closing the Santa Clara facility with this reduction in force. Instead, “Oracle is refocusing its Hardware Systems business, and for that reason, has decided to lay off certain of its employees in the Hardware Systems Division.”

Those hardware employees appear to have been Oracle’s failing SPARC hardware department staffers. In mid 2016, Oracle claimed its new SPARC S7 processor would be offered on Oracle Cloud. The cloud is Oracle’s new revenue hope since its new software licensing revenue plummeted by 20 percent in its last quarter ended December 15. At the same time, Oracle’s hardware revenue had fallen 13 percent.

Link

Oracle acquiring Apiary, API design for the $660m (in 2020) API market

As for Oracle, the enterprise software vendor wants to use Apiary’s technology set to make its existing API Integration Cloud more robust. Oracle’s API product focuses primarily on services that help companies monetize and analyze APIs. Apiary provides more of a front-end platform for designing, creating and governing APIs. From Natalie Gagliordi f at ZDnet

From CrunchBase:

  • $8.55M in funding, over three rounds
  • Founded April, 2011.

Apigee was acquired, by Google, last year for $625m. Of course, they were public with (let’s hazard a guess) many, many more customers and revenue: $92.03m in FY2016, to be exact.

Back in September 2015, Carl Lehmann at 451 Research said they had 33 employees (up from 22 in Dec 2014) and estimated their revenue at $2-3m. Carl says, now, it’s “likely below $5m in annual revenue.”

What Apiary does

Apiary’s promise is to be quick and easy when it comes to managing the full life-cycle of API design. As their CEO, Jakub Nesetril, put it when I interviewed him in 2015:

It all starts with that first meeting when you’re thinking about building an API and you’re either kind of, you know, you’re inside meeting room ideating on a white board and then taking a photo of it and sending it to a co-worker, or summarizing it down into an email and sending it down to somebody else, saying hey, I just thought would could build something like this. That white board should be. And, if you do that it becomes, you know, we do a lot to try to make it super simple. We have a language that is like really, really simple for developers to write and we can write down a quick API in five minutes. It’s marked down, it’s like very organic, it’s very simple for developers.

What it creates for you, is creates this kind of common space, common language kind of when you talk about it that’s machine readable, human writable so it’s super simple but it’s also machine writable, and machine readable. The important aspect of it is that we take your white board, we take your … we build a language that we have API blue prints. It’s a… We take that API blueprint and we immediately create a API prototype, the moment you hit your first button. So, from day one when you’ve proposed your first API idea, your first resource you know, your first data structure. You have an API that’s sitting out there on the internet, somebody can query it and guess what, if they decide that the API is broken, that they would like to have a different resource, they would like to change the of a certain data structure, they would like add to it, whatever. They can go in, edit that out, click the save button and boom the API prototype is updated immediately.

Load in some enterprise governance and access controls, and you have something nice and useful. See him explaining more in this 2013 InfoQ interview.

Carl at 451 summarized the meat of what they do back in that 2015 report:

Apiary structures its API lifecycle management platform into five phases. The design phase includes the means to ensure API design consistency using a style guide, a collaborative editor and an approval process. The prototype phase includes productivity capabilities such as auto-generated code and a feedback loop for quality assurance. The implementation phase enables agile-inspired and test-driven development practices, helps deploy server code, and provides for framework integration. The delivery phase includes tools for automated documentation, offers code samples, guides the release of final client code, and offers SDKs. The feedback phase includes debugging, support and usage metrics.

The Money – grabbing part of the $3bn pie

Forrester threw out some API management market-sizing back in June of 2015 (there’s likely something more up-to-date behind their paywall):

We predict US companies alone will spend nearly $3 billion on API management over the next five years. Annual spend will quadruple by the end of the decade, from $140 million in 2014 to $660 million in 2020. International sales will take the global market over the billion dollar mark.

With Oracle’s foot-print in all of enterprise applications and IT (they own Java and share much of the JEE market with IBM), there’s likely some genuine synergies to be had. That is, Oracle could be in a position to boost Apiary sales way above what the tiny company could do on its own.

To be clear, as pointed out above, Apiary doesn’t do all that Apigee does. Apiary is just for the development/design time part of APIs, also providing documentation.

That’s helpful for sure, but I’d guess most of Forrester’s $3bn estimation is likely in actually running and managing APIs. And, in fact, it’s probably more realistic to put Apiary in the development tools/ALM TAM, which is probably in the low, single digit billions. That said, I’m guessing Forrester would put Apiary in their API management bucket; after all, it has “API” in it!

As more background, we talked about the API management market back back when the Apigee acquisition was announced both on Software Defined Talk and Pivotal Conversations.

Link