Explore >> Select a destination
|
You are here 
|
devopsian.net | ||
| | | | |
yos.io
|
|
| | | | | You're building an API. You develop a backend service with a few endpoints and deploy it to production. You publish several official language-specific API clients as well as an API documentation. The day ends on a happy note. The following day, a new feature is being added the API. You have to: Update the server implementation to support the new feature. Update all client libraries (one SDK for each supported platform and language.) Update the documentation. All the above must be consistent with each other. Also, the frontend team is blocked until your backend API is complete. You let out a heavy sigh. | |
| | | | |
feorlen.org
|
|
| | | | | ||
| | | | |
mherman.org
|
|
| | | | | Let's look at how to describe a RESTful API using Swagger and NodeJS. | |
| | | | |
nurkiewicz.com
|
|
| | | When choosing or learning a new programming language, type system should be your first question. How strict is that language when types don't really match? Will there be a conservative, slow and annoying compiler? Or maybe a fast feedback loop, often resulting in crashes at runtime? And also, is the language runtime trusting you know what you are doing, even if you don't? Or maybe it's babysitting you, making it hard to write fast, low-level code? Believe it or not, I just described static, dynamic, weak and strong typing. | ||
