Requests to APIs can be very complex and need a lot of options: hostname, API keys, session tokens and at the end the HTTP method, route to the ressource, parameters and so on. I thought about how to solve this requirement in a flexible and modular way, because the complexity in the connector to make Heimdall requests exploded by adding more and more.
Logos are needed in different formats and sizes: Apple touch icons, favicon and much more. And maybe they are needed in several projects.
Wouldn’t it be nice only store the logo one time at one place, all the projects use them and resize it to the needed formats and sizes?
Having periodically posts without much effort is easy to reach with the WordPress API. I will describe here what’s the use case and which solution I use.
Facebook has the feature to show a summary of a webpage by writing the URL into a post. I will describe which information Facebook use and how its possible to change them.
Using third party libraries or not is a hard decision for beginners. The advantages are not immediately visible in the first time and its so much faster to just start with exactly what you need.
In some scenarios (e.g. having a landing page with the login to the client) the assets needed for subsequent pages are known, can preloaded into the cache and speeds up their first page view.
Node.js is single threaded. To use the capacity of multi CPU environments clustering is needed. There are solutions already available, so just have a quick look at one of them.