Posted on

NoSQL, the Cloud, and Java (Part 3): The Standards

The number of NoSQL databases is growing. There are already more than two hundred solutions divided into several categories, and this number has been increasing over time beyond popularity. One solution would be to create a standard API to simplify the use of those databases. After all, the behaviors are basic operations, but after all, what is the reason for not implementing this requirement? This article aims to discuss and update a point of these works related to the standards of NoSQL databases.

Within Info World, the article “The time for NoSQL standards is now” mentions that the critical point for related databases is that relational databases have standards. This pattern in relational databases allows, in addition to avoiding vendor lock-in, creating tools, API in programming languages, among other devices around SQL. If there is a NoSQL standard, the expectation is that the behavior will happen similarly.

Posted on

Moving Forward With Money-API, JSR 354: Motivation Behind the API

According to Wikipedia, money is any item or verifiable record that is generally accepted as payment for goods, services, and/or the repayment of debts in a particular country or socio-economic context. Money is represented by two parts: a numerical value and a currency. We deal with money in our programs every day, but the JDK doesn't provide a standard representation of wealth. What we need to know as developers is what data type is suitable for representing money.

The first attempt would be to use the primitive floating point types (double and float) that are available in the language. The author of Effective Java doesn't recommend using these types when precise values are required.