Automating a process can be complex, especially when it’s a long-running process with many steps and complex business rules, cross-cutting multiple departments and systems in an enterprise. To automate a process like this from end to end, you’ll need a process automation strategy and software. Assuming you’ve ticked both of those boxes, the next step is putting those things to work, which is the focus of this post.

As organizations continue to migrate to the cloud and search for ways to reduce costs, Perforce has released Helix Core 2023.2 – giving users the ability to connect their archive depots to S3-backed (or S3-compatible) cloud object storage. S3 storage support offers users a durable and convenient solution that grows automatically and indefinitely. In the following article I explain S3 storage, diving into the benefits of using S3 storage, and how to get started using S3 Storage within Helix Core.

A data lake is a main storage repository that can hold vast amounts of raw, unstructured data. A data lake is not the same as a data warehouse, which maintains data in structured files. Five key takeaways about data lake tools: A data warehouse uses a hierarchical structure, whereas the architecture of a data lake is flat.

Wondering which is the best way to host your business applications and IT infrastructure? Many enterprises are transitioning from on-premises software to cloud computing. On the other hand, several established companies are investing their capital in on-premises software. Both of these deployment models have advantages and drawbacks, and you can zero in on the right option by considering your specific requirements.

Reusable UI components are user interface widgets or elements that can be used in various places in a web project. These components are typically small and created for a specific functionality. Typically, you write the code once and then import the UI components wherever needed. For example, you can create a card component that displays certain information or have a navigation bar that will appear at the top of all web pages. Such UI elements can be imported and added to your desired web page.

API testing is a bit like putting together a puzzle. You need all the pieces to fit perfectly to see the big picture, and sometimes, you have to simulate a piece or two with mocking. Mocking in API testing lets you imitate a component or system’s behavior to test your application more efficiently. It’s like having a stunt double for your API when the real actor is unavailable. This approach can save time, reduce costs, and increase the reliability of your testing process.

Earlier this year at Snowflake Summit, we announced the public launch of the Snowflake Performance Index (SPI), an aggregate index for measuring real-world improvements in Snowflake performance experienced by customers over time. In this post, we provide our biannual update to showcase the latest improvements.

In our last post, we looked at the basics of RSpec and explored how well it works with Behavior Driven Development in Ruby. Now, we will look at specific types of RSpec tests for different parts of a Ruby on Rails application. Let's dive straight in!

For years, we've witnessed how applications have shifted to the cloud, driven by cost savings, flexibility, on-demand access, scalability, and faster deployment times. During that time, new architectural best practices for building cloud native applications have emerged. (For more insights, refer to this whitepaper.) Yet despite these advances, it remains difficult to build cloud native applications that fully take advantage of Kubernetes, the platform of choice for most cloud deployments.