This document discusses using .NET Core and Docker for microservices. It begins with an overview of why Docker and microservices are useful. It then discusses why .NET Core and Microsoft technologies are good choices for building microservices. The document demonstrates creating a simple .NET Core app as a Docker container. It also discusses microservices patterns like having a database per service and isolating service instances. The document concludes with information about prerequisites for the demos and asking if there are any questions.
Microservices is a software architecture design pattern in which complex applications are composed of small, independent processes communicating with each other using language-agnostic APIs. These services are small, highly decoupled and focus on doing a small task.
The document discusses IBM's use of Node.js microservices. It describes how IBM initially built monolithic applications but moved to microservices to allow for independent deployment of services and improved scalability. Some key aspects of IBM's microservices architecture using Node.js include having many independent services, communicating via message queues like RabbitMQ, and clustering services locally for horizontal scaling. While microservices provided benefits, the document also notes challenges around legal compliance, operations overhead, and integrating distributed services.
Continuous Delivery can help large organizations become as lean, agile and innovative as startups. Through reliable, low-risk releases, Continuous Delivery makes it possible to continuously adapt software in line with user feedback, shifts in the market and changes to business strategy. Test, support, development and operations work together as one delivery team to automate and streamline the build, test and release process.
A quick overview of application networking and microservice resilience and how a service mesh like Istio.io can help alleviate some of this pain.
Developing integration microservices using CI/CD with apache camel, open shift, fabric8.io, jenkins, et al.
Session presented at DDD event in TVP/Microsoft UK HQ. Introduction to Azure Service Fabric, and focus on the actor model (formerly known as Project Orleans), with demos and documentation on how it is supported in Service Fabric. Goal: ask ourselves why did we really replace OO with "stateless services".
This document summarizes new Azure features for June. It discusses updates to Docker, SQL Server, Java, Media Services, App Insights, Blockchain, Notification Hubs, Dev/Test Farms, Azure Search, DocumentDB, SQL Data Warehouse, and other services. It also provides recommended resources for service mappings, naming conventions, disaster recovery, and an upcoming Azure session at Microsoft Ignite.
Azure Service Fabric is now Generally Available! In this meetup we will start from the beginning and define what is microservice. Next we will have a deep dive in Azure Service Fabric. Azure Service Fabric is one of the most interesting Azure service. Used internally in Microsoft for 5 years and backing up one of the most demanding Azure services today such as Azure SQL, Document DB, Cortana and Skype for Business. We will be talking about the two models that are supported by Azure Service Fabric: - Reliable Services (We will explore the reasons for having both stateful and stateless offerings in this model) - Reliable Actors Then we will talk how you can create Azure Service Fabric cluster on premise or in another cloud. We will demo deployments in Azure for the various models. Azure Service Fabric is the most advanced and complete offering for developing and hosting microservices in Azure. It builds on years experience Microsoft acquired running one of the most demanding services such as Azure SQL. Moreover, Azure Service Fabric solves very difficult distributed computing problems such as data synchronization, zero downtime deployment, update and rollback operations at large scale. Join us to learn more about Azure Service Fabric and start using it immediately after the meetup!
Building microservices requires more than just infrastructure, but infrastructure does have a role. In this talk we look at microservices from an enterprise perspective and talk about DDD, Docker, Kubernetes and how established open-source projects in the integration space fits a microservices architecture
The document discusses Christian Posta's journey with microservices architectures. It begins by explaining why organizations are moving to microservices and defines microservices. It then covers related topics like cloud platforms, container technologies like Kubernetes and OpenShift, benefits and drawbacks of microservices, and tools for developing microservices like Docker, Kubernetes, OpenShift, and Camel.
This document summarizes how Kubernetes can be used on OpenStack. It discusses integrating Kubernetes with OpenStack services for networking (Neutron), identity and access management (Keystone), storage (Cinder and Swift), cluster setup/management, and container registry. For each area, it provides an overview of the current integration and potential future enhancements.
Making it easy to integrate legacy and iterative microservices with REST/CQRS and deploy to Docker/Kubernetes/OpenShift all on a developer laptop!