architecture
|
Architecting Your Test Automation PlatformWith all the pressure to “just automate,” we may not invest enough in architecting our test automation. You wouldn't remodel a house without doing some planning and design; our test automation journey should be treated no differently. A comprehensive architecture plan is crucial for increasing test automation coverage. | 
|
|
What’s Different about Testing Serverless Applications?Serverless computing is a DevOps technique that uses cloud-provided runtimes to execute code components in a defined workflow. Testing is easier in some ways with this model, but more difficult in others. Let's dive into the ways testing serverless applications and components is different from traditional architecture. | 
|
|
Continuous Security in Agile Development"Continuous" gets mentioned a lot in agile and DevOps, but one area that often doesn’t get enough attention is how to continuously build, test, and deliver secure applications. Just like for quality, you can’t test security in, so you need to have a plan for how to build it in. Here are some tips on how to do that. | 
|
|
Performance Testing for Our Modern, DevOps WorldAs DevOps-based methodologies are more broadly adopted, we'll increasingly move to a continuous testing model. Containerized environments and microservices make it easier to optimize your application by validating changes to the environment or system configuration, allowing you to deliver better products faster. | 
|
|
Ensure That Your Current Cloud Solution Will Stand the Test of TimeIt’s still early in the lifecycle of cloud adoption. This means certain cloud vendors and technologies will fall by the wayside as adoption takes on critical mass. How, then, do you future-proof your cloud solution to make sure you don’t make a decision that you’ll regret later? Here are three ideas to consider. | 
|
|
Engineering Architecture Systems for a Faster BuildIn the era of continuous integration and continuous deployment, big applications are creating bloated build pipelines. The problem is when code becomes so entangled that every change impacts large portions of the system, meaning there’s a lot to rebuild. If you reshape the code architecture, you can reduce build times. | 
|
|
How Agile, DevOps, and Continuous Integration Changed Software Architecture For the longest time, software architecture was something you built, adapted to your team or situation, and left in place—the old “if it ain’t broke, don’t fix it” mentality. Now, more rapid changes aren’t just expected, they’re necessary. |
|
|
Investigating Interface Architecture in Legacy SystemsProgrammers working with legacy systems often seek to understand how the program is designed, but that's not enough. When trying to understand legacy systems, special care must be taken to also explore, identify, and take inventory of interfaces, which can be integral to the entire system architecture. | 
|