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
Building RESTful Web Services with .NET Core

You're reading from   Building RESTful Web Services with .NET Core Developing Distributed Web Services to improve scalability with .NET Core 2.0 and ASP.NET Core 2.0

Arrow left icon
Product type Paperback
Published in May 2018
Publisher Packt
ISBN-13 9781788291576
Length 334 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (3):
Arrow left icon
Gaurav Aroraa Gaurav Aroraa
Author Profile Icon Gaurav Aroraa
Gaurav Aroraa
Tadit Dash Tadit Dash
Author Profile Icon Tadit Dash
Tadit Dash
Sharbani Bhattacharya Sharbani Bhattacharya
Author Profile Icon Sharbani Bhattacharya
Sharbani Bhattacharya
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Getting Started 2. Building the Initial Framework – Laying the Foundation of the Application FREE CHAPTER 3. User Registration and Administration 4. Item Catalogue, Cart, and Checkout 5. Integrating External Components and Handling 6. Testing RESTful Web Services 7. Continuous Integration and Continuous Deployment 8. Securing RESTful Web Services 9. Scaling RESTful Services (Performance of Web Services) 10. Building a Web Client (Consuming Web Services) 11. Introduction to Microservices 12. Other Books You May Enjoy

Continuous Integration and Continuous Deployment

Most projects are a team effort. The team could be located in different places or in the same place, and members from different locations have to work in sync mode so their changes won't conflict with other team members. A system won't mature until it is used in various scenarios; these scenarios could be based on the experience of domain experts or come from the production environment. There is a chance that a system could crash in the production environment even if the system is regarded as a perfect system. In terms of web applications, the conditions are more critical due to performance glitches, bad user experiences, and so on. A system should go through a process where, if a team member makes changes, the code is integrated after unit tests and the build is then deployed in the related environment.

When we say deployment...

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 £16.99/month. Cancel anytime