Software Engineering
Explore questions in the Software Engineering category that you can ask Spark.E!
- Input the same data for 2 times by different ppl
- Input the same data for 2 times by the same person
- A paradigm in which application images are never modified after they're deployed.
- A testing method to assure code is resistant to casual or malicious changes that have unforeseen impacts on the application.
- Which is not a characteristic of Cloud Native?
- automated processes used to build, test, and merge application code changes using source code control systems with integrated change management.
- bringing Dev and Ops teams together to increase application operability and end-to-end agility.
- Which is not a use case for developing Cloud Native applications?
- the seamless scaling of applications across cloud boundaries to meet consumer demands.
- when functional and unit tests are written first for a new feature or change and then the actual code is written to pass it.
- scripts and declarative configurations that describe the infrastructure resources the application needs including servers, operating systems, storage, and network connections.
- Which application modernization path leverages cloud-native Containers and Container technologies?
- When building applications as a Container you start with what artifact?
- What is not a consideration when adopting a Cloud Native approach for software development?
- Framework within which people can address complex adaptive problems, while productively and creatively delivering products, including software, of the highest possible value.
- Migration Toolkits available that can help analyze and accelerate migration for many workloads moving to Containers
- What is the name for the process used to migrate applications to cloud using virtualization technologies?
- automated processes used to package and release application code.
- Container image that contains read-only layers where the OS is the lowest layer. Application code and dependencies are "written" into a layer on-top of this layer using simple commands that can be captured in a manifest.
- when two developers work together and take turns where one developer writes the code and the other one observes and warns of potential bugs or errors.