DOCSLIB.ORG

Migrating Oracle Databases to Open Source Technologies

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Migrating Oracle Databases to Open Source Technologies AUTHOR John Schulz Principal Consultant, Microsoft MCM & MVP V01-012021-HW MIGRATING ORACLE DATABASES TO OPEN SOURCE TECHNOLOGIES | 2 Introduction Some Oracle customers today are beginning to weigh other options, often for a host of reasons including Oracle’s license and contract restrictions, customer audits, concern about eventually being locked in, and high support costs. One option they may choose is to migrate to open source databases (OSDBs) with much less restrictive licenses and no license fees. In this document, we will review the options current Oracle users have to migrate to open source database technology. We will start with what Oracle database technologies are currently in use, compare those to the many Open source options available, and then review how best to get there, including an evaluation of many of the robust tools available to help. All OSDBs offer a subset of the capabilities and feature options of the Oracle database, so first reviewing the Pythian white paper “Considerations For Converting From Oracle To Other RDBMS Platforms” is highly recommended. This will help ensure that the options, features, and non-functional capabilities unique to Oracle are either not used or are a palatable loss. No matter which Oracle database technologies are in use, there are three general approaches to migrating to an OSDB: 1. Direct migration Migrate the schema into the new OSDB format, modify the data manipulation language (DML) to work with the new OSDB technology, and copy over the data to the new database. This approach, while straightforward, is usually only practical for a small subset of OSDB technologies and in some cases not even for those. 2. Refactor the application and re-write for the new OSDB technologies chosen This approach, while daunting, is often the better one as it allows for a new application which eliminates technical debt and improves operability, including scaling and availability and faster features to market. It is also a major undertaking, and the return on investment is likely to be years away. 3. Find the right off-the-shelf application which supports the OSDB of your choice. The application itself may be either proprietary or open-source. pythian.com MIGRATING ORACLE DATABASES TO OPEN SOURCE TECHNOLOGIES | 3 Oracle Single-Instance vs RAC vs Exadata Oracle offers several products, and Oracle Database can roll out several specific feature sets to suit certain workloads. The kind of workload will, at least in part, drive the final decision as to which OSDB technologies are good use cases for the migration. Single-Instance Oracle Databases Many Oracle databases run on a single host, optionally with one or more standby databases providing disaster recovery (DR) , backup or query off-loading. These configurations are typically used by most small to medium-sized businesses for the majority of their database traffic. The workloads tend to vary extensively and can include transactional, content management, business intelligence, and data warehouse use cases. Oracle RAC This is Oracle’s premier high-volume transactional engine, designed for high availability (HA) via horizontal scalability. It operates as a cluster of computers with shared storage designed to scale beyond a single system while offering HA without replication. For DR, RAC installations also replicate to one or more standby RAC (or non-RAC) databases as part of Oracle’s Maximum Availability Architecture (MAA). Exadata Exadata is Oracle’s hardware-based product (with unique hardware and software capabilities, not replicable outside of the Exadata platform) designedto support large data warehouse applications and high volume OLTP applications. It is the only Oracle Database product that supports on-disk column store technology. Business Requirements Before thinking about which database technology to which you might want to migrate, you should evaluate your business requirements. Knowing what your real business requirements are will help you select the best OSDB technology in terms of the database itself, along with the way you’ll configure it and what tools you’ll use. High Availability (HA) We all want our databases to be highly available. But there is always a cost to keeping a database up 24X7, 365 days a year with 99.9999% uptime. Understanding your real needs will help identify what technologies you should investigate and how you might want to configure them. pythian.com MIGRATING ORACLE DATABASES TO OPEN SOURCE TECHNOLOGIES | 4 Disaster Recovery (DR) What are your DR requirements? Will you need an active disaster site able to seamlessly take over from the primary? Will a passive backup be acceptable? Can you just rebuild from the data you have in another database, meaning the cost of DR may not even be justified? Global Data Distribution Will your database need to be available globally, with data replicated between nodes more or less transparently? Or will you want a single central database with geographically distributed copies? Or maybe you just want to store customer data in the closest datacenter, and then safely replicate it in just one other place. Rapid Response to Changing Requirements Will your database need to support rapid changes due to fluctuations in market conditions? To take advantage of new business opportunities? Or will the database structure be more or less static, changing only slightly over time? Regulatory Requirements What are your regulatory and compliance requirements? This matters a good deal. Depending on what kind of data you have, one or more of the OSDB databases may not meet your needs – or you may need additional software to make it work. If you are thinking of migrating to a public cloud, is the cloud or the database offering in the cloud certified and able to meet your compliance requirements? Continuous Availability during Migration When it comes time to migrate to the new database technology, will users of the source Oracle Database and the target OSDB database(s) require continuous uninterrupted access to all the data? Will access to most of the data be acceptable? Will it be okay for applications to be down? If so, for how long? Migrating data in a batch inside of a downtime window is clearly the easiest and simplest route but is not always acceptable. What is your requirement? Migration Approaches We mentioned up top that there are three general options when migrating from your Oracle Database. However, within those three options are many additional considerations. pythian.com MIGRATING ORACLE DATABASES TO OPEN SOURCE TECHNOLOGIES | 5 Direct Migration With direct migration, you will need to evaluate the existing schema and SQL code, especially any stored program code (PL/SQL). There are a number of tools available to help in this effort, such as Ora2Pg and AWS Database Migration Services (DMS). After determining what features and functions are missing or just named differently, you will need to convert the schema and code. In many cases, this means changing at least some program logic. If your code used an object-relational mapper (ORM), this may prove relatively painless. If not, and if there are many lines of code to change, this could be a major effort. Once you complete the analysis and translation phases, you will next need to set up a test environment to validate the schema and code changes. After all these considerations are carefully weighed, it’s finally time to migrate the data. There are two approaches you can take: 1. Batch Shut down the existing application, dump the data, and restore it to the new database. This can be done through utilities like Ora2Pg or AWS DMS. It also can typically be done by performing a SQL-level dump from Oracle, suitably modifying it, and restoring it into the new database. This approach is generally straightforward and if downtime is acceptable, it’s often the simplest approach 2. Online heterogeneous replication In this case, you bring up both databases, load a copy of the production data into the new database, and start replicating from the existing Oracle Database to the new one. Oracle Golden Gate can target many databases and do this for you. You can also use AWS DMS (if you are migrating to AWS). There are also numerous other third-party options, with one of the most versatile being Kafka. In that case, you use an Oracle sink to write to Kafka, which can be done via Golden Gate. You must then use a source for your database to write to your new database. This approach allows for transformation work to take place between the source and destination, which is sometimes useful. Method two is the most common since it requires no downtime and can sometimes accommodate a slow roll migration with replication going in both directions. But it is also much harder to implement. Refactor and Rewrite For many large, complex databases using many Oracle-specific features and large amounts of stored program code, this is the correct approach. pythian.com MIGRATING ORACLE DATABASES TO OPEN SOURCE TECHNOLOGIES | 6 It also provides additional benefits: • Eliminate Technical debt – Old code and workarounds to resolve compatibility with old features make code fragile and difficult to fix or enhance • Move to a modern microservice framework – Allows developers to create new features faster with generally lower error rates • An updated codebase is a golden opportunity to implement data governance best practices from the ground up When taking this approach it is common to break a single monolithic database
Recommended publications
  • Beyond Relational Databases

    Beyond Relational Databases

    EXPERT ANALYSIS BY MARCOS ALBE, SUPPORT ENGINEER, PERCONA Beyond Relational Databases: A Focus on Redis, MongoDB, and ClickHouse Many of us use and love relational databases… until we try and use them for purposes which aren’t their strong point. Queues, caches, catalogs, unstructured data, counters, and many other use cases, can be solved with relational databases, but are better served by alternative options. In this expert analysis, we examine the goals, pros and cons, and the good and bad use cases of the most popular alternatives on the market, and look into some modern open source implementations. Beyond Relational Databases Developers frequently choose the backend store for the applications they produce. Amidst dozens of options, buzzwords, industry preferences, and vendor offers, it’s not always easy to make the right choice… Even with a map! !# O# d# "# a# `# @R*7-# @94FA6)6 =F(*I-76#A4+)74/*2(:# ( JA$:+49>)# &-)6+16F-# (M#@E61>-#W6e6# &6EH#;)7-6<+# &6EH# J(7)(:X(78+# !"#$%&'( S-76I6)6#'4+)-:-7# A((E-N# ##@E61>-#;E678# ;)762(# .01.%2%+'.('.$%,3( @E61>-#;(F7# D((9F-#=F(*I## =(:c*-:)U@E61>-#W6e6# @F2+16F-# G*/(F-# @Q;# $%&## @R*7-## A6)6S(77-:)U@E61>-#@E-N# K4E-F4:-A%# A6)6E7(1# %49$:+49>)+# @E61>-#'*1-:-# @E61>-#;6<R6# L&H# A6)6#'68-# $%&#@:6F521+#M(7#@E61>-#;E678# .761F-#;)7-6<#LNEF(7-7# S-76I6)6#=F(*I# A6)6/7418+# @ !"#$%&'( ;H=JO# ;(\X67-#@D# M(7#J6I((E# .761F-#%49#A6)6#=F(*I# @ )*&+',"-.%/( S$%=.#;)7-6<%6+-# =F(*I-76# LF6+21+-671># ;G';)7-6<# LF6+21#[(*:I# @E61>-#;"# @E61>-#;)(7<# H618+E61-# *&'+,"#$%&'$#( .761F-#%49#A6)6#@EEF46:1-#
  • ACID Compliant Distributed Key-Value Store

    ACID Compliant Distributed Key-Value Store

    ACID Compliant Distributed Key-Value Store #1 #2 #3 Lakshmi Narasimhan Seshan ,​ Rajesh Jalisatgi ,​ Vijaeendra Simha G A # ​ ​ ​ ​1l​ [email protected] # ​2r​ [email protected] #3v​ [email protected] Abstract thought that would be easier to implement. All Built a fault-tolerant and strongly-consistent key/value storage components run http and grpc endpoints. Http endpoints service using the existing RAFT implementation. Add ACID are for debugging/configuration. Grpc Endpoints are transaction capability to the service using a 2PC variant. Build used for communication between components. on the raftexample[1] (available as part of etcd) to add atomic Replica Manager (RM): RM is the service discovery transactions. This supports sharding of keys and concurrent transactions on sharded KV Store. By Implementing a part of the system. RM is initiated with each of the transactional distributed KV store, we gain working knowledge Replica Servers available in the system. Users have to of different protocols and complexities to make it work together. instantiate the RM with the number of shards that the user wants the key to be split into. Currently we cannot Keywords— ACID, Key-Value, 2PC, sharding, 2PL Transaction dynamically change while RM is running. New Replica ​ ​ Servers cannot be added or removed from once RM is I. INTRODUCTION ​ up and running. However Replica Servers can go down Distributed KV stores have become a norm with the and come back and RM can detect this. Each Shard advent of microservices architecture and the NoSql Leader updates the information to RM, while the DTM revolution. Initially KV Store discarded ACID properties leader updates its information to the RM.
  • Smart Anomaly Detection and Prediction for Assembly Process Maintenance in Compliance with Industry 4.0

    Smart Anomaly Detection and Prediction for Assembly Process Maintenance in Compliance with Industry 4.0

    sensors Article Smart Anomaly Detection and Prediction for Assembly Process Maintenance in Compliance with Industry 4.0 Pavol Tanuska * , Lukas Spendla, Michal Kebisek, Rastislav Duris and Maximilian Stremy Faculty of Materials Science and Technology in Trnava, Slovak University of Technology in Bratislava, 917 24 Trnava, Slovakia; [email protected] (L.S.); [email protected] (M.K.); [email protected] (R.D.); [email protected] (M.S.) * Correspondence: [email protected]; Tel.: +421-918-646-061 Abstract: One of the big problems of today’s manufacturing companies is the risks of the assembly line unexpected cessation. Although planned and well-performed maintenance will significantly reduce many of these risks, there are still anomalies that cannot be resolved within standard mainte- nance approaches. In our paper, we aim to solve the problem of accidental carrier bearings damage on an assembly conveyor. Sometimes the bearing of one of the carrier wheels is seized, causing the conveyor, and of course the whole assembly process, to halt. Applying standard approaches in this case does not bring any visible improvement. Therefore, it is necessary to propose and implement a unique approach that incorporates Industrial Internet of Things (IIoT) devices, neural networks, and sound analysis, for the purpose of predicting anomalies. This proposal uses the mentioned approaches in such a way that the gradual integration eliminates the disadvantages of individual approaches while highlighting and preserving the benefits of our solution. As a result, we have created and deployed a smart system that is able to detect and predict arising anomalies and achieve significant reduction in unexpected production cessation.
  • The Functionality of the Sql Select Clause

    The Functionality of the Sql Select Clause

    The Functionality Of The Sql Select Clause Neptunian Myron bumbles grossly or ablates ana when Dustin is pendant. Rolando remains spermatozoon: she protrude lickety-split.her Avon thieve too bloodlessly? Donnie catapults windily as unsystematic Alexander kerns her bisections waggle The sql the functionality select clause of a function avg could Capabilities of people SELECT Statement Data retrieval from several base is done through appropriate or efficient payment of SQL Three concepts from relational theory. In other subqueries that for cpg digital transformation and. How do quickly write the select statement in SQL? Lesson 32 Introduction to SAS SQL. Exist in clauses with. If function is clause of functionality offered by if you can use for modernizing legacy sql procedure in! Moving window function takes place of functionality offered by clause requires select, a new table in! The SQL standard requires that switch must reference only columns in clean GROUP BY tender or columns used in aggregate functions However MySQL. The full clause specifies the columns of the final result table. The SELECT statement is probably the less important SQL command It's used to return results from our databases. The following SQL statement will display the appropriate of books. For switch, or owe the DISTINCT values, date strings and TIMESTAMP data types. SQL SELECT Statement TechOnTheNet. Without this table name, proporcionar experiencias personalizadas, but signify different tables. NULL value, the queries presented are only based on tables. So, GROUP BY, step CREATE poverty AS statement provides a superset of functionality offered by the kiss INTO statement. ELSE logic: SQL nested Queries with Select.
  • See Schema of Table Mysql

    See Schema of Table Mysql

    See Schema Of Table Mysql Debonair Antin superadd that subalterns outrivals impromptu and cripple helpfully. Wizened Teodoor cross-examine very yestereve while Lionello remains orthophyric and ineffective. Mucking Lex usually copping some casbahs or flatten openly. Sql on the examples are hitting my old database content from ingesting data lake using describe essentially displays all of mysql, and field data has the web tutorial on The certification names then a specified table partitions used. Examining the gap in SQL injection attacks Web. Create own table remain the same schema as another output of FilterDeviceAlertEvents 2. TABLES view must query results contain a row beginning each faucet or view above a dataset The INFORMATIONSCHEMATABLES view has left following schema. Follow along with other database schema diff you see cdc. A Schema in SQL is a collection of database objects linked with an particular. The oracle as drop various techniques of. Smart phones and mysql database include: which table and web business domain and inductive impedance always come to see where. Cookies on a backup and their db parameter markers or connection to run, and information about is built up. MySQL Show View using INFORMATIONSCHEMA database The tableschema column stores the schema or database of the preliminary or waist The tablename. Refer to Fetch rows from MySQL table in Python to button the data that usually just. Data dictionary as follows: we are essentially displays folders and foreign keys and views, processing are hypothetical ideas of field knows how many other. Maintaining tables is one process the preventative MySQL database maintenance tasks.
  • Using Sqlancer to Test Clickhouse and Other Database Systems

    Using Sqlancer to Test Clickhouse and Other Database Systems

    Using SQLancer to test ClickHouse and other database systems Manuel Rigger Ilya Yatsishin @RiggerManuel qoega Plan ▎ What is ClickHouse and why do we need good testing? ▎ How do we test ClickHouse and what problems do we have to solve? ▎ What is SQLancer and what are the ideas behind it? ▎ How to add support for yet another DBMS to SQLancer? 2 ▎ Open Source analytical DBMS for BigData with SQL interface. • Blazingly fast • Scalable • Fault tolerant 2021 2013 Project 2016 Open ★ started Sourced 15K GitHub https://github.com/ClickHouse/clickhouse 3 Why do we need good CI? In 2020: 361 4081 261 11 <15 Contributors Merged Pull New Features Releases Core Team Requests 4 Pull Requests exponential growth 5 All GitHub data available in ClickHouse https://gh.clickhouse.tech/explorer/ https://gh-api.clickhouse.tech/play 6 How is ClickHouse tested? 7 ClickHouse Testing • Style • Flaky check for new or changed tests • Unit • All tests are run in with sanitizers • Functional (address, memory, thread, undefined • Integrational behavior) • Performance • Thread fuzzing (switch running threads • Stress randomly) • Static analysis (clang-tidy, PVSStudio) • Coverage • Compatibility with OS versions • Fuzzing 9 100K tests is not enough Fuzzing ▎ libFuzzer to test generic data inputs – formats, schema etc. ▎ Thread Fuzzer – randomly switch threads to trigger races and dead locks › https://presentations.clickhouse.tech/cpp_siberia_2021/ ▎ AST Fuzzer – mutate queries on AST level. › Use SQL queries from all tests as input. Mix them. › High level mutations. Change query settings › https://clickhouse.tech/blog/en/2021/fuzzing-clickhouse/ 12 Test development steps Common tests Instrumentation Fuzzing The next step Unit, Find bugs earlier.
  • A Gridgain Systems In-Memory Computing White Paper

    A Gridgain Systems In-Memory Computing White Paper

    WHITE PAPER A GridGain Systems In-Memory Computing White Paper February 2017 © 2017 GridGain Systems, Inc. All Rights Reserved. GRIDGAIN.COM WHITE PAPER Accelerate MySQL for Demanding OLAP and OLTP Use Cases with Apache Ignite Contents Five Limitations of MySQL ............................................................................................................................. 2 Delivering Hot Data ................................................................................................................................... 2 Dealing with Highly Volatile Data ............................................................................................................. 3 Handling Large Data Volumes ................................................................................................................... 3 Providing Analytics .................................................................................................................................... 4 Powering Full Text Searches ..................................................................................................................... 4 When Two Trends Converge ......................................................................................................................... 4 The Speed and Power of Apache Ignite ........................................................................................................ 5 Apache Ignite Tames a Raging River of Data ...............................................................................................
  • Grpc - a Solution for Rpcs by Google Distributed Systems Seminar at Charles University in Prague, Nov 2016 Jan Tattermusch - Grpc Software Engineer

    Grpc - a Solution for Rpcs by Google Distributed Systems Seminar at Charles University in Prague, Nov 2016 Jan Tattermusch - Grpc Software Engineer

    gRPC - A solution for RPCs by Google Distributed Systems Seminar at Charles University in Prague, Nov 2016 Jan Tattermusch - gRPC Software Engineer About me ● Software Engineer at Google (since 2013) ● Working on gRPC since Q4 2014 ● Graduated from Charles University (2010) Contacts ● jtattermusch on GitHub ● Feedback to [email protected] @grpcio Motivation: gRPC Google has an internal RPC system, called Stubby ● All production applications use RPCs ● Over 1010 RPCs per second in total ● 4 generations over 13 years (since 2003) ● APIs for C++, Java, Python, Go What's missing ● Not suitable for external use (tight coupling with internal tools & infrastructure) ● Limited language & platform support ● Proprietary protocol and security ● No mobile support @grpcio What's gRPC ● HTTP/2 based RPC framework ● Secure, Performant, Multiplatform, Open Multiplatform ● Idiomatic APIs in popular languages (C++, Go, Java, C#, Node.js, Ruby, PHP, Python) ● Supports mobile devices (Android Java, iOS Obj-C) ● Linux, Windows, Mac OS X ● (web browser support in development) OpenSource ● developed fully in open on GitHub: https://github.com/grpc/ @grpcio Use Cases Build distributed services (microservices) Service 1 Service 3 ● In public/private cloud ● Google's own services Service 2 Service 4 Client-server communication ● Mobile ● Web ● Also: Desktop, embedded devices, IoT Access APIs (Google, OSS) @grpcio Key Features ● Streaming, Bidirectional streaming ● Built-in security and authentication ○ SSL/TLS, OAuth, JWT access ● Layering on top of HTTP/2
  • Database Software Market: Billy Fitzsimmons +1 312 364 5112

    Database Software Market: Billy Fitzsimmons +1 312 364 5112

    Equity Research Technology, Media, & Communications | Enterprise and Cloud Infrastructure March 22, 2019 Industry Report Jason Ader +1 617 235 7519 [email protected] Database Software Market: Billy Fitzsimmons +1 312 364 5112 The Long-Awaited Shake-up [email protected] Naji +1 212 245 6508 [email protected] Please refer to important disclosures on pages 70 and 71. Analyst certification is on page 70. William Blair or an affiliate does and seeks to do business with companies covered in its research reports. As a result, investors should be aware that the firm may have a conflict of interest that could affect the objectivity of this report. This report is not intended to provide personal investment advice. The opinions and recommendations here- in do not take into account individual client circumstances, objectives, or needs and are not intended as recommen- dations of particular securities, financial instruments, or strategies to particular clients. The recipient of this report must make its own independent decisions regarding any securities or financial instruments mentioned herein. William Blair Contents Key Findings ......................................................................................................................3 Introduction .......................................................................................................................5 Database Market History ...................................................................................................7 Market Definitions
  • Implementing and Testing Cockroachdb on Kubernetes

    Implementing and Testing Cockroachdb on Kubernetes

    Implementing and testing CockroachDB on Kubernetes Albert Kasperi Iho Supervisors: Ignacio Coterillo Coz, Ricardo Brito Da Rocha Abstract This report will describe implementing CockroachDB on Kubernetes, a sum- mer student project done in 2019. The report addresses the implementation, monitoring, testing and results of the project. In the implementation and mon- itoring parts, a closer look to the full pipeline will be provided, with the intro- duction of all the frameworks used and the biggest problems that were faced during the project. After that, the report describes the testing process of Cock- roachDB, what tools were used in the testing and why. The results of testing will be presented after testing with the conclusion of results. Keywords CockroachDB; Kubernetes; benchmark. Contents 1 Project specification . 2 2 Implementation . 2 2.1 Kubernetes . 2 2.2 CockroachDB . 3 2.3 Setting up Kubernetes in CERN environment . 3 3 Monitoring . 3 3.1 Prometheus . 4 3.2 Prometheus Operator . 4 3.3 InfluxDB . 4 3.4 Grafana . 4 3.5 Scraping and forwarding metrics from the Kubernetes cluster . 4 4 Testing CockroachDB on Kubernetes . 5 4.1 SQLAlchemy . 5 4.2 Pgbench . 5 4.3 CockroachDB workload . 6 4.4 Benchmarking CockroachDB . 6 5 Test results . 6 5.1 SQLAlchemy . 6 5.2 Pgbench . 6 5.3 CockroachDB workload . 7 5.4 Conclusion . 7 6 Acknowledgements . 7 1 Project specification The core goal of the project was taking a look into implementing a database framework on top of Kuber- netes, the challenges in implementation and automation possibilities. Final project pipeline included a CockroachDB cluster running in Kubernetes with Prometheus monitoring both of them.
  • SAHA: a String Adaptive Hash Table for Analytical Databases

    SAHA: a String Adaptive Hash Table for Analytical Databases

    applied sciences Article SAHA: A String Adaptive Hash Table for Analytical Databases Tianqi Zheng 1,2,* , Zhibin Zhang 1 and Xueqi Cheng 1,2 1 CAS Key Laboratory of Network Data Science and Technology, Institute of Computing Technology, Chinese Academy of Sciences, Beijing 100190, China; [email protected] (Z.Z.); [email protected] (X.C.) 2 University of Chinese Academy of Sciences, Beijing 100049, China * Correspondence: [email protected] Received: 3 February 2020; Accepted: 9 March 2020; Published: 11 March 2020 Abstract: Hash tables are the fundamental data structure for analytical database workloads, such as aggregation, joining, set filtering and records deduplication. The performance aspects of hash tables differ drastically with respect to what kind of data are being processed or how many inserts, lookups and deletes are constructed. In this paper, we address some common use cases of hash tables: aggregating and joining over arbitrary string data. We designed a new hash table, SAHA, which is tightly integrated with modern analytical databases and optimized for string data with the following advantages: (1) it inlines short strings and saves hash values for long strings only; (2) it uses special memory loading techniques to do quick dispatching and hashing computations; and (3) it utilizes vectorized processing to batch hashing operations. Our evaluation results reveal that SAHA outperforms state-of-the-art hash tables by one to five times in analytical workloads, including Google’s SwissTable and Facebook’s F14Table. It has been merged into the ClickHouse database and shows promising results in production. Keywords: hash table; analytical database; string data 1.
  • Architecting Cloud-Native NET Apps for Azure (2020).Pdf

    Architecting Cloud-Native NET Apps for Azure (2020).Pdf

    EDITION v.1.0 PUBLISHED BY Microsoft Developer Division, .NET, and Visual Studio product teams A division of Microsoft Corporation One Microsoft Way Redmond, Washington 98052-6399 Copyright © 2020 by Microsoft Corporation All rights reserved. No part of the contents of this book may be reproduced or transmitted in any form or by any means without the written permission of the publisher. This book is provided “as-is” and expresses the author’s views and opinions. The views, opinions, and information expressed in this book, including URL and other Internet website references, may change without notice. Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred. Microsoft and the trademarks listed at https://www.microsoft.com on the “Trademarks” webpage are trademarks of the Microsoft group of companies. Mac and macOS are trademarks of Apple Inc. The Docker whale logo is a registered trademark of Docker, Inc. Used by permission. All other marks and logos are property of their respective owners. Authors: Rob Vettor, Principal Cloud System Architect/IP Architect - thinkingincloudnative.com, Microsoft Steve “ardalis” Smith, Software Architect and Trainer - Ardalis.com Participants and Reviewers: Cesar De la Torre, Principal Program Manager, .NET team, Microsoft Nish Anil, Senior Program Manager, .NET team, Microsoft Jeremy Likness, Senior Program Manager, .NET team, Microsoft Cecil Phillip, Senior Cloud Advocate, Microsoft Editors: Maira Wenzel, Program Manager, .NET team, Microsoft Version This guide has been written to cover .NET Core 3.1 version along with many additional updates related to the same “wave” of technologies (that is, Azure and additional third-party technologies) coinciding in time with the .NET Core 3.1 release.