Network and information systems (NIS) and the essential functions they support play a vital role in society from ensuring the supply of electricity, water, oil and gas to the provisioning of healthcare and the safety of passenger and freight transport. In addition, computerized systems are performing vital safety-related functions designed to protect human lives. For […]… Read More
The post How to Achieve Compliance with NIS Directive appeared first on The State of Security.
Zero Trust is a new concept to many but one I believe will be of increasing importance over the coming years. With this post, I wanted to introduce newcomers to the concept, talk about why it’s an exciting approach to improving security, and explore how you can leverage File Integrity Monitoring (FIM) and Security Configuration […]… Read More
The post Tripwire Enterprise and Zero Trust appeared first on The State of Security.
Back in 2013, Dropbox was scaling fast.
The company had grown quickly by taking advantage of cloud infrastructure from Amazon Web Services (AWS), but when you grow rapidly, infrastructure costs can skyrocket, especially when approaching the scale Dropbox was at the time. The company decided to build its own storage system and network — a move that turned out to be a wise decision.
In a time when going from on-prem to cloud and closing private data centers was typical, Dropbox took a big chance by going the other way. The company still uses AWS for certain services, regional requirements and bursting workloads, but ultimately when it came to the company’s core storage business, it wanted to control its own destiny.
Storage is at the heart of Dropbox’s service, leaving it with scale issues like few other companies, even in an age of massive data storage. With 600 million users and 400,000 teams currently storing more than 3 exabytes of data (and growing) if it hadn’t taken this step, the company might have been squeezed by its growing cloud bills.
Controlling infrastructure helped control costs, which improved the company’s key business metrics. A look at historical performance data tells a story about the impact that taking control of storage costs had on Dropbox.
In March of 2016, Dropbox announced that it was “storing and serving” more than 90% of user data on its own infrastructure for the first time, completing a 3-year journey to get to this point. To understand what impact the decision had on the company’s financial performance, you have to examine the numbers from 2016 forward.
There is good financial data from Dropbox going back to the first quarter of 2016 thanks to its IPO filing, but not before. So, the view into the impact of bringing storage in-house begins after the project was initially mostly completed. By examining the company’s 2016 and 2017 financial results, it’s clear that Dropbox’s revenue quality increased dramatically. Even better for the company, its revenue quality improved as its aggregate revenue grew.
In Marc Benioff’s book, Trailblazer, he tells the tale of how Steve Jobs planted the seeds of the idea that would become the first enterprise app store, and how Benioff eventually paid Jobs back with the gift of the AppStore.com domain.
While Salesforce did truly help blaze a trail when it launched as an enterprise cloud service in 1999, it took that a step further in 2006 when it became the first SaaS company to distribute related services in an online store.
In an interview last year around Salesforce’s 20th anniversary, company CTO and co-founder Parker Harris told me that the idea for the app store came out of a meeting with Steve Jobs three years before AppExchange would launch. Benioff, Harris and fellow co-founder Dave Moellenhoff took a trip to Cupertino in 2003 to meet with Jobs. At that meeting, the legendary CEO gave the trio some sage advice: to really grow and develop as a company, Salesforce needed to develop a cloud software ecosystem. While that’s something that’s a given for enterprise SaaS companies today, it was new to Benioff and his team in 2003.
As Benioff tells it in his book, he asked Jobs to elucidate on what he meant by an application ecosystem. Jobs replied that how he implemented the idea was up to him. It took some time for that concept to bake, however. Benioff wrote that the notion of an app store eventually came to him as an epiphany at dinner one night a few years after that meeting. He says that he sketched out that original idea on a napkin while sitting in a restaurant.
“One evening over dinner in San Francisco, I was struck by an irresistibly simple idea. What if any developer from anywhere in the world could create their own applications for the Salesforce platform? And what if we offered to store these apps in an online directory that allowed any Salesforce user to download them?”
Whether it happened like that or not, the app store idea would eventually come to fruition, but it wasn’t originally called the AppExchange as it is today. Instead, Benioff says he liked the name AppStore.com, so much so that he had his lawyers register the domain the next day.
When Benioff talked to customers prior to the launch, while they liked the concept, they didn’t like the name he had come up with for his online store. He eventually relented and launched in 2006 with the name AppExchange.com instead. Force.com would follow in 2007, giving programmers a full-fledged development platform to create applications, and then distribute them in AppExchange.
Meanwhile, AppStore.com sat dormant until 2008 when Benioff was invited back to Cupertino again for a big announcement around iPhone. As Benioff wrote, “At the climactic moment, [Jobs] said [five] words that nearly floored me: ‘I give you App Store.”
Benioff wrote that he and his executives actually gasped when they heard the name. Somehow, even after all that time had passed since that the original meeting, both companies had settled upon the same name. Only Salesforce had rejected it, leaving an opening for Benioff to give a gift to his mentor. He says that he went backstage after the keynote and signed over the domain to Jobs.
In the end, the idea of the web domain wasn’t even all that important to Jobs in the context of an app store concept. After all, he put the App Store on every phone, and it wouldn’t require a website to download apps. Perhaps that’s why today, the domain points to the iTunes store, and launches iTunes (or gives you the option of opening it).
Even the App Store page on Apple.com uses the sub-domain ‘app-store’ today, but it’s still a good story of how a conversation between Jobs and Benioff would eventually have a profound impact on how enterprise software was delivered, and how Benioff was able to give something back to Jobs for that advice.
It would be hard to top the 2018 enterprise M&A total of a whopping $87 billion, and predictably this year didn’t come close. In fact, the top 10 enterprise M&A deals in 2019 were less than half last year’s, totaling $40.6 billion.
This year’s biggest purchase was Salesforce buying Tableau for $15.7 billion, which would have been good for third place last year behind IBM’s mega deal plucking Red Hat for $34 billion and Broadcom grabbing CA Technologies for $18.8 billion.
Contributing to this year’s quieter activity was the fact that several typically acquisitive companies — Adobe, Oracle and IBM — stayed mostly on the sidelines after big investments last year. It’s not unusual for companies to take a go-slow approach after a big expenditure year. Adobe and Oracle bought just two companies each with neither revealing the prices. IBM didn’t buy any.
Microsoft didn’t show up on this year’s list either, but still managed to pick up eight new companies. It was just that none was large enough to make the list (or even for them to publicly reveal the prices). When a publicly traded company doesn’t reveal the price, it usually means that it didn’t reach the threshold of being material to the company’s results.
As always, just because you buy it doesn’t mean it’s always going to integrate smoothly or well, and we won’t know about the success or failure of these transactions for some years to come. For now, we can only look at the deals themselves.
Dining, hospitality and entertainment corporation Landry’s notified customers of a security incident that might have affected their payment card data. On December 31, Landry’s revealed that it first learned of the incident after it detected unauthorized activity on the payment processing systems for its restaurant outlets as well as its food and beverage locations. The […]… Read More
The post Landry’s Notifies Customers of Payment Card Incident appeared first on The State of Security.
