DOCSLIB.ORG

Configuring Data Sources in Your Quarkus Applications

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Configuring Data Sources in Your Quarkus Applications Red Hat build of Quarkus 1.7 Configuring data sources in your Quarkus applications Last Updated: 2021-04-19 Red Hat build of Quarkus 1.7 Configuring data sources in your Quarkus applications Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project. The OpenStack ® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community. All other trademarks are the property of their respective owners. Abstract Configure a data source for your Quarkus application using extensions for built-in database drivers and connect your application to a relational database. Table of Contents Table of Contents .M . A. .K . I.N . .G . .O . P. .E . N. S. .O . U. .R . C. .E . .M . .O . R. .E . .I N. .C . L. .U . S. .I V. .E . 3. .C . H. .A . P. .T .E . R. 1.. .I .N . T. .R .O . .D . U. .C . T. .I O. N. T. O. .U . S. .I N. .G . D . .A . T. A. S. .O . U. R. C. .E . S. W. I.T . H. Q. .U . .A .R . K. .U . S. .4 . 1.1. SETTING THE DB-KIND PROPERTY FOR A DATA SOURCE 4 1.2. SETTING DATABASE CREDENTIALS 5 1.3. QUARKUS DRIVER EXTENSIONS FOR BUILT-IN DATABASES 5 .C . H. .A . P. .T .E . R. 2. J. .D . B. .C . .D . A. .T . A. S. .O . U. .R . C. .E . .C . O. .N . .F .I .G . U. .R . A. .T . I.O . N. 8. 2.1. INSTALLING QUARKUS EXTENSIONS FOR JDBC DATA SOURCES 8 2.2. SETTING THE JDBC URL OF YOUR DATA SOURCE 9 2.3. OBTAINING A JDBC DATA SOURCE WITH HIBERNATE ORM 9 2.4. DISABLING A JDBC DATA SOURCE IN A SIMULTANEOUS CONFIGURATION 10 2.5. CONFIGURING JDBC DRIVERS WITH NO BUILT-IN DRIVER EXTENSION 10 2.6. CONFIGURING MULTIPLE JDBC DATA SOURCES 11 .C . H. .A . P. .T .E . R. 3. R. .E . A. .C . T. .I V. .E . .D . A. .T . A. S . O. U. .R . C. .E . C. .O . .N . F. .I G. .U . .R .A . T. .I O. N. 1.4 . 3.1. SETTING THE REACTIVE DATA SOURCE CONNECTION URL 14 3.2. DISABLING A REACTIVE DATA SOURCE IN A SIMULTANEOUS CONFIGURATION 15 .C . H. .A . P. .T .E . R. 4. .D . A. .T .A . S . O. U. .R . C. .E . M. A. .N . A. .G . .E .M . .E . N. .T . 1.6 . 4.1. DATA SOURCE HEALTH CHECK 16 4.2. DATA SOURCE METRICS 16 4.3. NARAYANA TRANSACTION MANAGER INTEGRATION 16 4.4. TEST WITH IN-MEMORY DATABASES 16 APPENDIX A. JDBC DATABASE CONNECTION URLS FOR DATABASES WITH PRODUCTION AND .D . E. V. .E . L. .O . P. .M . .E . N. .T . .S .U . P. .P . O. R. .T . 1.8 . A.1. POSTGRESQL DATABASE URL EXAMPLE 18 A.2. MARIADB DATABASE URL EXAMPLE 18 A.3. MYSQL DATABASE URL EXAMPLE 18 A.4. MICROSOFT SQL SERVER DATABASE URL EXAMPLE 19 .A .P . P. .E . N. .D . I. X. B . J. .D . B. .C . .D . .A .T . A. .B . A. .S . E. C . .O . N. .N . .E .C . T. .I O. N. U. .R . L. .S . F. .O . R. D. .A . T. .A . B. .A . S. .E .S . .W . .I T. .H . .D . E. .V . E. .L .O . .P . M. E. N. T. .S . U. .P . P. .O . R. .T . 20 B.1. DERBY DATABASE URL EXAMPLE 20 B.2. H2 DATABASE URL EXAMPLE 20 1 Red Hat build of Quarkus 1.7 Configuring data sources in your Quarkus applications 2 MAKING OPEN SOURCE MORE INCLUSIVE MAKING OPEN SOURCE MORE INCLUSIVE Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message . 3 Red Hat build of Quarkus 1.7 Configuring data sources in your Quarkus applications CHAPTER 1. INTRODUCTION TO USING DATA SOURCES WITH QUARKUS When you want to add persistent data storage to your application, you must connect your application to a relational database. To achieve this, you use a data source that you connect to your application using a database driver. You can connect your Quarkus application to one or multiple data sources. You can use the data source management functionalities integrated into Quarkus to: configure your application to use one or multiple data sources obtain references to data sources in your code view and set pool tuning configuration properties In Quarkus applications, you can use two types of database drivers to connect your application to a relational database. You can use multiple data sources of both types in one application simultaneously: JDBC drivers that use the standard JDBC API that provides database connectivity for Java-based application. Quarkus JDBC drivers manage database connections using Agroal, a fast, light-weight, and highly scalable database connection pool implementation that is integrated with other features of Quarkus, including security, transaction management and health checks. Reactive drivers that are based on the data source driver implementation in Eclipse Vert.x. Eclipse Vert.x reactive data source drivers provide the non-blocking and reactive network-related features of Quarkus and are suitable for applications that are designed to be highly scalable and event-driven. You can configure both types of data source drivers using a set of unified and flexible configuration options that Quarkus provides. 1.1. SETTING THE DB-KIND PROPERTY FOR A DATA SOURCE When you set the db-kind property in the configuration file of your application to match the type of your data source that you want to use, Quarkus automatically resolves the appropriate type of database driver. The following procedure demonstrates how you can set the db-kind property for a data source. Prerequisites You have a Quarkus Maven project. Procedure 1. Navigate to your Quarkus project directory. 2. In the src/main/resources/application.properties file, set the value of the db-kind property to match the type of the data source that you want to use. The following example uses postgresql as the data source type: quarkus.datasource.db-kind=postgresql Additional resources Driver extensions for Quarkus built-in databases 4 CHAPTER 1. INTRODUCTION TO USING DATA SOURCES WITH QUARKUS 1.2. SETTING DATABASE CREDENTIALS You can define credentials that your application uses to access your database. Defining access credentials for your database is optional. You can skip this procedure when configuring a data source for your application. Prerequisites You have a Quarkus Maven project. You have set the db-kind property for your data source. Your Quarkus application is in JVM mode. This prerequisite applies when you use a JDBC driver that Quarkus does not support in native mode. Procedure 1. Navigate to your Quarkus project directory. 2. In the src/main/resources/application.properties file, set the value of the quarkus.datasource.username property to match the username that your application uses to access the database: quarkus.datasource.username=<username> 3. In the src/main/resources/application.properties file, set the value of the quarkus.datasource.password property to match the password that your application uses to access the database: quarkus.datasource.password=<password> Additional resources Setting the db-kind property for a data source 1.3. QUARKUS DRIVER EXTENSIONS FOR BUILT-IN DATABASES The following table provides an overview of Quarkus built-in databases and the extensions that you can use to connect your application to a relational database: Table 1.1. Driver extensions for Quarkus built-in databases Database db-kind Agroal extension Reactive extension built-in DB2 db2 quarkus-jdbc-db2 quarkus-reactive-db2-client Derby derby quarkus-jdbc-derby N/A H2 h2 quarkus-jdbc-h2 N/A MariaDB mariadb quarkus-jdbc-mariadb quarkus-reactive-mysql-client 5 Red Hat build of Quarkus 1.7 Configuring data sources in your Quarkus applications Database db-kind Agroal extension Reactive extension built-in Microsoft mssql quarkus-jdbc-mssql N/A SQL Server MySQL mysql quarkus-jdbc-mysql quarkus-reactive-mysql-client PostgreSQL postgresql, quarkus-jdbc-postgresql quarkus-reactive-pg-client pgsql, or pg You can configure H2 and Derby databases to run in embedded mode.
Load more

Recommended publications
  • Histcoroy Pyright for Online Information and Ordering of This and Other Manning Books, Please Visit Topwicws W.Manning.Com
    www.allitebooks.com HistCoroy pyright For online information and ordering of this and other Manning books, please visit Topwicws w.manning.com. The publisher offers discounts on this book when ordered in quantity. For more information, please contact Tutorials Special Sales Department Offers & D e al s Manning Publications Co. 20 Baldwin Road Highligh ts PO Box 761 Shelter Island, NY 11964 Email: [email protected] Settings ©2017 by Manning Publications Co. All rights reserved. Support No part of this publication may be reproduced, stored in a retrieval system, or Sign Out transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, without prior written permission of the publisher. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in the book, and Manning Publications was aware of a trademark claim, the designations have been printed in initial caps or all caps. Recognizing the importance of preserving what has been written, it is Manning’s policy to have the books we publish printed on acid­free paper, and we exert our best efforts to that end. Recognizing also our responsibility to conserve the resources of our planet, Manning books are printed on paper that is at least 15 percent recycled and processed without the use of elemental chlorine. Manning Publications Co. PO Box 761 Shelter Island, NY 11964 www.allitebooks.com Development editor: Cynthia Kane Review editor: Aleksandar Dragosavljević Technical development editor: Stan Bice Project editors: Kevin Sullivan, David Novak Copyeditor: Sharon Wilkey Proofreader: Melody Dolab Technical proofreader: Doug Warren Typesetter and cover design: Marija Tudor ISBN 9781617292576 Printed in the United States of America 1 2 3 4 5 6 7 8 9 10 – EBM – 22 21 20 19 18 17 www.allitebooks.com HistPoray rt 1.
    [Show full text]
  • Quarkus – the Kubernetes Native Java Framework
    Cheat Sheet Quarkus – the Kubernetes Native Java Framework by Alex Soto Start-Up What is Quarkus? Quarkus is a Kubernetes Native Java stack tailored for GraalVM & OpenJDK HotSpot that makes Java programs run 10X faster and 100X smaller. It also improves the developer ex- perience by adding features like live reloading/debugging and persistence with Panache. Requirements • Java 8 • Maven 3.5.3+ (recommended Maven 3.6.X) • GraalVM 19 or Docker (optional for native compilation) Scaffolding a Quarkus application You can create a minimal Quarkus application using a Maven goal. This goal creates a mi- nimal endpoint, a test and Docker resources: mvn io.quarkus:quarkus-maven-plugin:0.19.1:create \ -DprojectGroupId=org.alexsotob \ -DprojectArtifactId=jax \ -DclassName="org.alexsotob.quickstart.GreetingResource" \ -Dpath="/hello" Start Quarkus in live reload (dev) mode: ./mvnw compile quarkus:dev You can request the provided endpoint: curl http://localhost:8080/hello Live Reload You can make any change on any (Java) resource and, if the Quarkus application was star- ted in live reload mode, the change will be automatically reflected without having to re- compile or repackage the application. Try it by changing the output value of the src/main/- java/org/alexsotob/quickstart/GreetingResource.java class. Packaging Run ./mvnw package to generate a jar file called jax-1.0-SNAPSHOT-runner.jar that contains the application and lib directory containing required dependencies for running the applicati- on. Quarkus, unlike other solutions, does not create a fat jar so as to be Docker layers fri- endly. Both jar file and lib folder should be placed together in the same directory.
    [Show full text]
  • Data Modeler User's Guide
    Oracle® SQL Developer Data Modeler User's Guide Release 18.1 E94838-01 March 2018 Oracle SQL Developer Data Modeler User's Guide, Release 18.1 E94838-01 Copyright © 2008, 2018, Oracle and/or its affiliates. All rights reserved. Primary Author: Celin Cherian Contributing Authors: Chuck Murray Contributors: Philip Stoyanov This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • Podman, Buildah and Quarkus the Latest in Linux Containers Technology
    Podman, Buildah and Quarkus The Latest in Linux Containers Technology Daniel Oh Open Source Summit Japan 2019 1 About Me Daniel Oh ● Principal Technical Product Marketing Manager at Red Hat ○ Cloud Native App Development ○ Agile & DevOps practices ● CNCF Ambassador ● Java Developer ● Opensource.com Moderator ● Public Speaker & Writer [email protected] @danieloh30 danieloh30 INTRODUCTION Container tools landscape is changing. Why? Since Open Container Initiative (OCI) there are several new projects What needs do these projects address? What are these projects and when should I use them? What specific security concern does each address? 3 @danieloh30 INTRODUCTION Early concerns with Docker Since the early days enterprise users of Docker had concerns ● Build requires a “big fat” daemon on every host ● Regression for integration with container platforms Kubernetes/OpenShift ● Build has secret handling issues ● Root/privileged concerns at runtime ● Root/privileged concerns with daemon ● Build requires a running container 4 @danieloh30 INTRODUCTION ● Docker, Red Hat et al. June 2015 ● Two specifications ○ Image format ■ How to package an OCI Image with sufficient information to launch the application on the target platform ○ Runtime ■ How to launch a “filesystem bundle” that is unpacked on disk ● Version 1.0 of each released July 19th 2017 ● Distribution spec started in April, 2018. 5 @danieloh30 CONTAINERS ARE LINUX ARE CONTAINERS Containers are Linux 6 CONTAINERS ARE LINUX Container innovation continues …. buildah.io podman.io LXC Initial Docker OCI release initial CNCF Aug May Mar Mid Jun Nov Mar Apr Jun Sep May Sep May ‘08 ‘11 ‘13 ‘14 ‘15 ‘15 ‘16 ‘17 ‘17 ‘17 ‘18 ‘18 ‘19 Moby OpenShift Initial Buildah Buildah 1.0 online OpenShift release, Skopeo Podman Enterprise Buildah Podman New logo Kubernetes 3.0 RHEL 7 @danieloh30 CONTAINERS ARE LINUX How did Docker change containers? Docker Image Docker CLI Daemon Layers registry Application Docker daemon App.
    [Show full text]
  • Package 'Databaseconnector'
    Package ‘DatabaseConnector’ April 15, 2021 Type Package Title Connecting to Various Database Platforms Version 4.0.2 Date 2021-04-12 Description An R 'DataBase Interface' ('DBI') compatible interface to various database plat- forms ('PostgreSQL', 'Oracle', 'Microsoft SQL Server', 'Amazon Redshift', 'Microsoft Parallel Database Warehouse', 'IBM Netezza', 'Apache Im- pala', 'Google BigQuery', and 'SQLite'). Also includes support for fetching data as 'Andromeda' objects. Uses 'Java Database Connectivity' ('JDBC') to con- nect to databases (except SQLite). SystemRequirements Java version 8 or higher (https://www.java.com/) Depends R (>= 2.10) Imports rJava, SqlRender (>= 1.7.0), methods, stringr, rlang, utils, DBI (>= 1.0.0), urltools, bit64 Suggests aws.s3, R.utils, withr, testthat, DBItest, knitr, rmarkdown, RSQLite, ssh, Andromeda, dplyr License Apache License VignetteBuilder knitr URL https://ohdsi.github.io/DatabaseConnector/, https: //github.com/OHDSI/DatabaseConnector 1 2 R topics documented: BugReports https://github.com/OHDSI/DatabaseConnector/issues Copyright See file COPYRIGHTS RoxygenNote 7.1.1 Encoding UTF-8 R topics documented: connect . .3 createConnectionDetails . .6 createZipFile . .9 DatabaseConnectorDriver . 10 dbAppendTable,DatabaseConnectorConnection,character,data.frame-method . 10 dbClearResult,DatabaseConnectorResult-method . 11 dbColumnInfo,DatabaseConnectorResult-method . 12 dbConnect,DatabaseConnectorDriver-method . 13 dbCreateTable,DatabaseConnectorConnection,character,data.frame-method . 13 dbDisconnect,DatabaseConnectorConnection-method
    [Show full text]
  • Amazon Aurora Mysql Database Administrator's Handbook
    Amazon Aurora MySQL Database Administrator’s Handbook Connection Management March 2019 Notices Customers are responsible for making their own independent assessment of the information in this document. This document: (a) is for informational purposes only, (b) represents current AWS product offerings and practices, which are subject to change without notice, and (c) does not create any commitments or assurances from AWS and its affiliates, suppliers or licensors. AWS products or services are provided “as is” without warranties, representations, or conditions of any kind, whether express or implied. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers. © 2019 Amazon Web Services, Inc. or its affiliates. All rights reserved. Contents Introduction .......................................................................................................................... 1 DNS Endpoints .................................................................................................................... 2 Connection Handling in Aurora MySQL and MySQL ......................................................... 3 Common Misconceptions .................................................................................................... 5 Best Practices ...................................................................................................................... 6 Using Smart Drivers ........................................................................................................
    [Show full text]
  • Kyuubi Release 1.3.0 Kent
    Kyuubi Release 1.3.0 Kent Yao Sep 30, 2021 USAGE GUIDE 1 Multi-tenancy 3 2 Ease of Use 5 3 Run Anywhere 7 4 High Performance 9 5 Authentication & Authorization 11 6 High Availability 13 6.1 Quick Start................................................ 13 6.2 Deploying Kyuubi............................................ 47 6.3 Kyuubi Security Overview........................................ 76 6.4 Client Documentation.......................................... 80 6.5 Integrations................................................ 82 6.6 Monitoring................................................ 87 6.7 SQL References............................................. 94 6.8 Tools................................................... 98 6.9 Overview................................................. 101 6.10 Develop Tools.............................................. 113 6.11 Community................................................ 120 6.12 Appendixes................................................ 128 i ii Kyuubi, Release 1.3.0 Kyuubi™ is a unified multi-tenant JDBC interface for large-scale data processing and analytics, built on top of Apache Spark™. In general, the complete ecosystem of Kyuubi falls into the hierarchies shown in the above figure, with each layer loosely coupled to the other. For example, you can use Kyuubi, Spark and Apache Iceberg to build and manage Data Lake with pure SQL for both data processing e.g. ETL, and analytics e.g. BI. All workloads can be done on one platform, using one copy of data, with one SQL interface. Kyuubi provides the following features: USAGE GUIDE 1 Kyuubi, Release 1.3.0 2 USAGE GUIDE CHAPTER ONE MULTI-TENANCY Kyuubi supports the end-to-end multi-tenancy, and this is why we want to create this project despite that the Spark Thrift JDBC/ODBC server already exists. 1. Supports multi-client concurrency and authentication 2. Supports one Spark application per account(SPA). 3. Supports QUEUE/NAMESPACE Access Control Lists (ACL) 4.
    [Show full text]
  • Getting Started with Quarkus
    BROUGHT TO YOU IN PARTNERSHIP WITH CONTENTS ∙ Key Benefits ∙ Getting Started ∙ Key Components Getting Started ∙ JAX-RS ∙ Health Checks With Quarkus ∙ Security and JWT ∙ Docker and Native ∙ Container Images ∙ And more! ALEX SOTO ∙ Conclusion DIRECTOR OF DEVELOPER EXPERIENCE, RED HAT Quarkus is a Kubernetes-Native Java stack tailored to GraalVM and GETTING STARTED OpenJDK HotSpot, helping Java programs run 10X faster, while being To create a Quarkus service, you just need to run the next Maven goal 100X smaller. Improving the developer experience, Quarkus provides into an empty directory: additional features like live reloading and debugging as well as mvn io.quarkus:quarkus-maven-plugin:1.13.1.Final:create persistence with Panache. \ Its integration with the Eclipse MicroProfile specification also makes -DprojectGroupId=org.acme \ -DprojectArtifactId=hello-world \ it the perfect choice for developing microservices and deploying -DclassName="org.acme.quickstart.GreetingResource" \ them in Kubernetes. -Dpath="/hello" KEY BENEFITS LIVE RELOAD Quarkus offers near-instant scale-up and high-density utilization in Quarkus applications come with a live reload feature that allows container orchestration platforms such as Kubernetes. Many more the developer to make changes to their source code, which will be application instances can be run using the same hardware resources. directly reflected in the deployed code without having to recompile In Quarkus, classes used only at application startup are invoked at or repackage the source code. build time and not loaded into the runtime JVM. Quarkus also avoids reflection as much as possible. These design principles reduce the size and memory footprint of an application running on the JVM.
    [Show full text]
  • Database Language SQL: Integrator of CALS Data Repositories
    Database Language SQL: Integrator of CALS Data Repositories Leonard Gallagher Joan Sullivan U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Information Systems Engineering Division Computer Systems Laboratory Gaithersburg, MD 20899 NIST Database Language SQL Integrator of CALS Data Repositories Leonard Gallagher Joan Sullivan U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Information Systems Engineering Division Computer Systems Laboratory Gaithersburg, MD 20899 September 1992 U.S. DEPARTMENT OF COMMERCE Barbara Hackman Franklin, Secretary TECHNOLOGY ADMINISTRATION Robert M. White, Under Secretary for Technology NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY John W. Lyons, Director Database Language SQL: Integrator of CALS Data Repositories Leonard Gallagher Joan Sullivan National Institute of Standards and Technology Information Systems Engineering Division Gaithersburg, MD 20899, USA CALS Status Report on SQL and RDA - Abstract - The Computer-aided Acquisition and Logistic Support (CALS) program of the U.S. Department of Defense requires a logically integrated database of diverse data, (e.g., documents, graphics, alphanumeric records, complex objects, images, voice, video) stored in geographically separated data banks under the management and control of heterogeneous data management systems. An over-riding requirement is that these various data managers be able to communicate with each other and provide shared access to data and
    [Show full text]
  • Quarkus Cookbook Kubernetes-Optimized Java Solutions
    Quarkus Cookbook Kubernetes-Optimized Java Solutions Alex Soto Bueno & Jason Porter Quarkus Cookbook Kubernetes-Optimized Java Solutions Alex Soto Bueno and Jason Porter Quarkus Cookbook by Alex Soto Bueno and Jason Porter Copyright © 2020 Alex Soto Bueno and Jason Porter. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://oreilly.com). For more information, contact our corporate/institutional sales department: 800-998-9938 or [email protected]. Acquisitions Editor: Suzanne McQuade Indexer: Potomac Indexing, LLC Development Editor: Jeff Bleiel Interior Designer: David Futato Production Editor: Daniel Elfanbaum Cover Designer: Karen Montgomery Copyeditor: Piper Editorial Illustrator: Rebecca Demarest Proofreader: Amanda Kersey July 2020: First Edition Revision History for the First Edition 2020-07-14: First Release See http://oreilly.com/catalog/errata.csp?isbn=9781492062653 for release details. The O’Reilly logo is a registered trademark of O’Reilly Media, Inc. Quarkus Cookbook, the cover image, and related trade dress are trademarks of O’Reilly Media, Inc. The views expressed in this work are those of the authors, and do not represent the publisher’s views. While the publisher and the authors have used good faith efforts to ensure that the information and instructions contained in this work are accurate, the publisher and the authors disclaim all responsibility for errors or omissions, including without limitation responsibility for damages resulting from the use of or reliance on this work.
    [Show full text]
  • Microserviços Supersônicos E Subatômicos Com Quarkus Pedro Hos and William Siqueira Pedro Hos @ Github.Com/Pedro-Hos
    Microserviços Supersônicos e Subatômicos com Quarkus Pedro Hos and William Siqueira Pedro Hos @ github.com/pedro-hos ● Banco de Dados @ FATEC São José dos Campos 2012 ● I’ve worked as Java Developer in some companies ● Since 2017 I am Software Maintenance Engineer @ Red Hat ● JUG Leader at JUG Vale jugvale.com ● Contributor at SJCDigital github.com/sjcdigital ● Blogger at pedrohosilva.wordpress.com ● Opensource and some source code samples github.com/pedro-hos William Siqueira @ github.com/jesuino ● Banco de Dados @ FATEC São José dos Campos 2010 ● Software Engineer @ Red Hat ● Colaborador do JUG Vale jugvale.com ● Colaborador do SJCDigital github.com/sjcdigital ● Escreve em alguns blogs ● Palestrante JavaOne, The Developers Conference, FISL e outros ● Opensource github.com/jesuino Schedule ● Microservices overview ● Java and microservices ● Eclipse Microprofile ● Quarkus - numbers ○ First demo ■ Add hello endpoint - play with configuration - add json - add health check ■ add swagger - fault tolerance ● Quarkus features ○ Extensions - talk about all extensions ○ Second Demo - Database - security ○ Kogito Demo ● Quarkus Native - talk about how quarkus can be compiled to native ● Quarkus on Openshift/Kubernetes What are microservices Microservices - also known as the microservice architecture - is an architectural style that structures an application as a collection of services that are ● Highly maintainable and testable ● Loosely coupled ● Independently deployable ● Organized around business capabilities ● Owned by a small team The microservice
    [Show full text]
  • Performance Evaluation of Relational Embedded Databases: an Empirical
    Performance evaluation of relational Check for updates embedded databases: an empirical study Evaluación del rendimiento de bases de datos embebida: un estudio empírico Author: ABSTRACT 1 Hassan B. Hassan Introduction: With the rapid deployment of embedded databases Qusay I. Sarhan2 across a wide range of embedded devices such as mobile devices, Internet of Things (IoT) devices, etc., the amount of data generat- ed by such devices is also growing increasingly. For this reason, the SCIENTIFIC RESEARCH performance is considered as a crucial criterion in the process of selecting the most suitable embedded database management system How to cite this paper: to be used to store/retrieve data of these devices. Currently, many Hassan, B. H., and Sarhan, Q. I., Performance embedded databases are available to be utilized in this context. Ma- evaluation of relational embedded databases: an empirical study, Kurdistan, Irak. Innovaciencia. terials and Methods: In this paper, four popular open-source rela- 2018; 6(1): 1-9. tional embedded databases; namely, H2, HSQLDB, Apache Derby, http://dx.doi.org/10.15649/2346075X.468 and SQLite have been compared experimentally with each other to evaluate their operational performance in terms of creating data- Reception date: base tables, retrieving data, inserting data, updating data, deleting Received: 22 September 2018 Accepted: 10 December 2018 data. Results and Discussion: The experimental results of this Published: 28 December 2018 paper have been illustrated in Table 4. Conclusions: The experi- mental results and analysis showed that HSQLDB outperformed other databases in most evaluation scenarios. Keywords: Embedded devices, Embedded databases, Performance evaluation, Database operational performance, Test methodology.
    [Show full text]