Documents in MongoDB have a unique object ID when they are created. How can we get around this to develop a more effective REST API when document lookups are involved?
It's easy to use Venn diagrams to explain JOINs, but when you think about it, they're not quite the right tool to use. That's where JOIN diagrams come in.
How many times have you reviewed a log file without the data key (secret decoder ring) that explains what everything means. When a user more informative and intuitive format like JSON or XML? It's not too hard to do and can be quite helpful. Here's an example.
Red Hat, Eclipse, and Eurotech have announced Eclipse Kapua — an end-to-end open source IOT cloud platform that combines and enhances several current solutions.
Oren Golan published an excellent piece on his blog this past weekend sharing an example of how Micro and NATS are providing microservices for financial modeling and Bitcoin visualization.
Sometimes tackling a problem in a single query isn't the best approach. We have a look at a scenario where a CASE statement is needed in a GROUP BY clause. What's the best way to handle this?