Systems | Development | Analytics | API | Testing

Organizations face many challenges every day, and every day new challenges emerge. You have the day-to-day obstacles to overcome and then there is new twist. Today, the biggest challenge emerging on the market is how to adopt and implement effective API and service management habits. The number of APIs and services a company uses is growing exponentially every day, managing them individually or with a corporate wiki is just not possible.

In our previous blog posts covering our in-house Security Orchestration, Automation & Response (SOAR) application, we described the basic building blocks for the system and the steps we took to orchestrate interactions between a number of security tools. While building orchestration, we already introduced a significant amount of Automation powering features like threat intelligence collection and event polling.

In the previous article, we walked through an example of how to query and retrieve data from a MySQL database using the native MySQL C API and then compared that to the clean simplicity of using the SourcePro DB API. In this article, we are going to take that a step further and look at input parameter binding. Building off the system we discussed previously that manages the accounts for a credit card system, we are now going to implement a simple application that can add transactions to an account.

You might think that each marketer uniquely implements their landing page. However, there is a formula for landing page optimization, and following best practices will get you a healthy conversion rate. Even if you want a one-of-a-kind landing page, using tried-and-true principles will improve your results.

We recently talked to Angie Jones in a podcast episode dedicated to best practices in software testing. In this article, drawing on our previous discussion, we’ll share her thoughts about the main factors to consider to build a comprehensive test automation strategy.

The NoSuchFieldError is an error in Java that occurs when a specified field does not exist. It is thrown when an application attempts to access or modify a field of an object or a static field of a class but the object or class no longer contains that field. The NoSuchFieldError only occurs during runtime if the definition of a class has changed incompatibly. Since it is thrown at runtime, it does not need to be declared in the throws clause of a method or constructor.

Interested in taking your product to the next stage of growth but have missing metrics? We understand that as a startup, companies are laser focused on getting their product out the door. Founding teams today don’t want to (or need to) create their own user management, billing, or other analytics tools. By forging partnerships with best-in-breed providers, startups can take advantage of these analytical tools without wasting engineering manpower to create in-house toolkits.

A lot of teams are starting to look for version control for binary files. As more teams adopt game engine technology, they produce more art assets, builds, and other files that they need to store and track. A lot of version control tools simply don’t do a good job with versioning or storing large binary files, like game engine files. Managing these files efficiently becomes a serious issue the more a team and their projects grow. You need the right version control for large binary files.