# Elastic Objects >... while you're programming, you are learning. It's often the case that it can take a year of programming on a project before you understand what the best design approach should have been ... > > -- Martin Fowler Computer communication today means some kind of typed method invocation and fixed method functionality bound to an url. The concept of Elastic Objects is different: It offers a generic object with typed parts send over one endpoint. Functionality is offered by beans with an execution method which can be arbitrary composed. They called **Calls**. Some working editable examples of diffent you can find on [ElasticObjects.org](http://www.elasticobjects.org/examples/ExamplesStart.html) which itself is build by one generic spring boot endpoint and EO. A simple example where you can edit it's structure: ```
``` Here you can edit * the value of source * the fieldName of target * the value of sourcePath and the corresponding fieldName The core library is rather small but allows a much rich message communication even within existing solutions. * any combination of functionality allowed in a message * any arbitrary information could placed in a message * minimal coupling to an application server * No annotation magic, pure java ### Links * http://alteseite.schiffshistorisches-archiv.de/uploads/media/Deckschrubben.pdf * https://www.heise.de/developer/artikel/Low-Code-Low-Quality-4134288.html * https://de.wikipedia.org/wiki/Modellgetriebene_Softwareentwicklung * https://levelup.gitconnected.com/how-to-use-technical-debt-in-your-favor-98bae475ba68 * https://commons.wikimedia.org/w/index.php?search=Eisen+herstellung&title=Special%3ASearch&go=Go#/media/File:Fotothek_df_tg_0000590_Metallurgie_%5E_Probierkunst_%5E_Silber_%5E_Erz_%5E_Brennofen_%5E_Test_%5E_Blasebalg.jpg ---- [fluentcodes](http://fluentcodes.com) - [elastic objects](http://elasticobjects.com) - [mvn repository](https://mvnrepository.com/artifact/org.fluentcodes.projects.elasticobjects)