Abstract: A vehicle data streaming service may receive requests to register plug-ins to generate synthetic vehicle attribute data streams. A plug-in service of the vehicle data streaming service may configure a given plug-in in an internal containerized environment in a fully automated manner and/or configure the plug-in in an external compute service environment. The vehicle data streaming service may configure the plug-ins to receive input streams to generate synthetic attribute output streams. The vehicle data streaming service and the plug-in service may allow the synthetic attribute output streams to be associated with synthetic vehicle attributes included, or to be included, in a curated catalog of vehicle attributes. The vehicle data streaming service furthermore allows one or more vehicle data stream destinations to subscribe to the synthetic vehicle attributes included in the catalog.

Abstract: Systems and methods are disclosed for implementing a vehicle shadow service configured to construct and maintain up-to-date vehicle shadows using asynchronously received disaggregated vehicle data. For example, different sensors of a vehicle may provide sensor data into a data stream at different times in a disaggregated manner. A vehicle shadow may be constructed using partial sensor data from a sub-set of sensors of the vehicle, and may be updated or augmented using asynchronously received sensor data from other sensors of the vehicle.

Abstract: A vehicle data streaming service provides a curated catalog of vehicle attributes and allows a vehicle data stream source to register to the vehicle data streaming system and associate its data stream to a vehicle attribute of the attribute catalog. The vehicle data streaming service also allows vehicle data stream destinations to subscribe to the vehicle attribute in the vehicle catalog, receives streamed vehicle data from the data stream source, and sends streamed vehicle data conforming to registration requirements to the data stream destinations. Additionally, the vehicle data streaming service may allow management of the vehicle attribute catalog and may further manage the registration one or more sources and the subscriptions of one or more destinations.

Abstract: Techniques are described for providing an access control list (ACL) assisted process for filtering the analysis and display of dependency relationships among software application components (e.g., packages, files, classes, etc.), e.g., as part of modernization processes aimed at decomposing monolithic applications, identifying anti-patterns, or otherwise analyzing such applications. A software modernization service of a cloud provider network provides discovery agents and other tools that are capable of creating an inventory of users' software applications and collecting application artifacts (e.g., source code or bytecode files) associated with the software applications in users' computing environments. Various techniques are described for using ACLs containing entries enabling or disabling the analysis or display of various application components to customize various modernization processes and results displays.

Abstract: Systems and methods are disclosed for implementing perspective-based vehicle shadows. A user of a vehicle shadow service can specify different vehicle shadows for a given vehicle, wherein the different vehicle shadows comprise at least partially different sets of sensor data received from the vehicle and represent the vehicle from different perspectives. For example, a first vehicle shadow may represent the vehicle from the perspective of a first vehicle system, such as the tires, and another vehicle shadow may represent the same vehicle from the perspective of a second vehicle system, such as the engine. Streaming data is provided to the vehicle shadow service and is mapped to the respective perspective-based vehicle shadows, based on user defined configurations for the respective perspective-based vehicle shadows.

Abstract: A vehicle data management system and data jurisdiction system manage vehicle data between multiple jurisdictions and enables a set of jurisdiction rules involving rules of various jurisdictions to be applied consistently. The vehicle data jurisdiction system can detect changes in jurisdiction of a vehicle based on various pieces of received vehicle information and applies appropriate jurisdiction rules from a set of jurisdiction rules. Various jurisdictions may have conflicting jurisdiction rules and, in such circumstances, the data jurisdiction system resolves potential conflicts between the rules using a jurisdiction rules resolution workflow. Based on the resolution of the conflict, the data jurisdiction system can migrate data of the vehicle to one or more other jurisdictions, or otherwise implement the correct rules determined by resolving the conflict.

Abstract: Systems and methods are disclosed for implementing a vehicle shadow service that includes a vehicle and/or vehicle shadow update mechanism. A vehicle shadow management sub-system of the vehicle shadow service includes or interfaces with an interface configured to receive vehicle state change requests. Received requests are stored in an update queue for a vehicle shadow and a validation processor determines whether the received state change requests are valid before sending a given state change request to a vehicle corresponding to the vehicle shadow. In some embodiments, state change requests may be invalidated due to being rendered moot by subsequently received requests, changes in state of the vehicle, expiration, etc. The corresponding vehicle shadow is then updated when a data stream from the vehicle indicates that the requested state change has in fact been implemented at the vehicle.

Abstract: Techniques are described for automatically identifying monolithic software applications in users' computing environments for software modernization purposes. A monolithic patent application typically refers to a single-tiered application with self-contained functionality designed largely without modularity, although many types of applications can have monolithic characteristics. In many cases, modularity in a software application's design is desirable and thus developers may often seek to decompose monolithic applications into more modular “microservices” or other subunits when possible. A software modernization system includes a software analysis service that obtains, for one or more software applications undergoing evaluation, a collection of application artifacts, application profiling metrics, and other application profile data.

Abstract: Disclosed are various embodiments for anti-pattern detection in extraction and deployment of a microservice. A software modernization service is executed to analyze a computing application to identify various applications. When one or more of the application components are specified to be extracted as an independently deployable subunit, anti-patterns associated with deployment of the independently deployable subunit are determined prior to extraction. Anti-patterns may include increases in execution time, bandwidth, network latency, central processing unit (CPU) usage, and memory usage among other anti-patterns. The independently deployable subunit is selectively deployed separate from the computing application based on the identified anti-patterns.

Abstract: Disclosed are various embodiments for isolated code detection from application code analysis. Various application components may be identified from a source code file or a bytecode file of a computing application. A graph model representative of the computing application is generated having nodes and bridges that connect some nodes to other nodes. The graph model is generated such that at least one of the nodes is an isolated node having less than a threshold number of bridges connecting to other nodes, which is indicative that a corresponding one of the application components can be implemented as an independently deployable component of the computing application.

Abstract: Disclosed are various embodiments for the extraction of isolated nodes during source code refactoring. A graph model representative of a computing application is generated having nodes and bridges that connect some nodes to other nodes. An application component corresponding to a selected one of the nodes may be extracted from the computing application. An independently deployable component of the computing application may be generated and deployed on a network service such that the independently deployable component is accessible through a network-based call.

Abstract: Disclosed are various embodiments for the refactoring of local calls to network calls during software modernization. First and second application components are identified based on analysis of a computing application. A local call from the first application component to a process of the second application component is identified, and an independently deployable microservice is created from the computing application. The independently deployable subunit comprises the second application component having a network endpoint. The independently deployable microservice is deployed such that the process is accessible to the first application component via the network endpoint. The local call is programmatically refactored into a network call from the first application component to the process of the second application component.

Abstract: Techniques are described for using graph partitioning techniques to identify refactoring candidates to decompose monolithic software applications as part of software modernization processes. An application modernization system constructs a graph model of a software application based on an analysis of application artifacts associated with the software application. The graph model includes nodes each representing an independent application component and further includes edges representing identified dependency relationships among the application components. An application modernization system further generates application profile metrics associated with the identified dependencies, and weights derived from such metrics are applied to the edges of the graph model. Once a weighted graph model is obtained, a graph partitioning algorithm is applied to identify a plurality of subgraphs each representing a candidate subunit of the application for refactoring.

Abstract: Disclosed are various embodiments for domain-driven application breakout. Application components are identified based on analysis of a computing application, where the application components are different portions of the computing application. Individual ones of the application components are associated with a category, where the category may include a business domain category. One or more of the application components associated with the category are extracted as an independently deployable subunit, which may include a microservice. The independently deployable subunit is generated for the category using the at least one of the application components and deployed separate from the computing application. A local call in the computing application to the extracted application components is refactored to a network call to the independently deployable subunit.