Skip to main content

Posts

Showing posts with the label api

REST

REpresentational State Transfer call from client to server get data back hypermedia as a engine to application state. self-descriptive messages http://www.ics.uci.edu/~fielding/pubs/dissertation/introduction.htm

Data as Software as Data

Better software for better data. Better data for better software. data chaos in json so for clarity make use of thrift

Hashicorp Vault

What is Vault? Vault is a tool for securely accessing  secrets . A secret is anything that you want to tightly control access to, such as API keys, passwords, certificates, and more. Vault provides a unified interface to any secret, while providing tight access control and recording a detailed audit log. A modern system requires access to a multitude of secrets: database credentials, API keys for external services, credentials for service-oriented architecture communication, etc. Understanding who is accessing what secrets is already very difficult and platform-specific. Adding on key rolling, secure storage, and detailed audit logs is almost impossible without a custom solution. This is where Vault steps in. The key features of Vault are: 1) Secure Secret Storage 2)  Dynamic Secrets 3)  Data Encryption 4)  Leasing and Renewal 5)  Revocation   Terms used in Vault   Storage Backend  - A storage backend is responsible for durable storage of  encrypted  data. Backends are not trusted by...

REST

REpresentational State Transfer call from client to server get data back hypermedia as a engine to application state. self-descriptive messages http://www.ics.uci.edu/~fielding/pubs/dissertation/introduction.htm