|
|
|
|
Microservices architecture on paper sounds amazing but unless the business as a whole is not committed to it, then your department will end up with low morale, low productivity, and tones of code debt.
ADAM DALLIS
|
|
This practical guide covers the entire microservices landscape, including the principles, technologies, and methodologies of this unique, modular style of system building. You'll learn about the experiences of organizations around the globe that have successfully adopted microservices.
IRAKLI NADARESHVILI ET AL.
|
|
Our 2 day long, in-person trainings allow you to significantly improve your Microservices knowledge & get expert feedback during live coding sessions. Join us in Berlin (May 6-7) or Barcelona (April 8-9)
RISINGSTACK
|
|
In reality if you want to build exactlty microservices but not just monolith with couple of side services, you’ll have to think about splitting your business domain. And here you unlikely find any good advices. First of all, in many cases it’s just not completely solvable, second, after a meeting with the project manager your business domain will change, breaking all the existing architecture.
ROMAN KRIVTSOV
|
|
Istio is an Open Source project developed in partnership between teams from Google, IBM, and Lyft and it provides a solution to the complexities of microservice based application, to name a few:
* Traffic management: Timeouts, retries, load balancing,
* Security: End-user Authentication and Authorization,
* Observability: Tracing, monitoring, and logging.
RINOR MALOKU
|
|
Serving millions of requests per minute with a microservices environment is not an easy task. Every request is routed to many applications, and may potentially stall or fail at any step in the flow.
GUY KOBRINSKY
|
|
This post is going to look at the migration of a core product feature out of monolith into a self-contained micro-service. The author is focusing on the techniques that they used to ensure zero seconds of downtime on the feature as they rolled it out, as well as discussing the timeline, advantages, and disadvantages of the approach.
STEVE BUSSEY
|
|
This article is about developing large Electron.js applications using Microservice Architecture. The author worked on a large desktop application, which had a variety of CPU-consuming features inside, from an HTTP server to a version control system with gigabytes of daily backups. In other words, it was a high niche application. It acted like a server, but it was portable, with a convenient GUI.
YURY BUSHEV
|
|
Docker can be used on all types of projects, regardless of size and complexity. In the beginning, you can start with compose and Swarm. When the project grows, you can migrate to cloud services like Amazon Container Services or Kubernetes.
TARUN SHARMA
|
|
The pitch for the Lagom framework is that its programming model and architecture allow developers to write microservices that effectively scale across large deployments, that provide desirable application quality-of-life characteristics such as robust error tolerance and application responsiveness, and that take full advantage of the today’s massively-multicore computer hardware.
JONATHAN WEST
|
|
In this post, Eli Nudler writes about their journey of optimizing a platform which consists of more microservices than engineers, and where an average request from a client goes through 10 microservices before finally returning a response to the client.
ELI NUDLER
|
|
|
|
|
|
|
|