-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
The Git history of changes made before publication of toCairn can be requested by sending a message to the repository owner.
- Loading branch information
0 parents
commit b9f19ce
Showing
123 changed files
with
9,558 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
# IntelliJ | ||
.idea/ | ||
*.iml | ||
|
||
# Custom scripts | ||
scripts/ignored | ||
|
||
# Maven compile output directory | ||
target/ | ||
|
||
# Custom directories holding data for/from analysis | ||
results/ | ||
data/ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,201 @@ | ||
Apache License | ||
Version 2.0, January 2004 | ||
http://www.apache.org/licenses/ | ||
|
||
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION | ||
|
||
1. Definitions. | ||
|
||
"License" shall mean the terms and conditions for use, reproduction, | ||
and distribution as defined by Sections 1 through 9 of this document. | ||
|
||
"Licensor" shall mean the copyright owner or entity authorized by | ||
the copyright owner that is granting the License. | ||
|
||
"Legal Entity" shall mean the union of the acting entity and all | ||
other entities that control, are controlled by, or are under common | ||
control with that entity. For the purposes of this definition, | ||
"control" means (i) the power, direct or indirect, to cause the | ||
direction or management of such entity, whether by contract or | ||
otherwise, or (ii) ownership of fifty percent (50%) or more of the | ||
outstanding shares, or (iii) beneficial ownership of such entity. | ||
|
||
"You" (or "Your") shall mean an individual or Legal Entity | ||
exercising permissions granted by this License. | ||
|
||
"Source" form shall mean the preferred form for making modifications, | ||
including but not limited to software source code, documentation | ||
source, and configuration files. | ||
|
||
"Object" form shall mean any form resulting from mechanical | ||
transformation or translation of a Source form, including but | ||
not limited to compiled object code, generated documentation, | ||
and conversions to other media types. | ||
|
||
"Work" shall mean the work of authorship, whether in Source or | ||
Object form, made available under the License, as indicated by a | ||
copyright notice that is included in or attached to the work | ||
(an example is provided in the Appendix below). | ||
|
||
"Derivative Works" shall mean any work, whether in Source or Object | ||
form, that is based on (or derived from) the Work and for which the | ||
editorial revisions, annotations, elaborations, or other modifications | ||
represent, as a whole, an original work of authorship. For the purposes | ||
of this License, Derivative Works shall not include works that remain | ||
separable from, or merely link (or bind by name) to the interfaces of, | ||
the Work and Derivative Works thereof. | ||
|
||
"Contribution" shall mean any work of authorship, including | ||
the original version of the Work and any modifications or additions | ||
to that Work or Derivative Works thereof, that is intentionally | ||
submitted to Licensor for inclusion in the Work by the copyright owner | ||
or by an individual or Legal Entity authorized to submit on behalf of | ||
the copyright owner. For the purposes of this definition, "submitted" | ||
means any form of electronic, verbal, or written communication sent | ||
to the Licensor or its representatives, including but not limited to | ||
communication on electronic mailing lists, source code control systems, | ||
and issue tracking systems that are managed by, or on behalf of, the | ||
Licensor for the purpose of discussing and improving the Work, but | ||
excluding communication that is conspicuously marked or otherwise | ||
designated in writing by the copyright owner as "Not a Contribution." | ||
|
||
"Contributor" shall mean Licensor and any individual or Legal Entity | ||
on behalf of whom a Contribution has been received by Licensor and | ||
subsequently incorporated within the Work. | ||
|
||
2. Grant of Copyright License. Subject to the terms and conditions of | ||
this License, each Contributor hereby grants to You a perpetual, | ||
worldwide, non-exclusive, no-charge, royalty-free, irrevocable | ||
copyright license to reproduce, prepare Derivative Works of, | ||
publicly display, publicly perform, sublicense, and distribute the | ||
Work and such Derivative Works in Source or Object form. | ||
|
||
3. Grant of Patent License. Subject to the terms and conditions of | ||
this License, each Contributor hereby grants to You a perpetual, | ||
worldwide, non-exclusive, no-charge, royalty-free, irrevocable | ||
(except as stated in this section) patent license to make, have made, | ||
use, offer to sell, sell, import, and otherwise transfer the Work, | ||
where such license applies only to those patent claims licensable | ||
by such Contributor that are necessarily infringed by their | ||
Contribution(s) alone or by combination of their Contribution(s) | ||
with the Work to which such Contribution(s) was submitted. If You | ||
institute patent litigation against any entity (including a | ||
cross-claim or counterclaim in a lawsuit) alleging that the Work | ||
or a Contribution incorporated within the Work constitutes direct | ||
or contributory patent infringement, then any patent licenses | ||
granted to You under this License for that Work shall terminate | ||
as of the date such litigation is filed. | ||
|
||
4. Redistribution. You may reproduce and distribute copies of the | ||
Work or Derivative Works thereof in any medium, with or without | ||
modifications, and in Source or Object form, provided that You | ||
meet the following conditions: | ||
|
||
(a) You must give any other recipients of the Work or | ||
Derivative Works a copy of this License; and | ||
|
||
(b) You must cause any modified files to carry prominent notices | ||
stating that You changed the files; and | ||
|
||
(c) You must retain, in the Source form of any Derivative Works | ||
that You distribute, all copyright, patent, trademark, and | ||
attribution notices from the Source form of the Work, | ||
excluding those notices that do not pertain to any part of | ||
the Derivative Works; and | ||
|
||
(d) If the Work includes a "NOTICE" text file as part of its | ||
distribution, then any Derivative Works that You distribute must | ||
include a readable copy of the attribution notices contained | ||
within such NOTICE file, excluding those notices that do not | ||
pertain to any part of the Derivative Works, in at least one | ||
of the following places: within a NOTICE text file distributed | ||
as part of the Derivative Works; within the Source form or | ||
documentation, if provided along with the Derivative Works; or, | ||
within a display generated by the Derivative Works, if and | ||
wherever such third-party notices normally appear. The contents | ||
of the NOTICE file are for informational purposes only and | ||
do not modify the License. You may add Your own attribution | ||
notices within Derivative Works that You distribute, alongside | ||
or as an addendum to the NOTICE text from the Work, provided | ||
that such additional attribution notices cannot be construed | ||
as modifying the License. | ||
|
||
You may add Your own copyright statement to Your modifications and | ||
may provide additional or different license terms and conditions | ||
for use, reproduction, or distribution of Your modifications, or | ||
for any such Derivative Works as a whole, provided Your use, | ||
reproduction, and distribution of the Work otherwise complies with | ||
the conditions stated in this License. | ||
|
||
5. Submission of Contributions. Unless You explicitly state otherwise, | ||
any Contribution intentionally submitted for inclusion in the Work | ||
by You to the Licensor shall be under the terms and conditions of | ||
this License, without any additional terms or conditions. | ||
Notwithstanding the above, nothing herein shall supersede or modify | ||
the terms of any separate license agreement you may have executed | ||
with Licensor regarding such Contributions. | ||
|
||
6. Trademarks. This License does not grant permission to use the trade | ||
names, trademarks, service marks, or product names of the Licensor, | ||
except as required for reasonable and customary use in describing the | ||
origin of the Work and reproducing the content of the NOTICE file. | ||
|
||
7. Disclaimer of Warranty. Unless required by applicable law or | ||
agreed to in writing, Licensor provides the Work (and each | ||
Contributor provides its Contributions) on an "AS IS" BASIS, | ||
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or | ||
implied, including, without limitation, any warranties or conditions | ||
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A | ||
PARTICULAR PURPOSE. You are solely responsible for determining the | ||
appropriateness of using or redistributing the Work and assume any | ||
risks associated with Your exercise of permissions under this License. | ||
|
||
8. Limitation of Liability. In no event and under no legal theory, | ||
whether in tort (including negligence), contract, or otherwise, | ||
unless required by applicable law (such as deliberate and grossly | ||
negligent acts) or agreed to in writing, shall any Contributor be | ||
liable to You for damages, including any direct, indirect, special, | ||
incidental, or consequential damages of any character arising as a | ||
result of this License or out of the use or inability to use the | ||
Work (including but not limited to damages for loss of goodwill, | ||
work stoppage, computer failure or malfunction, or any and all | ||
other commercial damages or losses), even if such Contributor | ||
has been advised of the possibility of such damages. | ||
|
||
9. Accepting Warranty or Additional Liability. While redistributing | ||
the Work or Derivative Works thereof, You may choose to offer, | ||
and charge a fee for, acceptance of support, warranty, indemnity, | ||
or other liability obligations and/or rights consistent with this | ||
License. However, in accepting such obligations, You may act only | ||
on Your own behalf and on Your sole responsibility, not on behalf | ||
of any other Contributor, and only if You agree to indemnify, | ||
defend, and hold each Contributor harmless for any liability | ||
incurred by, or claims asserted against, such Contributor by reason | ||
of your accepting any such warranty or additional liability. | ||
|
||
END OF TERMS AND CONDITIONS | ||
|
||
APPENDIX: How to apply the Apache License to your work. | ||
|
||
To apply the Apache License to your work, attach the following | ||
boilerplate notice, with the fields enclosed by brackets "[]" | ||
replaced with your own identifying information. (Don't include | ||
the brackets!) The text should be enclosed in the appropriate | ||
comment syntax for the file format. We also recommend that a | ||
file or class name and description of purpose be included on the | ||
same "printed page" as the copyright notice for easier | ||
identification within third-party archives. | ||
|
||
Copyright 2021 Pieter Dirk Soels | ||
|
||
Licensed under the Apache License, Version 2.0 (the "License"); | ||
you may not use this file except in compliance with the License. | ||
You may obtain a copy of the License at | ||
|
||
http://www.apache.org/licenses/LICENSE-2.0 | ||
|
||
Unless required by applicable law or agreed to in writing, software | ||
distributed under the License is distributed on an "AS IS" BASIS, | ||
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
See the License for the specific language governing permissions and | ||
limitations under the License. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,99 @@ | ||
# toCairn | ||
|
||
Proof of Concept for the thesis 'Identifying microservice boundaries in a monolithic application based on data | ||
autonomy'. toCairn can cluster the classes based on multiple metrics. The metrics used determine the input required. | ||
Multiple clustering algorithms can be used to identify the microservice boundaries. These algorithms include an | ||
agglomerative hierarchical clustering algorithm as well as multiple multi-objective evolutionary clustering algorithms | ||
(MOEA). As this is a Proof of Concept, please consider it for evaluation but not for production purposes. | ||
|
||
This thesis project was conducted at the University of Amsterdam by Pieter Dirk Soels. | ||
|
||
## Features | ||
|
||
- Creates a dependency graph of your application. | ||
- Identifies frequency of class interaction based on static source code analysis. | ||
- Identifies frequency of class interaction based on a custom JaCoCo coverage report. | ||
- Identifies size of a class based on JFR memory allocation analysis. | ||
- Identify microservices based on multiple established metrics formed from microservice characteristics. | ||
- Perform clustering using an agglomerative hierarchical clustering algorithm with provided weights for the metrics. | ||
- Perform clustering using MOEA to generate a non-dominated solution space optimizing these multiple objectives. | ||
|
||
## Running the project locally | ||
|
||
Currently, the project is only built to be running locally. The project requires input files to be present on an | ||
available filesystem path. | ||
|
||
To run the project locally, you must have an instance of Neo4j running, the graph database that this project uses. For | ||
convenience, a `docker-compose.yml` definition is provided in the project root to run an instance already configured to | ||
run with this project. When you have `docker-compose` installed on your machine, you can boot up the Neo4j instance | ||
using `docker-compose up -d`. If you run your own instance, please configure the server application to use your own | ||
configured Neo4j instance through application properties (see `application.yml`). | ||
|
||
To run the server, start the Spring server defined in `ThesisApplication.java`. This will start the server upon which it | ||
will be accessible at `localhost:8080`. | ||
|
||
## Prerequisites | ||
|
||
For this application to work, you need to compile this project. For this, one needs to have Java JDK 11 and Maven 3.8+ | ||
installed. Furthermore, one needs to have a Neo4J database. One can set one up themselves manually or use our convenient | ||
`docker-compose.yaml` script to set one up with defaults matching the application. Storage is persisted in a Docker | ||
volume in this set up. For the latter, one needs to have both `docker` and `docker-compose` installed on their system. | ||
|
||
Lastly, a convenience would be the use of Postman to communicate with our API. In the root of this repository, there is | ||
a collection file (`toCairn.postman_collection.json`) that you can import to start using the application straight away. | ||
|
||
## Usage | ||
|
||
This PoC does not come with a frontend. Instead, we use manual API requests to store and retrieve data as well as to | ||
perform actions. On top of that, we use the visualisations from Neo4J to inspect our created graph and its configuration | ||
manually. | ||
|
||
Make sure you have a Neo4J database running either through the aforementioned manual set up or through running | ||
`docker-compose up -d` in the root of this repository. Then, run `ToCairnApplication` to start the application. | ||
|
||
You can then interact with the application on `http://localhost:8080` and interact with the database on | ||
`localhost:7474`. | ||
|
||
## FAQ | ||
|
||
These are common questions and problems encountered and how to solve them. | ||
|
||
### Neo4j missing annotations | ||
|
||
When receiving an error message containing `Missing @TargetNode declaration in class` | ||
or `missing a property for the generated, internal ID (@Id @GeneratedValue Long id)`, it could be that the project did | ||
not compile correctly. Try to run it again or run `mvn clean compile` to recompile the project, and the problem should | ||
be gone. This happens when initializing the Spring context both during running the application and during tests. | ||
|
||
### Persistence queries seem to take very long | ||
|
||
Due to how Spring Data Neo4J (SDN) is implemented it could be that, when persisting certain resources, a lot of queries | ||
need to be executed. SDN tries to make sure that the graph database exactly matches the Java model. As most of our | ||
resources are linked, this means that it will try to verify the whole graph every time you persist a resource. We tried | ||
to mitigate this as much as possible with custom queries for persisting relationships as well as using projections for | ||
storing and retrieving data. | ||
|
||
However, it could be the case on a different model that it keeps getting stuck when persisting entities. To debug such | ||
case for yourself, run the application with the `-Dlogging.level.org.springframework.data.neo4j=DEBUG` environment | ||
variable set. This will log all the queries made to Neo4J in the console. | ||
|
||
### Missing expected relationships | ||
|
||
As the relationships between classes is determined using static code analysis, there are various reasons why certain | ||
expected relationships are not present in the constructed graph. Most understandably at first, relationships based on | ||
reflection that are only present during runtime are not possible (at least to a certain point) using static analysis. | ||
The same goes for polymorphism. We can hardly deduce from static analysis whether a class is a certain subtype and | ||
therefore we do not see such relationships. | ||
|
||
Lastly, from static code analysis, we often only know the name of a class. However, to accurately match that class, we | ||
need its fully qualified name. For that, we use JavaParser's symbol solver. From traffic on discussion fora, it seems | ||
that this is still the most used AST parser and way to deduce this in meta-programming. However, this symbol solver is | ||
(at the time of writing) unmaintained. Therefore, some AST could not be resolved due to, for example, new Java | ||
constructs that the solver does not yet support (such as Java 10's `var`). Lastly, not providing dependency `.jar` files | ||
greatly lowers the ability to solve class FQNs as often a type must be deduced from library usage (e.g. deserialization) | ||
. To see such problems, you can enable debug logging through the environment property `logging=debug` which will print | ||
them to the console. | ||
|
||
## License | ||
|
||
This project is licensed under the [Apache 2.0 license](LICENSE.txt). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
version: "3.6" | ||
|
||
# Development environment set up for this application | ||
services: | ||
# Neo4j graph database for storing input and result data | ||
neo4j: | ||
image: neo4j:4.3.0 | ||
ports: | ||
- 7687:7687 | ||
- 7474:7474 | ||
volumes: | ||
- neo4j:/conf | ||
- neo4j:/data | ||
- neo4j:/import | ||
- neo4j:/logs | ||
- neo4j:/plugins | ||
environment: | ||
# Start with a default database | ||
- NEO4J_dbms_default__database=tocairn | ||
# Raise memory limits | ||
- NEO4J_dbms_memory_pagecache_size=1G | ||
- NEO4J_dbms_memory_heap_initial__size=1G | ||
- NEO4J_dbms_memory_heap_max__size=1G | ||
# DO NOT copy paste these auth variables for a production environment | ||
- NEO4J_AUTH=neo4j/password | ||
# Allow for DB upgrades | ||
- NEO4J_dbms_allow__upgrade=true | ||
|
||
# Store data of databases between restarts in Docker volume | ||
volumes: | ||
neo4j: |
Oops, something went wrong.