Last week I discussed design considerations for APIs, given that APIs aren't applications and shouldn't be treated as such. At small scales, APIs that come along for the ride with bulky Web frameworks might be fine, but beyond that you're asking for trouble. If you're building an API that will serve a large number of clients, your API code should be thin and tight, as well as make liberal use of caching. Otherwise, the future headaches will be crippling.
- How to recover data from a corrupt hard drive or SSD with no backup on Mac: How to delete corrupted files on external Mac drive
- IBM offers advice on how to secure blockchain in the cloud
- Toy maker Maisto’s website pushed growing CryptXXX ransomware threat
- Phishing apps posing as popular payment services infiltrate Google Play
- Security pros concerned about Facebook payment expansion