Organisation transformation often results in large software integration projects, which include several systems exchanging data to provide proper services to users. While on the surface, this may seem to be a technical challenge, the main problems lay outside of pure point-to-point data exchange. They are related to organisation structure and delivery maturity, which can vary between different parts of the system.
Introduced by Red Hat in early 2019, Quarkus is Java framework with a goal to make Java a leading platform in Kubernetes and serverless. It is cleverly built on top of a number of popular Java libraries and, what is new in its approach, it integrates closely with GraalVM and OpenJDK. This second part – runtime integration – is the main point here.
I would like to share my thoughts on our recent big story of the Java upgrade from 8 to 12. It was the first such significant upgrade since the beginning of the project in the middle of 2016.
Nowadays supplying Single Sign On mechanisms becomes more and more important for users convenience. Briefly – single user logged into one system can be automatically logged within other applications used across organization (internally and / or externally). As it is very often used in integration of various systems - reliable operation upon bigger load with good performance of this service becomes important.
One of the most crucial things about building software is productivity – we want to deliver new features and make it faster and faster to do so. But what about the productivity of the organic side of building software – i.e. the person who works as the developer?
Npm is commonly used software registry and there's a good chance that you're already using it in your project. It allows you to install any of over 600,000 packages and to publish your own. Although it's really popular and useful, there are few things you should consider when using it.