Systems | Development | Analytics | API | Testing

Testing in production simply means testing new code changes in production, with live traffic, in order to test the system’s reliability, resiliency, and stability. It helps teams solve bugs and other issues faster, as well as effectively analyze the performance of newly released changes. Its overall purpose is to expose problems that can’t be identified in non-production environments for reasons that may include not being able to mimic the concurrency, load, or user behavior.

At Speedscale, we’re always trying to find ways to iterate faster and reduce developer toil. In line with that mission, we slant our engineering decisions towards using cutting edge tech because we usually move faster and it also allows us to help our customers later on when they upgrade their own tech stack. Recently, we had the opportunity to upgrade the communication channel between our api-gateway and react front end. This journey provided some unexpected benefits.

Large portions of software development budgets are dedicated for testing code. A new component may take weeks to thoroughly test, and even then mistakes happen. If you consider software defects as security issues then the concern goes well beyond an application temporarily crashing. Although even minor bugs can cost companies a lot of time to locate the bug, resolve it, retest it in lower environments, then deploy it back to production.

It seems like only yesterday that the cloud was considered the destination. For technology decision-makers, choices boiled down to: “Do I want this thing in my data center, or would it be better, cheaper and faster in the cloud?” The cloud was the place to be.

The exponential adoption of IT technologies over the past several decades has had a profound impact on organizations of all sizes. Whether it is a small, medium, or large enterprise, the need to create web applications while managing an extensive set of data effectively is high on every CIO’s priority list. As a result, there has been an ongoing effort to implement better approaches to software development, data analysis, and data management.

Massive tomes have been written on engineering management, but I thought it might be helpful to take a brief minute to discuss setting up your Founding Engineers (FE) for success. For this post I define FEs as the first wave of engineers hired after the founding team. This round of hiring usually takes place after seed funding has been secured and some semblance of initial product/market fit has been achieved.

DevOps merges operational and development teams to boost the speed of software development and ensure that the final product is delivered as clean and consistent as possible. Ultimately, DevOps allows teams to increase product quality and speed of delivery in even the most highly competitive environments. The idea of weaving together disparate teams to accelerate development might appeal to many organizations, but some common challenges may come up before implementing a DevOps environment.

Last month, we were proud to launch our Hitachi Kubernetes Service, a true storage-as-a-service (SaaS) offering to improve the performance and management of multiple Kubernetes environments. By enabling users to manage their clusters simply and securely across any major cloud provider and on premises, Kubernetes can play an instrumental role in businesses’ modernization efforts. It’s for this reason that we are always working to get it on the radar of our existing clients.

Java developers are unlikely to ever suffer from a lack of libraries, utilities, and programs at their disposal. There's no shortage of tools that offer niche as well as fundamental features. However, some tools undoubtedly stand out due to their popularity, usefulness, data representation, and in-tool features. These 8 tools listed below are often listed as some of the best Java development tools available on the market.