2019/04/09: DevOpsDays Tokyo Day 1b

by Gene Kim on

#DevOpsDaysTokyo

Up: The Amazon Effect and What It Means for Open Source Software (Ippei Suzuki)

  • CreationLine: OpenStack, CNCF, Linux Foundation
  • OSS: permissiveness,
  • strong relationship: trust and partnership; higher degree of loyalty = stickiness
  • scale big and fast: inexpensive to grow a large community; monetization is based on this large community
  • buying into this model through acquisition
  • 40 companies have $100MM+ revenue based on COSS; $9.4T valuation on this table
  • Amazon effect: 50% of product searches start on Amazon; 2017 sales: $25B; operating margin is only 3.8%; most orgs fight by Prod Lifecycle (manufacturing, sales, delivery logistics, supply chain, warehouse return, customer support)
  • AmazonBasics threat: type in "batteries" and you'll see search results; Energizer 24 count: $12.99; AmazonBasics: 48 count: $12.49
  • now: AmazonBasic: in almost all categories
  • Amazon makes 53% of all eCommerce revenue
  • if you sell well on Amazon, they will create an AmazonBasics product and take share
  • AWS had 50% market share: now 33%
  • why open source at a Devops event?
  • OSS and DevOps; permissiveness
  • strong relationship: Culture
  • scale big and fast automation
  • OSS: OSI: Open Source Initiative: 10 rules
  • free redistribution; source code; derived works; license must not be specific to product; license must not retrict other software
  • FSF: 4 freedoms: freedom to use/change/distribute/distribute derivatives
  • FOSS licensing examples: BSD/Apache 2.0, LGPL, GPL, AGPL
  • open source fork
  • COSS models: open-core models: core is OSS, but closed source features around it
  • new breed of open source based licenses;
  • common clause: Kevin Wang (author of several OSS tools, including FOSSA); teamed up with Heather Meeker: "the world has changed a lot and the OSS/cloud ecosystem has a lot, too"
  • maybe OSS definition is outdated and needs to change: it's not a demand for change; but to initiate a conversation
  • you cn write on top of Common Clause licensed software, you can embed and redistribute it, and distribute and "sell" your product (as a SaaS)
  • you can provide consulting services
  • but, you cannot: sell a product that consists in substance of the Commons Clause software and does not add value (I.e., you cannot grab OSS at a price w/o adding value to it)
  • simple, but opposition has emerged: Simon Phipps (OSI), Andrew Updegrove, Drew DeVault; violates permissiveness principle
  • Another movement: Service Side Public License, based on GPL v3: introduced by MongoDB, intended to AGPL
  • definition: based on spirit of AGPL, but makes explicit the conditions for providing the software as a service
  • users need to publish the code when it's offered as a cloud service (no download, modification)

- it's to ensure that they're giving back to the community

  • @DevOpsDaysTokyo: The Amazon Effect and what that means to DevOps and Open Source by Ippei Suzuki has started🆕 #DevOpsDaysTokyo #room1 https://t.co/h6lfVGoPY7
  • these new breed of licensing models: they're targeting Amazon
  • Redis: RSAL: five new Redis modules; Redis is OSS and remains under BSD license

TODO

  • I've taken a bunch of pictures of slides
  • I'd like to mass upload them into this page, and have them renderedat the bottom w/o having to post on Twitter