Issue #19 | Mar 25, 2016
This post will try to clarify a few things about why microservices may help you and some guidelines about building them.
In this post author explore how WildFly Swarm can be used for building microservices and how to integrate Netflix Hystrix and Turbine in order to build resilience into WildFly Swarm microservices.
How microservices made up of small applications can be more effective than big behemoth IT systems.
A Completely Biased Summary of the Assets of Microservice Architectures.
At the MicroXchg conference in Berlin, Bora Tunca from SoundCloud presented the evolution of SoundCloud’s microservices architecture throughout the years.
This is a talk about System-Z, the microservice-based microservices modelling system used at Spotify to help them understand their set of services.
Secrets, including private SSH keys, are almost always needed during a build. Let’s see how Habitus solves this for us.
Alak Deb explains shortcomings of Microservices architecture.
With the release of Wildfly Swarm, Java EE apps can be deployed alongside a stripped down version of Wildfly. Swarm is still in beta at the moment, and the documentation is missing a few steps that are required to get a "Hello World" application up and running, which is explained in this article.
Feathers 2.0 helps developers transition from monolithic application development to microservices.
An explanation of microservice architectures compared to monolith architectures, and a list of best practices and stacks that they’re well-suited for.
Most microservices interact in one of two ways: Via HTTP communication or via message queues. With deepstream, we’d like to suggest a third: Distributed state.
In this part author will finally finish writing demo application. Author will implement the last two services: Worker and frontend.
This is the second in a series of blogs on microservices, based on rallydev experience with building services for the CA Agile Central product.
Find critical and often overlooked aspects of a solution to a problem.
This book envelops the whole microservices development and deployment lifecycle using some of the latest and greatest practices and tools. We’ll use Docker, Kubernetes, Ansible, Ubuntu, Docker Swarm and Docker Compose, Consul, etcd, Registrator, confd, and so on.
Nike presenters will talk about adopting the Netflix operations support systems (OSS) stack for their deployment pipeline and application architecture, covering the problems this solved and the challenges this introduced.
his talk introduces CQRS and Event Sourcing and shows how applications leveraging CQRS and Event Sourcing can be implemented with the Spring Ecosystem. The talk will have slides and live demos.
Want to implement message-based architectures, such as microservices, using completely free products? This course will teach you about how to scale applications with these architectures using free products (RabbitMQ and MassTransit).
The goal of Micro is to provide a toolkit for microservice development and management. At the core, micro is simple and accessible enough that anyone can easily get started writing microservices. As you scale to hundreds of services, micro will provide the fundamental tools required to manage a microservice environment.
After last week’s release of the first two chapters of his new book, The Tao of Microservices, nearForm co-founder and CTO Richard Rodger is holding a follow-on webinar.
Wednesday, April 6, 2016 – 10 South Place, London, EC2M 2RB
转载本站任何文章请注明：转载至神刀安全网，谢谢神刀安全网 » Microservices Weekly | Issue #19: Ants vs elephants