How can you tell when your organization needs to start building a modern data stack? Orchard Analytics provides technical data team services on flexible contracts. Reach out to Phil to learn more. The software abundance problem created the need for data tools, and now -- surprise -- there’s an abundance of data tools.

It’s now more than 30 years since the first website was born. Its purpose, you ask? To provide information about the World Wide Web, of course. In the three decades that have elapsed since then, we’ve created around 6 billion more websites. Some, like that inaugural site about the internet itself, are devoted to providing information. Others allow us to buy and sell products. Others give us access to photos, videos and other forms of media.

2020 has been a remarkable year, full of change and reinvention. Yet one thing remains the same, NodeSource Node.js binary downloads keep increasing month by month, providing millions of users around the world with the power of Node.js. Node By Numbers 2020 gives us important insights into the usage of Node.js across Linux environments and the Node.js community in general.

How vulnerable is your sensitive data? Your data policies may put this information at risk of being breached. An ad hoc approach for dealing with this data makes it difficult to maintain your organization’s cybersecurity. Data obfuscation holds the key to improving your security and making it easier to use your data, but it must be driven by your policies to be effective.

Are you asking yourself the question “what is no-code”? You’re not alone. The concept sounds almost too good to be true: developing your own software applications without ever having to learn a programming language like Java or Python. Even your most technophobic employee can become a star software developer thanks to the proliferation of no-code development tools.

Traditionally, companies purchased the technology they needed to complete tasks efficiently and accurately. Today’s technology doesn’t evolve in a straight line, though. It grows at an exponential rate that shortens the life span of tools. When technology moves so quickly, an organisations needs to adopt a hyper selective approach – and in doing so move towards the phenomenon of the ‘composable enterprise’.

When many CIOs look at their technology assets they often see a random collection of applications, legacy systems, microservices and hardware. It can be difficult to make sense of an organisations technology-stack and how these seemingly disparate components are integrated and connected.

In the previous posts in this series, we have discussed Kerberos, LDAP and PAM authentication for Kafka. In this post we will look into how to configure a Kafka cluster and client to use a TLS client authentication. The examples shown here will highlight the authentication-related properties in bold font to differentiate them from other required security properties, as in the example below. TLS is assumed to be enabled for the Apache Kafka cluster, as it should be for every secure cluster.

Why do we test? Testing proves that our application works properly. Traceability, or being able to trace requirements to test cases, forms the foundation of your testing strategy. Test traceability is the ability to link a test to a set of requirements and verify that the application works as expected. Traceability matters as your product scales. When your application is small, it’s easy to pinpoint what’s broken. Most of these requirements can be tracked in a spreadsheet.

Combining the best of data lakes and data warehouses.