I was inspired by a post from 3AP company’s blog Using HATEOAS with REST APIs to tackle and explore the JSON-LD format in this article, explaining the problem it solves, where it assists users, and where it does not. No unrealistic hype, or RDF related terminology - only factual information.

JSON is commonly used as the format for data transfer via the Internet. It is easily understood and is supported in many places. However, while JSON has been very successful, it has one key limitation:

Imagine this: You have a new project, the design is ready, and you’ve started implementing the user interface (UI) components. However, the logic hasn’t been implemented, and the application isn’t up and running. Despite this, your customers are eager to see the initial UI progress. That’s where Storybook comes to the rescue!

Online insurance businesses face the enormous task of converting established products that were previously sold by a broker or sales agent into viable online products sold directly to consumers. Viability in this scenario means that a user can configure and understand an insurance offer without the help of a professional. So for one of our customers, our team set out to build a website selling insurance online.

How many times have you been in a situation where you had to implement a new UI into brand-new or existing applications? Suppose your designer provided you with a design and style guide; what would your approach to getting the given styles in place be?

“Unable to acquire JDBC Connection” is staring at you from your production logs. Your connection pool is running out of database connections. What do you do?