- Transactive energy. Software that balances production and consumption. Devices are smart and can allocate power based on supply. Clouds over solar panels? Large office space building can reduce heating to compensate. There’s also a trading aspect — the market price for energy will fluctuate as production/consumption (supply/demand) change. Most are basing the market aspect on blockchain technology.
- Series A in about 8–9 months.
- Wrapped around Hyperledger: open source blockchains. Backed by Linux and IBM.
- Distributed ledger. Everyone can check of everyone. Think like a Google spreadsheet.
- Middleware between OS and DB.
- Remember CouchDB and Cassandra from Apache. The former supports mobile.
- Researched some blockchains and the Ethereum model.
- Popularity ranks for backends: https://db-engines.com/en/ranking. Oracle #1.
- BEA was an enterprise software company that got acquired by Oracle.
- B-B and B-C are marketing models: business to business and business to consumer.
- GCP, Google Cloud Platform, storage + analytics + ML.
- IBM Cloud is a huuuuge suite of tools: https://www.ibm.com/cloud/products.
- UDP is faster and doesn’t perform error handling. You could miss datagrams. TCP is heavier but provides all that handshaking.
- HTTP is stateless. Each request is entirely encapsulated and does not depend on other information. Cookies and server-side sessions kinda kinda violate this, but are usually disregarded. On the whole, an HTTP request is self-sufficient and depends on no other state.
- Application layer faces the user: HTTP, SSH, SMTP, etc.
- Transport layer then provides node-to-node: TCP, UDP, etc.
- Internet layer then provides network-to-network: IPv4, IPv6.
- You’ve got SOLID principles under the belt already, but summarized for memory: each thing should only do one thing, lower level utilities should be abstracted, and code should be written to be extended not modified (no concrete specifics in general places).