An Experimental Study of the Performance, Energy, and Programming Effort Trade-Offs of Android Persistence Frameworks

Total Page:16

File Type:pdf, Size:1020Kb

An Experimental Study of the Performance, Energy, and Programming Effort Trade-Offs of Android Persistence Frameworks An Experimental Study of the Performance, Energy, and Programming Effort Trade-offs of Android Persistence Frameworks Jing Pu Thesis submitted to the Faculty of the Virginia Polytechnic Institute and State University in partial fulfillment of the requirements for the degree of Master of Science in Computer Science and Applications Eli Tilevich, Chair Barbara G. Ryder Francisco Servant July 1, 2016 Blacksburg, Virginia Keywords: Energy Efficiency; Performance; Programming Effort; Orthogonal Persistence; Android; Copyright 2016, Jing Pu An Experimental Study of the Performance, Energy, and Programming Effort Trade-offs of Android Persistence Frameworks Jing Pu (ABSTRACT) One of the fundamental building blocks of a mobile application is the ability to persist program data between different invocations. Referred to as persistence, this functionality is commonly implemented by means of persistence frameworks. When choosing a particular framework, Android|the most popular mobile platform—offers a wide variety of options to developers. Unfortunately, the energy, performance, and programming effort trade-offs of these frameworks are poorly understood, leaving the Android developer in the dark trying to select the most appropriate option for their applications. To address this problem, this thesis reports on the results of the first systematic study of six Android persistence frameworks (i.e., ActiveAndroid, greenDAO, Orm- Lite, Sugar ORM, Android SQLite, and Realm Java) in their application to and performance with popular benchmarks, such as DaCapo. Having measured and ana- lyzed the energy, performance, and programming effort trade-offs for each framework, we present a set of practical guidelines for the developer to choose between Android persistence frameworks. Our findings can also help the framework developers to optimize their products to meet the desired design objectives. This thesis is based on research accepted for publication in the proceedings of the IEEE Modeling, Analysis, and Simulation of Computer and Telecommunication Sys- tems Conference (MASCOTS 2016). This research is supported by the National Science Foundation through the Grant CCF-1116565. Dedication To My Family For Their Love And Support iii Acknowledgments I would like to thank all of those who have contributed to this work. In particular I am most grateful to Dr. Eli Tilevich, my supervisor, for his help and support which made this thesis possible. I am indebted to him not just for his scientific contribution but also for his motivating words, day after day, and his friendship. I would like to thank the members of my thesis committee: Drs. Barbara G. Ryder, Francisco Servant and Eli Tilevich for their scientific and emotional support. I would like to give special thanks to Zheng Song for his help and suggestion with my research project. I wish to express my sincere appreciation to Sharon Kinder-Potter in the office of Computer Science Department for her help and assistance. My thanks goes to all my colleagues in the Computer Science Department for their help and advice which made my stay at Virginia Polytechnic Institute and State University a most pleasant experience. I would like to thank Newman Library for the job position provided to me and Anne Lawrence, Amanda French, Keith Gilbertson and other colleagues there for their assistance. Finally, I would like to pay tribute to the constant support of my family, my relatives and my friends, without their love over the many years none of this would have been possible and whose sacrifice I can never repay. I want to thank my lovely mother for always being there. A very special thanks goes to my husband, Sai, for helping and encouraging me all the time. iv Contents 1 Introduction 1 1.1 Persistence, Android Programming, and Energy Efficiency . .1 1.2 Analyzing the Trade-offs of Android Persistence Frameworks . .2 1.3 Research Questions . .3 1.4 Research Findings . .3 1.5 Research Contributions . .4 1.6 Thesis Roadmap . .5 2 Terminology 6 3 Motivation 9 4 Related Work 11 4.1 Persistence Framework . 11 4.2 Performance and Energy Efficiency . 12 4.3 Programming Effort . 13 5 Android Persistence Frameworks 14 5.1 The Evolution of Persistence Frameworks . 14 5.2 Android Persistence Framework Overview . 15 v 5.3 Android Persistence Framework Feature Comparison . 16 6 Experiment Design 21 6.1 Android Persistence Framework Experiment Architecture . 21 6.2 Android Persistence Framework Selection . 22 6.3 Benchmark Selection . 23 6.4 Parameters and Dependent Variables . 24 6.4.1 Performance . 25 6.4.2 Energy . 25 6.4.3 Programming Effort . 26 6.4.4 Benchmark Input Parameters . 26 6.5 Experimental Hardware and Tools . 26 7 Study Results 30 7.1 Programming Effort Analysis . 30 7.1.1 Uncommented Lines of Code Analysis . 30 7.1.2 McCabe Cyclomatic Complexity Analysis . 31 7.1.3 Overall Programming Effort Analysis . 33 7.2 Experiments with the Android ORM Benchmark . 34 7.2.1 Initialization Analysis . 34 7.2.2 Insert Analysis . 36 7.2.3 Update Analysis . 38 7.2.4 Select and Delete Analysis . 40 7.2.5 Overall Analysis . 44 7.3 Experiments with the DaCapo benchmark . 45 8 Recommendation Model 52 vi 8.1 Recommendation Model . 52 8.1.1 Design of PEP Model . 52 8.1.2 Benchmark Evaluation . 54 9 Threats to Validity 56 9.1 External Threats . 56 9.2 Internal Threats . 56 10 Future Work 58 10.1 Expanding Platform and Case Study . 58 10.2 Understanding the Concurrency Behavior of Android Persistence Frame- work.................................... 59 10.3 Designing Energy Efficient Persistence Frameworks . 59 10.4 Expanding the Study of Android Middleware . 60 11 Conclusions 61 Bibliography 61 A Persistence Framework Libraries 70 B Initialization Core Code 71 C Insert Core Code 74 D Update Core Code 79 E Select Core Code 88 F Delete Core Code 94 vii List of Figures 6.1 Android Persistence Framework Experiment Architecture . 22 6.2 Monsoon Mobile Device Power Monitor's main channel measurement connection . 27 6.3 Monsoon Mobile Device Power Monitor's Software UI . 28 6.4 Traceview Profiling UI . 29 7.1 Comparison of initialization energy consumption among different per- sistence frameworks in Android ORM benchmark. The x axis indi- cates six Android persistence frameworks and the y axis is the energy consumption of benchmark with individual framework. 35 7.2 Comparison of initialization execution time among different persis- tence frameworks in the Android ORM Benchmark. The x axis indi- cates six Android persistence frameworks and the y axis is the execu- tion time of benchmark with individual framework. 35 7.3 Comparison of initialization read/write operations among SQLite-based Android persistence frameworks in the Android ORM Benchmark. The x axis indicates five SQLite-based Android persistence frame- works, and the y axis is the operation number of benchmark with individual framework: specially, black bar shows the read operation number and red bar shows the write operation number. the read and write number for Sugar ORM are 0. 36 viii 7.4 Comparison of insert energy consumption among different persistence frameworks in the Android ORM Benchmark. Six Android persistence frameworks are represented by different colors, the x axis indicates number of transaction, and the y axis is the energy consumption of benchmark with individual framework. 37 7.5 Comparison of insert execution time among different persistence frame- works in the Android ORM Benchmark. Six Android persistence frameworks are represented by different colors, the x axis indicates number of transaction, and the y axis is the execution time of bench- mark with individual framework. 37 7.6 Comparison of insert read/write operations among SQLite-based An- droid persistence frameworks in the Android ORM Benchmark. The x axis indicates five SQLite-based Android persistence frameworks, and the y axis is the operation number of benchmark with individ- ual framework when number of transaction = 125: specially, black bar shows the read operation number and red bar shows the write operation number. 38 7.7 Comparison of update energy consumption among different persis- tence frameworks in the Android ORM Benchmark. Six Android per- sistence frameworks are represented by different colors, the x axis indi- cates number of transaction, and the y axis is the energy consumption of benchmark with individual framework. 39 7.8 Comparison of update execution time among different persistence frame- works in the Android ORM Benchmark. Six Android persistence frameworks are represented by different colors, the x axis indicates number of transactions, and the y axis is the execution time of bench- mark with individual framework. 39 7.9 Comparison of update read/write operations among different persis- tence frameworks in the Android ORM Benchmark. The x axis in- dicates five SQLite-based Android persistence frameworks, and the y axis is the operation number of benchmark with individual framework when number of transactions = 125: specially, black bar shows the read operation number and red bar shows the write operation number. 40 ix 7.10 Comparison of select energy consumption among different persistence frameworks in the Android ORM Benchmark. Six Android persistence frameworks are represented by different colors, the x axis indicates number of transactions, and the y axis is the energy consumption of benchmark with individual framework. 41 7.11 Comparison of select execution time among different persistence frame- works in the Android ORM Benchmark. Six Android persistence frameworks are represented by different colors, the x axis indicates number of transactions, and the y axis is the execution time of bench- mark with individual framework. 41 7.12 Comparison of select read/write operations among SQLite-based An- droid persistence frameworks in the Android ORM Benchmark. The x axis indicates five SQLite-based Android persistence frameworks, and the y axis is the operation number of benchmark with individ- ual framework when number of transactions = 125: specially, black bar shows the read operation number and red bar shows the write operation number.
Recommended publications
  • Hibernate ORM Query Simplication Using Hibernate
    2016 3rd National Foundation for Science and Technology Development Conference on Information and Computer Science Hibernate ORM Query Simplication Using Hibernate Criteria Extension (HCE) Kisman Sani M. Isa Master of Information Technology Master in Computer Science Bina Nusantara University Bina Nusantara University Jl. Kebon Jeruk Raya No. 27, Jakarta Barat, DKI Jl. Kebon Jeruk Raya No. 27, Jakarta Barat, DKI Jakarta, Indonesia 11530 Jakarta, Indonesia 11530 [email protected] [email protected] Abstract— Software development time is a critical issue interfaced by a query. The software engineer will make in software development process, hibernate has been the query specified to database used. Each database widely used to increase development speed. It is used in vendor has their Structured Query Language (SQL). As database manipulation layer. This research develops a the development of software technology and most of library to simplify hibernate criteria. The library that is programming languages are object oriented, some called as Hibernate Criteria Extension (HCE) provides API functions to simplify code and easily to be used. Query engineer or software institutions try to simplify the associations can be defined by using dot. The library will query process. They try to bind object in application to automatically detect the join association(s) based on database. This approach is called as Object Relational mapping in entity class. It can also be used in restriction Mapping (ORM). ORM is a translation mechanism from and order. HCE is a hibernate wrapper library. The object to relational data, vice versa. ORM has “dialect” configuration is based on hibernate configuration.
    [Show full text]
  • JPA Avancé » Licence
    Formation « JPA Avancé » Licence Cette formation vous est fournie sous licence Creative Commons AttributionNonCommercial- NoDerivatives 4.0 International (CC BY-NC-ND 4.0) Vous êtes libres de : ● Copier, distribuer et communiquer le matériel par tous moyens et sous tous formats Selon les conditions suivantes : ● Attribution : Vous devez créditer l'Oeuvre, intégrer un lien vers la licence et indiquer si des modifications ont été effectuées à l'Oeuvre. Vous devez indiquer ces informations par tous les moyens possibles mais vous ne pouvez pas suggérer que l'Offrant vous soutient ou soutient la façon dont vous avez utilisé son Oeuvre. ● Pas d’Utilisation Commerciale: Vous n'êtes pas autoriser à faire un usage commercial de cette Oeuvre, tout ou partie du matériel la composant. ● Pas de modifications: Dans le cas où vous effectuez un remix, que vous transformez, ou créez à partir du matériel composant l'Oeuvre originale, vous n'êtes pas autorisé à distribuer ou mettre à disposition l'Oeuvre modifiée. http://creativecommons.org/licenses/by-nc-nd/4.0/deed.fr Ippon Technologies © 2014 Ippon Formation en bref Pourquoi Ippon Technologies publie ses supports de formation ? Car Ippon participe à la communauté Java et Web et soutien le modèle open-source Le support théorique représente 40% du temps de formation, l'intérêt est dans les Travaux Pratiques et l'expert Ippon qui assure le cours. Nos TP sont dispensés lors des sessions de formations que nous proposons. Ippon Technologies © 2014 Pour nous contacter Pour nous contacter et participer à nos formations : - Technique : [email protected] - Commercial : [email protected] Toutes les informations et les dates de formations sont sur notre site internet et notre blog : - http://www.ippon.fr/formation - http://blog.ippon.fr Ippon Technologies © 2014 Bienvenue ● Présentation ● Organisation ● Détails pratiques Ippon Technologies © 2014 Prérequis ● Pour suivre le cours ○ Avoir de bonnes bases en Java : les JavaBeans, les Collections, JDBC..
    [Show full text]
  • The Convergence of Modeling and Programming
    The Convergence of Modeling and Programming: Facilitating the Representation of Attributes and Associations in the Umple Model-Oriented Programming Language by Andrew Forward PhD Thesis Presented to the Faculty of Graduate and Postdoctoral Studies in partial fulfillment of the requirements for the degree Doctor of Philosophy (Computer Science1) Ottawa-Carleton Institute for Computer Science School of Information Technology and Engineering University of Ottawa Ottawa, Ontario, K1N 6N5 Canada © Andrew Forward, 2010 1 The Ph.D. program in Computer Science is a joint program with Carleton University, administered by the Ottawa Carleton Institute for Computer Science Acknowledgements A very special, and well-deserved, thank you to the following: a) Dr. Timothy C. Lethbridge. Tim has been a mentor of mine for several years, first as one of my undergraduate professors, later as my Master’s supervisor. Tim has again helped to shape my approach to software engineering, research and academics during my journey as a PhD candidate. b) The Complexity Reduction in Software Engineering (CRUISE) group and in particular Omar Badreddin and Julie Filion. Our weekly meetings, work with IBM, and the collaboration with the development of Umple were of great help. c) My family and friends. Thank you and much love Ayana; your support during this endeavor was much appreciated despite the occasional teasing about me still being in school. To my mom (and editor) Jayne, my dad Bill, my sister Allison and her husband Dennis. And, to my friends Neil, Roy, Van, Rob, Pat, and Ernesto – your help will be forever recorded in my work. Finally a special note to Ryan Lowe, a fellow Software Engineer that helped to keep my work grounded during our lengthy discussion about software development – I will miss you greatly.
    [Show full text]
  • Thesis Artificial Intelligence Method Call Argument Completion Using
    Method Call Argument Completion using Deep Neural Regression Terry van Walen [email protected] August 24, 2018, 40 pages Academic supervisors: dr. C.U. Grelck & dr. M.W. van Someren Host organisation: Info Support B.V., http://infosupport.com Host supervisor: W. Meints Universiteit van Amsterdam Faculteit der Natuurwetenschappen, Wiskunde en Informatica Master Software Engineering http://www.software-engineering-amsterdam.nl Abstract Code completion is extensively used in IDE's. While there has been extensive research into the field of code completion, we identify an unexplored gap. In this thesis we investigate the automatic rec- ommendation of a basic variable to an argument of a method call. We define the set of candidates to recommend as all visible type-compatible variables. To determine which candidate should be recom- mended, we first investigate how code prior to a method call argument can influence a completion. We then identify 45 code features and train a deep neural network to determine how these code features influence the candidate`s likelihood of being the correct argument. After sorting the candidates based on this likelihood value, we recommend the most likely candidate. We compare our approach to the state-of-the-art, a rule-based algorithm implemented in the Parc tool created by Asaduzzaman et al. [ARMS15]. The comparison shows that we outperform Parc, in the percentage of correct recommendations, in 88.7% of tested open source projects. On average our approach recommends 84.9% of arguments correctly while Parc recommends 81.3% correctly. i ii Contents Abstract i 1 Introduction 1 1.1 Previous work........................................
    [Show full text]
  • Designpatternsphp Documentation Release 1.0
    DesignPatternsPHP Documentation Release 1.0 Dominik Liebler and contributors Jul 18, 2021 Contents 1 Patterns 3 1.1 Creational................................................3 1.1.1 Abstract Factory........................................3 1.1.2 Builder.............................................8 1.1.3 Factory Method......................................... 13 1.1.4 Pool............................................... 18 1.1.5 Prototype............................................ 21 1.1.6 Simple Factory......................................... 24 1.1.7 Singleton............................................ 26 1.1.8 Static Factory.......................................... 28 1.2 Structural................................................. 30 1.2.1 Adapter / Wrapper....................................... 31 1.2.2 Bridge.............................................. 35 1.2.3 Composite............................................ 39 1.2.4 Data Mapper.......................................... 42 1.2.5 Decorator............................................ 46 1.2.6 Dependency Injection...................................... 50 1.2.7 Facade.............................................. 53 1.2.8 Fluent Interface......................................... 56 1.2.9 Flyweight............................................ 59 1.2.10 Proxy.............................................. 62 1.2.11 Registry............................................. 66 1.3 Behavioral................................................ 69 1.3.1 Chain Of Responsibilities...................................
    [Show full text]
  • A Decision Support Model for Using an Object-Relational Mapping Tool in the Data Management Component of a Software Platform
    UNIVERSITY OF UTRECHT DEPARTMENT OF INFORMATION AND COMPUTING SCIENCES A Decision Support Model for using an Object-Relational Mapping Tool in the Data Management Component of a Software Platform Rares George Sfirlogea Supervisors: dr. R.L. Jansen dr. ir. J.M.E.M. van der Werf Friday 6th February, 2015 Academic year 2014/2015 Abstract The usage of an ecosystem-based application framework gives software com- panies a competitive advantage in delivering stable, feature rich products while keeping the completion time to a minimum. It is seldom the case that a platform is selected by looking at its software architecture although it can reveal a lot of details about its limitations and functionality. The Object- Relational Mapping (ORM) tool in the data management component imposes extendability restrictions on the software platform. The software architect or developer that is responsible of making this decision is often unaware of the platform traits leading to breaking the general conventions or even consider- ing a costly rewrite of the entire application in the future. The aim of this research thesis is to create a decision support model regarding the inclusion of an ORM tool in the platform architecture and the consequences it imposes on the software platform's quality attributes. With this artefact, any individ- ual in charge with the product architecture can make a more knowledgeable decision, by aligning the platform capabilities with his data requirements. Acknowledgements I would like to express my sincere appreciation for all the people who helped this research reach its final state. With a special mention going to my thesis coordinators, the experts who agreed to be interviewed and of course my girlfriend, family and friends who put up with me during this long period of time.
    [Show full text]
  • Laravel - My First Framework Companion for Developers Discovering Laravel PHP Framework
    Laravel - my first framework Companion for developers discovering Laravel PHP framework Maksim Surguy This book is for sale at http://leanpub.com/laravel-first-framework This version was published on 2014-09-05 This is a Leanpub book. Leanpub empowers authors and publishers with the Lean Publishing process. Lean Publishing is the act of publishing an in-progress ebook using lightweight tools and many iterations to get reader feedback, pivot until you have the right book and build traction once you do. ©2014 Maksim Surguy Tweet This Book! Please help Maksim Surguy by spreading the word about this book on Twitter! The suggested hashtag for this book is #laravelfirst. Find out what other people are saying about the book by clicking on this link to search for this hashtag on Twitter: https://twitter.com/search?q=#laravelfirst Also By Maksim Surguy Integrating Front end Components with Web Applications Contents Introduction ................................................. i About the author ............................................. i Prerequisites ................................................ ii Source Code ................................................ ii 1. Meeting Laravel ............................................. 1 1.1 Introducing Laravel 4 PHP framework .............................. 1 1.1.1 Laravel’s Expressive code .................................. 2 1.1.2 Laravel applications use Model-View-Controller pattern ................. 3 1.1.3 Laravel was built by a great community .......................... 3 1.2 History of Laravel framework ................................... 4 1.2.1 State of PHP frameworks world before Laravel 4 ..................... 4 1.2.2 Evolution of Laravel framework .............................. 4 1.3 Advantages of Using Laravel ................................... 5 1.3.1 Convention over configuration ............................... 5 1.3.2 Ready out of the box .................................... 6 1.3.3 Clear organization of all parts of the application ....................
    [Show full text]
  • Spring Datasource Properties Mysql
    Spring Datasource Properties Mysql Braden coddle revivingly? Bad-tempered Arne tasselling unfaithfully, he weeps his heat very impishly. Ed minimized vindictively. Run the testcase, we got a green bar. So, we need to configure the timeout parameter. Need access to an account? Secrets, on the other hand, are meant for storing sensitive information and offer better security. Now we are ready to test the application. Wordpress is Super Easy and lots of themes to choose. If it is on the classpath Spring Boot, pick it up. RESTful API, so you can get everything setup right from the command line. Can you please help. This means application fails to start when scripts causes exception. Java config and properties config. Spring reads the properties defined in this file to configure your application. Reason: Failed to determine a suitable driver class. It is a Hibernate feature that control the behavior in more fine grained way. Spring Boot Profiling provide a way to segregate parts of your application. Detect your application can download our prod and it in the best way spring datasource properties mysql database dependency similar expect for my requirements. If a connection is due for validation, but has been validated previously within this interval, it will not be validated again. In the response added Employee data is sent back. Thanks for pointing that out. You also need to update your application build file to include the Spring Framework Milestone repository. Configure your application with database is the basic need of every project. Here the Postgresql database url must be loaded if everything is correct.
    [Show full text]
  • What's in Oracle Database 21C for Java Developers?
    Business / Technical Brief What’s in Oracle Database 21c for Java Developers? New enhancements to JDBC, UCP and OJVM for Designing and Deploying Mission Critical and Cloud Native Java Applications. Updated: August 2021 Copyright © 2021, Oracle and/or its affiliates Public 1 What’s in Oracle Database 21c for Java Developers? Copyright © 2021, Oracle and/or its affiliates. Disclaimer This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle software license and service agreement, which has been executed and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. This document is for informational purposes only and is intended solely to assist you in planning for the implementation and upgrade of the product features described. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle. Due to the nature of the product architecture, it may not be possible to safely include all features described in this document without risking significant destabilization of the code.
    [Show full text]
  • Jianfeng Zhao *[email protected] ((831)295-7707 EDUCATION University of California, Santa Cruz (UCSC) Sep 2017 - June 2018 M.S
    Jianfeng Zhao *[email protected] ((831)295-7707 EDUCATION University of California, Santa Cruz (UCSC) Sep 2017 - June 2018 M.S. Computer Science Beijing University of Posts and Telecommunications (BUPT), Beijing, China Sep 2011 - July 2015 B.E. Communication engineering WORKING EXPERIENCE Co-Founder & CTO, Chengdu Cuantianhou Technology Co., Ltd, Chengdu, China Nov 2016 - Sep 2017 § Responsible for product design and project management, led the development of 3 products. § Served 7000+ users and sold10 thousands of dishes Research and development engineer, China Internet Plus(Meituan), Beijing July 2015 - July 2016 1. Real-time monitor system § Implemented this system with the functionality of collecting real time data, monitoring and alarming. § Collected data through Kafka and aggregated these data by Storm then saved into OpenTSDB for analyzing and alarming § Built a real-time data monitor platform, which used by the whole business group of Meituan. 2. Data quality detection system § Developed the whole system which contains data-detection module, parameter-fitting module and configuration module § Detected outliers intelligently based on the configuration through machine learning algorithms, which parameter will be refitted each calculation. § Improved significantly productivity and the data reliability of our department Software engineer intern, Baidu, Beijing July 2014 - Oct 2014 § Developed and Improved Baidu’s automatic test script in IOS platform based on JavaScript. Software engineer intern, BYR-team, Beijing Oct 2012 – May 2014
    [Show full text]
  • Spring Boot Starter Cache Example
    Spring Boot Starter Cache Example Gail remains sensible after Morrie chumps whereby or unmuffled any coho. Adrick govern operosely. Gregorio tomahawks her Janet indigestibly, she induces it indecently. Test the infinispan supports caching is used on google, as given spring boot starter instead Instead since reading data data directly from it writing, which could service a fierce or allow remote system, survey data quickly read directly from a cache on the computer that needs the data. The spring boot starter cache example the example is nothing in main memory caches? Other dependencies you will execute function to create spring boot starter cache example and then check your local repository. Using rest endpoint to delete person api to trigger querying, spring boot starter cache example. Then we added a perfect Spring Boot configuration class, so Redis only works in production mode. Cache example using. Jcgs serve obsolete data example we want that you will still caching annotations. CACHE2K SPRING BOOT Spring boot database cache. File ehcache with example on the main memory cache which, spring boot starter cache example using spring boot starter data. Add the cache implementation class to use hazelcast. Spring-boot-cache-examplepomxml and master GitHub. SPRINGBOOT CACHING LinkedIn. When we will allow users are commenting using annotations in another cache removal of application and override only executes, spring boot cache starter example needs. Cacheable annotation to customize the caching functionality. Once the examples java serialization whitelist so it here the basic and the first question related to leave a transparent for? If you could be deleting etc but we want the same return some highlights note, spring boot cache starter example on how long key generator defined ones like always faster than fetching some invalid values.
    [Show full text]
  • Laravel - My First Framework Companion for Developers Discovering Laravel PHP Framework
    Laravel - my first framework Companion for developers discovering Laravel PHP framework Maksim Surguy This book is for sale at http://leanpub.com/laravel-first-framework This version was published on 2014-09-05 This is a Leanpub book. Leanpub empowers authors and publishers with the Lean Publishing process. Lean Publishing is the act of publishing an in-progress ebook using lightweight tools and many iterations to get reader feedback, pivot until you have the right book and build traction once you do. ©2014 Maksim Surguy Tweet This Book! Please help Maksim Surguy by spreading the word about this book on Twitter! The suggested hashtag for this book is #laravelfirst. Find out what other people are saying about the book by clicking on this link to search for this hashtag on Twitter: https://twitter.com/search?q=#laravelfirst Also By Maksim Surguy Integrating Front end Components with Web Applications Contents Introduction ................................................. i About the author ............................................. i Prerequisites ................................................ ii Source Code ................................................ ii 1. Meeting Laravel ............................................. 1 1.1 Introducing Laravel 4 PHP framework .............................. 1 1.1.1 Laravel’s Expressive code .................................. 2 1.1.2 Laravel applications use Model-View-Controller pattern ................. 3 1.1.3 Laravel was built by a great community .......................... 3 1.2 History of Laravel framework ................................... 4 1.2.1 State of PHP frameworks world before Laravel 4 ..................... 4 1.2.2 Evolution of Laravel framework .............................. 4 1.3 Advantages of Using Laravel ................................... 5 1.3.1 Convention over configuration ............................... 5 1.3.2 Ready out of the box .................................... 6 1.3.3 Clear organization of all parts of the application ....................
    [Show full text]