• Complain

Freeman - Essential Docker for ASP.NET Core MVC

Here you can read online Freeman - Essential Docker for ASP.NET Core MVC full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. City: Berkeley;CA;New York;NY, year: 2017, publisher: Apress, genre: Computer. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:

Romance novel Science fiction Adventure Detective Science History Home and family Prose Art Politics Computer Non-fiction Religion Business Children Humor

Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.

Freeman Essential Docker for ASP.NET Core MVC
  • Book:
    Essential Docker for ASP.NET Core MVC
  • Author:
  • Publisher:
    Apress
  • Genre:
  • Year:
    2017
  • City:
    Berkeley;CA;New York;NY
  • Rating:
    5 / 5
  • Favourites:
    Add to favourites
  • Your mark:
    • 100
    • 1
    • 2
    • 3
    • 4
    • 5

Essential Docker for ASP.NET Core MVC: summary, description and annotation

We offer to read an annotation, description, summary or preface (depends on what the author of the book "Essential Docker for ASP.NET Core MVC" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.

1. Understanding Docker -- 2. Docker Quick Reference -- 3. Getting Ready -- 4. Docker Images and Containers -- 5. Docker Volumes and Networks -- 6. Docker Compose -- 7. Docker Swarms -- 8. Containerized Development.;Find out how to use Docker in your ASP.NET Core MVC applications, and how containers make it easier to develop, deploy and manage those applications in production environments. Packed with examples and practical demonstrations, this book will help you deploy even large-scale, cross-platform web applications from development into production. Best-selling author Adam Freeman takes you on a whirlwind tour of Docker, from creating a consistent development environment for your team to deploying a project and scaling it up in production. By the end of the book, you will have a solid understanding of what Docker does, how it does it and why it is useful when developing and deploying ASP.NET Core MVC applications. What You Will LearnGain a solid understanding of Docker: what it is, and why you should be using it for your ASP.NET Core MVC applicationsUse Docker to create a development platform for ASP.NET Core MVC so that applications behave consistently across development and productionUse Docker to test, deploy and manage ASP.NET Core MVC containersUse Docker Swarms to scale up applications to cope with large workloadsWho This Book Is ForASP.NET Core MVC developers who want to use Docker to containerize and manage their applications.

Essential Docker for ASP.NET Core MVC — read online for free the complete book (whole text) full work

Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "Essential Docker for ASP.NET Core MVC" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.

Light

Font size:

Reset

Interval:

Bookmark:

Make
Adam Freeman 2017
Adam Freeman Essential Docker for ASP.NET Core MVC 10.1007/978-1-4842-2778-7_1
1. Understanding Docker
Adam Freeman 1
(1)
London, UK
Docker is a set of tools for creating and running application in containers, which isolates the application from all the other software running on a server. Even though the server may be running dozensor even hundredsof containers, each application is shielded from all the other instances and operates as though it is the only application running.
This book explains how you can use Docker for ASP.NET Core MVC applications and how containers make it easier to develop, deploy, and manage those applications in production environments.
What Do You Need to Know?
To get the most from this book, you should be familiar with .NET Core and ASP.NET Core MVC development, including how to create, compile, and run projects in Visual Studio or Visual Studio Code. You should also have a basic familiarity with Windows, Linux, or macOS and be able to run commands using a command prompt.
What Is the Structure of This Book?
This book is split into eight chapters. Chapter also includes instructions for creating a simple ASP.NET Core MVC project that is used as an example throughout the rest of the book.
Chapters , comes full circle and explains how the features from the rest of the book can be applied to the development environment instead of production.
Is This an Exhaustive Docker Reference?
No. This book covers the essential Docker features for working with ASP.NET Core MVC applications. I have left out Docker features that have no bearing on MVC applications or that are unlikely to be used by the majority of projects.
Are There Lots of Examples?
There are loads of examples, and every chapter shows you how Docker works by demonstrating, not describing, the features. At the end of this book, you will have a solid understanding of what Docker does, how it does it, and why it is useful when developing and deploying ASP.NET Core MVC applications.
You can download the examples for all the chapters in this book from apress.com . The download is available without charge and includes the example ASP.NET Core MVC project and the configuration files so that you dont have to create them yourself. You dont have to download the code, but cutting and pasting the code into your own projects is the easiest way of experimenting with the examples.
This Book and the Docker Release Schedule
Docker is actively developed, and new releases appear often. For the most part, new releases fix bugs and add new features, but Docker is a fast-moving target, and sometimes there are breaking changes.
It doesnt seem fair or reasonable to ask you to buy a new edition of this book every few months, especially since the majority of Docker features are unlikely to change. Instead, I will post updates following the major releases to the GitHub repository for this book, for which there is a link on apress.com .
This is an experiment for me (and for Apress), and I dont yet know what form those updates may takenot least because I dont know what the future Docker will containbut the goal is to extend the life of this book by supplementing the examples it contains.
I am not making any promises about what the updates will be like, what form they will take, or how long I produce them before folding them into a new edition of this book. Please keep an open mind and check the repository for this book when new Docker versions are released. If you have ideas about how the updates could be improved as the experiment unfolds, then e-mail me at adam@adam-freeman.com and let me know.
Which Operating Systems Are Supported?
All of the examples in this book have been tested with all three operating systems: Windows, macOS, and Linux. The exception is Chapter because the Docker clustering features that it describes are supported by Docker on Linux server only.
Why Should You Care About Docker?
Docker helps to solve two important problems that affect any complex project but that are especially prevalent in ASP.NET Core projects: the consistency problem and the responsiveness problem.
What Is the Consistency Problem?
Most ASP.NET Core MVC applications are made up of multiple components. There will be at least one server running the MVC application and usually a database to persistently store data.
Complex applications may require additional components: more application servers to share the work, load balancers to distribute HTTP requests among the application servers, and data caches to improve performance. As the number of components increases, additional servers are needed, as are networks to link everything together, name servers to aid discovery, and storage arrays to provide data resilience.
Few projects can afford to provide each developer with a complete replica of the production systems. As a consequence, developers create an approximation of the production systems, typically running all the components required by an application on a single development workstation and ignoring key infrastructure such as networks and load balancers.
Working with an approximation of the production system can lead to several different difficulties, all of which arise because the platform that the developer is using is not consistent with the production systems into which the application is deployed.
The first difficulty is that differences in the environment can cause the application to behave unexpectedly when it is deployed. A project developed on Windows but deployed onto Linux servers, for example, is susceptible to differences in file systems, storage locations, and countless other features.
The second difficulty is that the approximations developers use to represent the production environment can drift apart. Dependencies on different versions of development tools, NuGet packages, and even versions of the .NET Core and ASP.NET Core runtimes can occur, leading to code that makes assumptions that are not valid in production or on other developers workstations, which have their own approximation of production.
The third difficulty is performing the actual deployment. The differences between development and production systems require two configurations, one of which is difficult to test until the moment of deployment. I have lost track of the amount of time that I have spent over the years trying to deploy applications only to find that a single character is missing from a configuration setting or that there is a hard-coded assumption that the database can be accessed via localhost .
The fourth difficulty is that it can be difficult to ensure that all the servers for an application are configured consistently. A misconfigured server may cause only periodic problems, especially if a users HTTP requests are distributed to a large group of servers, and identifying the problem and isolating the cause can be a difficult task, made fraught by having to perform diagnostics on a live production system.
How Does Docker Solve the Consistency Problem?
When you put an ASP.NET Core MVC application in a containera process known as containerization you create an image, which is a template for containers that includes the complete environment in which the application will exist. Everything that will be used to run the application is part of the image: the .NET Core runtime, the ASP.NET Core packages, third-party tools, configuration files, and the custom classes and Razor views that provide the application functionality.
Next page
Light

Font size:

Reset

Interval:

Bookmark:

Make

Similar books «Essential Docker for ASP.NET Core MVC»

Look at similar books to Essential Docker for ASP.NET Core MVC. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.


Reviews about «Essential Docker for ASP.NET Core MVC»

Discussion, reviews of the book Essential Docker for ASP.NET Core MVC and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.