LocalStack today announced it has extended its ability to simulate Amazon Web Services (AWS) environments to provide an ability to debug applications before deploying them.
Colin Neagle, head of marketing for LocalStack, said App Inspector makes it possible for developers to debug their applications running in a simulated AWS environment inside a container on a local server.
Simulating the full application stack within a local sandbox container makes it possible to better understand application behavior such as data flows between AWS services, event execution paths and resource dependencies that may have been inadvertently misconfigured, noted Neagle.
Once discovered, App Inspector then generates a visual representation of the interaction between services in the local environment to make it simpler to debug applications without digging through logs and then needing to upload a fix to a staging server running in the AWS cloud.
That capability doesn’t replace the need for an observability platform but it does reduce the overall amount of friction software engineering teams are likely to encounter as they build applications on a laptop or local server, said Neagle.
In general, application developers still prefer to build software on a local machine that they have more control over. LocalStack was created to provide a local instance of an AWS environment that enables developers to build software that is destined to run in a cloud environment. The goal is to reduce the number of instances where code that runs on a local machine doesn’t actually run as intended in the cloud.
At present, LocalStack supports AWS, but the company is also building a set of emulation services for Microsoft Azure that will be made available later this year.
It’s not clear how much code is developed first on a notebook, desktop PC or local server, but in the age of artificial intelligence (AI) the amount of code being generated by individual developers is increasing exponentially. Every time code has to be sent back for revision, it slows the overall pace of application development. DevOps and platform engineering teams will need to streamline workflows in a way that ultimately improves productivity.
The speed at which DevOps teams make that adjustment will naturally vary from one team to another, but the sooner everyone realizes that a piece of AI-generated code might not run as intended in a cloud computing environment the less stress there is likely to be for all concerned. The challenge and the opportunity, of course, is identifying those points of friction before the amount of code being created might soon become too overwhelming to effectively deploy and manage.
Ultimately, DevOps teams need to meet application developers where they proverbially are rather than forcing them all to develop applications in the cloud. The simple truth is many developers, if inclined, will simply evade any cloud mandate using shadow IT resources. The better part of valor then is to enable application developers to build applications on the platforms they prefer in ways that can still be centrally managed by a DevOps team.