Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Microsoft Power Platform Enterprise Architecture

You're reading from   Microsoft Power Platform Enterprise Architecture Design tailor-made solutions for architects and decision makers to meet complex business requirements

Arrow left icon
Product type Paperback
Published in Jan 2023
Publisher Packt
ISBN-13 9781804612637
Length 534 pages
Edition 2nd Edition
Languages
Concepts
Arrow right icon
Author (1):
Arrow left icon
Robert Rybaric Robert Rybaric
Author Profile Icon Robert Rybaric
Robert Rybaric
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Section I: The Basics FREE CHAPTER
2. Microsoft Power Platform and Microsoft Dynamics 365 Overview 3. Microsoft 365 and Microsoft Azure Overview 4. Section II: The Architecture
5. Understanding the Microsoft Power Platform Architecture 6. Power Platform Customization and Development Tools and Techniques 7. Application Lifecycle Management 8. Section III: The Implementation
9. Implementation Approach and Methodologies 10. Microsoft Power Platform Security 11. Microsoft Power Platform Extensibility 12. Microsoft Power Platform Integration 13. Microsoft Power Platform Data Migration 14. Best Practices for Solution Architecture 15. Other Books You May Enjoy
16. Index
Appendix

Backend integration patterns and solution approaches

In the following sections, you will learn about the most typical integration patterns used within Dataverse-based solutions. For every pattern, we will present the possible solution approaches while using the technological background information you have learned about in this and in the previous chapters of this book.

The remote procedure call pattern

The remote procedure call (RPC) pattern is the simplest integration pattern, where one application directly calls the interface of another application without using any middleware. This pattern is usually synchronous and consists of a request-response pair. The called application must provide a suitable API to be used from the calling application. This pattern can be seen in the following diagram:

Figure 9.12: Remote procedure call pattern

As you can see, the calling application is directly calling the API of the called application with a request, and the API directly...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime