Forget monoliths vs. microservices: cognitive load is what matters ...
▻https://diasp.eu/p/9241595
Forget monoliths vs. microservices: cognitive load is what matters
HN Discussion: ▻https://news.ycombinator.com/item?id=20235018 Posted by fancyfish (karma: 237) Post stats: Points: 273 - Comments: 56 - 2019-06-20T17:19:18Z
#HackerNews #cognitive #forget #load #matters #microservices #monoliths #what HackerNewsBot debug: Calculated post rank: 200 - Loop: 386 - Rank min: 100 - Author rank: 53
Fescar: A Distributed Transaction Solution Open Sourced by Alibaba
▻https://hackernoon.com/fescar-a-distributed-transaction-solution-open-sourced-by-alibaba-f70c9b
To support microservice-based development, Alibaba has now launched Fescar, an open source version of its Global Transaction Service solution to the problem of distributed transactions.This article is part of the Alibaba Open Source series.In online systems, #microservices have gained recent support from developers as a means of reducing difficulties, enhancing scalability, and facilitating agile development by splitting complex applications into loosely coupled services. However, implementing a seemingly simple function in a micro-serviced system may require calling multiple services and operating multiple databases, introducing a formidable distributed transaction problem for service calls.Currently, distributed transactions are the greatest obstacle to realizing microservices, and (...)
#distributed-systems #programming #open-source #software-development
Independently Scalable Multi-Container #microservices Architecture on #aws #fargate (II)
▻https://hackernoon.com/microservices-on-fargate-part2-f29c6d4d708f?source=rss----3a8144eabfe3--
In this article we will be building the stack of resources needed to run the application we prepared and containerized in the first part:Independently Scalable Multi-Container Microservices Architecture on AWS Fargate (I)The application source and CloudFormation stack file can be found here:docwhite/ecsfsOverviewThe ideas and requirements for this application, ecsfs, are:Backend and frontend services not to be public-facing.Nginx will sit on the front, publicly accessible.Nginx would proxy the request to the frontend.The frontend requests from the backend.Auto-scalable backend (since it performs expensive computations).In order to address (1) and (2) we will require private and public subnets. To forward all traffic to the nginx server (2) we will set up an Application Load Balancer (...)
Independently Scalable Multi-Container #microservices Architecture on #aws #fargate (I)
▻https://hackernoon.com/microservices-on-fargate-part1-f26a318827a8?source=rss----3a8144eabfe3--
Various cafés and boutiques stacked up at The Cafe Apartments in Vietnam.A guide on deploying a full stack (nginx, frontend, backend) application on AWS using #docker, Fargate and CloudFormation.Few weeks ago I started my journey through AWS. Now I got to a point where I feel confident to share my journey and some ideas that might help others.The reason I am writing this article is because I saw many examples of backend-frontend-nginx stacks in Fargate but not in a way that you could scale each component independently.On all those examples if you wanted more backend availability you would need to scale frontend and nginx with it because all containers were defined together and would run as one big service. It was not what I was after.This guide is structured as follows:Part 1: why (...)
Baselining #blockchain: The Promise of Architectural Aristocracy
▻https://hackernoon.com/baselining-blockchain-the-promise-of-architectural-aristocracy-75a15777f
A monolith versus #microservices comparison on how “all that glitters is not gold”The tale of the tape — block by block (Getty Images)PrefaceEnterprise Architecture (EA) is serious business designed to analyse, design, plan and in turn implement the findings to successfully execute on business strategies. It is about defining a symbiotic relationship in how information, business and #technology will flow together.It’s a must for any business serious about keeping up with the changing tides of technology. These tides owing to paradigm shifts in our exciting technological landscape as we dig deep to find efficiencies in anything and everything. The ownership then resting on the broad and bold shoulders of our technology integrator’s to build applications fast and reliably, but how?The case for (...)
Is Shared #database in #microservices actually anti-pattern?
▻https://hackernoon.com/is-shared-database-in-microservices-actually-anti-pattern-8cc2536adfe4?s
I used to work with several projects leveraging idea of microservices. What always was a problem (besides deployment, but having enough DevOps resources it is pretty much solvable) is separation of concerns.If you look at books, blog posts and tweets about microservices architecture (there are already millions of them), you’ll see that everyone declares nearly the same idea — microservices must be independent. That completely makes sense. But in words.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 (...)
#messaging Pattern For High Availability and Handling Failures in #microservices
▻https://hackernoon.com/messaging-pattern-for-high-availability-and-handling-failures-in-microse
We at Propelld ( A Fintech Startup ) are using microservices architecture for our business requirements. It was because we needed to be quicker in our deployment cycles (You may already know Business People ?). It is helpful for developers from a different background for easily contributing to architecture providing flexibility in choosing the language for the feature they build.But microservices do come with challenges like Failures, Fault Tolerance, monitoring, and logging etc.Microservices TrendHow it all started?I was given the task to implement Email Service that requires email to be sent at various steps in the process. The challenges with Email Service was to maintain High Availability and Prevent Fails. My mentor threw some concepts like message-driven and event-driven approaches (...)
Service Mesh: Moving from bare-bones Envoy to #istio
▻https://hackernoon.com/service-mesh-moving-from-bare-bones-envoy-to-istio-e0fef88fc1e3?source=r
Migrating from bare-bones Envoy to IstioThis post is part of the “Service Mesh” series. If you haven’t read the previous posts, I would urge you to do so, it will help understand this article better. Here are the previous articlesService Mesh with Envoy 101Microservices monitoring with Envoy Service Mesh, Prometheus & GrafanaDistributed Tracing with Envoy Service Mesh & JaegerIn the previous articles we looked at installing Envoy as a side car proxy to our services and saw how the Service Mesh setup helped in managing traffic between the services and to collect and visualise tons of telemetry data about the traffic.There were a few annoying things in the setup thoughInstalling the Envoy side car manuallyRouting traffic to the side car proxy manuallyManaging the configurations for all the (...)
Understanding Micro Frontends
▻https://hackernoon.com/understanding-micro-frontends-b1c11585a297?source=rss----3a8144eabfe3---
As a #frontend developer, all these years you were developing monoliths, even though you already knew it was a bad practice. You divided your code into components, used require or import and defined npm packages in your package.json or mounted sub git repositories into your project, yet you ended up building a monolith. It’s time to change it.Why is your code is a monolith?All frontend applications are a monolithic application in nature, except apps that already implemented micro frontends. The reason is if you are developing with the React library and if you have two teams both should be using the same React library and both teams should be in sync on deployments and always will be conflicting during code merges. They are not separated completely and most probably they are maintaining (...)
#javascript #microservices #agile-development #micro-frontends
How to develop Go #grpc #microservices and deploy in Kubernates
▻https://hackernoon.com/how-to-develop-go-grpc-microservices-and-deploy-in-kubernates-5eace0425b
How to develop Go gRPC microservices and deploy in KubernetesA few month back, I started my journey learning gRPC. This article is to demonstrate how we can use gRPC to develop microservices using Go and deploy them in #kubernetes cluster. We will develop two microservice. One microservice will be responsible for calculating summation of two integer and other will serve a public REST API.PrerequisitesThere are many many way to run kubernetes cluster in local machine. I am going to use Minikube for this article. We also need to install kubectl, Docker and #protobuf Compiler.To start Minikube you have to run following command with root privileges$ minikube start [—vm-driver=<driver>]Define communication protocolAs an underlying transport protocol we will use gRPC. For that we need (...)
►https://www.sayonetech.com/blog/microservices-architecture-the-new-business-enablers
These days, microservices or microservices architecture is a familiar term in the software development arena. As traditional software architectures became more complex and problematic over the years, recent entrants such as the microservices architecture are gaining momentum among enterprises and businesses.
But, is it just the hype or above that? Well, let’s take a closer look at how microservices are evolving to be the new business enablers.
Building Fault-Tolerant #microservices using #netflix’s Hystrix
▻https://hackernoon.com/building-fault-tolerant-microservices-using-netflixs-hystrix-c36083ca9af
Microservices are a collection of independent, autonomous services compared to the monolithic application where all the modules are tightly fitted into one application.In Microservices architecture it is very essential to develop fault-tolerant microservices. We must develop the microservices in such a way that the fault impact must be minimized and should be based on the fast-fail mechanism to have minimum impact.Here is an example of e-commerce application built on the microservices architecture.E-commerce application Microservice architectureThe above architecture was working well until one day the e-commerce application stopped working. It was found that the service which fetches the list of available items was not responding. On further analysis, it was found that it used Third (...)
Don’t use #microservices
▻https://hackernoon.com/dont-use-microservices-c3b5484b329a?source=rss----3a8144eabfe3---4
Why You Shouldn’t Use MicroservicesYep, I said it — DON’T USE MICROSERVICES. And I mean it. Don’t use that pattern. To make it clear from the beginning, I am not against it, but like with any other decision do proper analysis before.Every damn pattern has pro and cons and those must match to your particular context.And in most cases, you are not in the right context for microservices.Microservices are an extreme form of classic distributed systems. In distributed systems, a couple of applications work together to fulfill a business outcome. Traditionally the number of systems aka applications involved was pretty small. Every network connection aka app2app communication is a breaking point. It can break or cause otherwise trouble anytime. Network down, network slow, packet loss, apps slow (...)
#dont-use-microservices #software-microservices #avoid-microservices #software-development
Why You Should NOT Switch to #microservices
▻https://hackernoon.com/why-you-should-not-switch-to-microservices-6f0bcd98ab68?source=rss----3a
Should your product be built as a monolith or consist of microservices from the start? When is the right time to adopt microservices? Why would you need to fall back?Microservices is the term that boomed lately and many businesses are considering moving to this software architecture. There are multiple opinions expressed on the benefits and necessity of moving from a monolith app to microservices or serverless computing. Using microservices can bring efficiency to workflows in finances, retail, consulting, banking, marketing, data analytics, and other industries.This Statista graph shows that microservices or serverless computing were already actively used in 11% of production deployments as of 2017, and 18% more of respondents named the adoption of this tech their top priority for (...)
#microservices Architecture: The New Business Enablers
▻https://hackernoon.com/microservices-architecture-the-new-business-enablers-3b237807c103?source
These days, microservices or microservices architecture is a familiar term in the software development arena. As traditional software architectures became more complex and problematic over the years, recent entrants such as the microservices architecture are gaining momentum among enterprises and businesses.But, is it just the hype or above that? Well, let’s take a closer look at how microservices are evolving to be the new business enablers.What are Microservices?The microservices architecture decomposes or divides the entire application into a set of manageable services. It basically follows the phenomenon of ‘do one thing really well’. According to Martin Fowler, the software guru, a microservice architecture consists of “suites of independently deployable services” organized “around (...)
#microservices-business #application-architecture #microservices-enables #microservice-architecture
How Cloud Services Can Aid in Agile Product Development
▻https://hackernoon.com/how-cloud-services-can-aid-in-agile-product-development-82d14d0d52f8?sou
Introduction to AgileAgile methodology is a form of software development methodology where the entire focus is on providing client satisfaction through the process of continuous delivery. There was a time when the waterfall methodology was the golden standard for software development, but this process had its cons and when agile was introduced, it became widely appreciated over time.Agile processes were based on sustainable development, where stakeholders, developers, and customers were equally benefited, and were able to work at a constant pace. The frequent collaboration with stakeholders, closely working team members, and the possibility to embrace change late in the project has made Agile popular among teams. Going through the Agile Manifesto would give you an idea of the set of (...)
#product-development #agile-development #cloud-services #serverless #microservices
4 Critical Capabilities of Headless CMS #api You Need to Integrate with External Systems
▻https://hackernoon.com/4-critical-capabilities-of-headless-cms-api-you-need-to-integrate-with-e
Integrating a new content management system (CMS) into your existing ecosystem of tools and services may be challenging, but not with a headless CMS with a quality API. Read on to learn how headless CMS API can help you prepare for the future.There is no doubt that in order to connect content-as-a-service with its headless API-first approach to other best-of-breed #microservices you have to have a good quality API on both ends, so that the services communicate and integrate well.But what does a good quality API really mean? Of course, there are many different angles you can consider (e.g. it has to be testable, well documented, with solid error reporting, secure…). In this article I am focusing on the quality of a headless CMS API, and more specifically the required API capabilities (...)
An Approach To Automating Application Resiliency #testing With #kubernetes
▻https://hackernoon.com/an-approach-to-automating-application-resiliency-testing-with-kubernetes
Table of contentIf you’ve never failed, you’ve never livedReliability and ResiliencySo let it break… but plan for it!Why Kubernetes?Organize the resistance with ToxiProxyResiProxy: a Kubernetes companionHappy vs Alternate pathKeep calm and under control with KarateConclusionIf you’ve never failed, you’ve never livedWithout too much pessimism applied to micro-services, this common saying is also sensible: failures are an intrinsic characteristic of any distributed system. Hundreds of independent entities trying to communicate and collaborate to achieve a greater good… at least one of them is sure to fail.Trying to avoid all of these failures is wishful thinking and can sometimes lead to an extra complexity that can directly impact an architecture, its cost, and in particular limit its capacity to (...)
How Toyota Guides The Evolution Of Our Infrastructure (And Makes Me Appreciate Jira)
▻https://hackernoon.com/how-toyota-guides-the-evolution-of-our-infrastructure-and-makes-me-appre
Reflecting on my company’s journey to #microservices, #devops, and the Perfect Value StreamIn the Manufacturing industry, the Value Stream Map (VSM) is a popular tool used to measure performance. The VSM was made famous by Toyota, and is essentially a flow chart that describes the necessary steps to produce value.For example, consider this simple VSM for a Chair Factory.An example VSM for a Chair Factory.This example illustrates the 4 steps our factory needs to produce a chair after receiving an Order: Welding, Painting, Assembling, and Inspection.There are a couple of things worth pointing out here.The steps must be done sequentially. In this example, Painting must come after Welding for each chair.The steps can be done in parallel for different work items. In this example, that means (...)
The #microservices Approach to Mobile Application Development (Part II)
▻https://hackernoon.com/microservices-architecture-for-mobile-application-development-part-ii-1a
Read Part 1 here!In part I we discussed how we may decompose a large complex React Native app into smaller React Native mini apps (using Electrode Native), and how mini apps can be combined together to build larger apps. Mini apps allow development using separate code repositories for each mini app, and mini apps can be centered around a particular business feature. This also allows separate teams to work on each mini app.We also discussed on-device data storage options when using React Native, and Realm database emerged as a viable contender.We sourced various articles and forums to examine and abstract some common performance issues encountered when using React Native and explored possible solutions that will mitigate this.In part II we will explore some deeper implementation issues in (...)
#push-notification #mobile-app-development #react-native #microservice-architecture
The Microservice Weekly #139
▻https://hackernoon.com/the-microservice-weekly-139-d39e91538ab8?source=rss----3a8144eabfe3---4
Highly Available #microservices with Health Checks and Circuit BreakersIn this article, you’ll read how algorithms for load balancing help to deliver highly available services. Then, you can read an example of how Kong makes it easier to deliver high availability with built-in health checks and circuit breakers.2 Days of Microservices Training in EdinburghDuring the course of these two days, we will cover a high-level architectural overview of what is needed to design, develop and maintain an application built with microservices.Microservices with #kubernetes, Docker, Helm (Part 1) — Generic configuration and API GatewayRead how to set up a Microservices architecture from scratch using Kubernetes, Helm, and Docker. You’ll learn how to automate the deployment process using a CI/CD tool.Monolith (...)
Building general purpose #blockchain
▻https://hackernoon.com/building-general-purpose-blockchain-71ffb8511ce?source=rss----3a8144eabf
towards blockchain solution for any micro service ecosystemsAs I have spent some time playing and working with blockchain solutions, at some point I decided to try and build general purpose blockchain system myself. So, to go beyond “your first blockchain” tutorial. I wanted to do it as an experiment, for purely academic purposes and see what comes out of it. Here is the idea behind it and general overview of what came out of my time spent on analyzing, designing and building product like this…The idea is to understand what is needed to create blockchain that can be supplementary component for your backend — a service that plays nicely with your multi / micro service backend setup and provides blockchain functionality.If built properly this can be generally useful to anyone wanting to remove (...)
#blockchain-technology #purpose-blockchain #microservices #open-source
Should you use a #monolith, #containers or #serverless ?
▻https://hackernoon.com/should-you-use-a-monolith-containers-or-serverless-a5e23a44e73f?source=r
Monolith. Credit: ▻https://pixabay.com/en/stonehenge-architecture-history-1590047/It’s been a long time since my last Article in January. I apologise for the delay, it’s difficult to find time to just sit down and translate my thoughts into insightful, digestible content. I have so much I want to write about but sometimes there’s so much that I don’t exactly know where to start.IntroductionThe purpose of this post is intended to help you decide whether you should use monoliths, containers or serverless architectures. Each have their own merits and faults and we’ll discuss each of them in detail throughout the article. The decision should ultimately be made based on the stage of the project you are at and your familiarity with these architectures. A clean architecture will always be better (...)
#scaling #microservices via Fork-ing
▻https://hackernoon.com/scaling-microservices-via-fork-ing-37f8f9b3266c?source=rss----3a8144eabf
Building Natively Scalable MicroservicesImage from LONGLONGLIFE.orgIntroductionAlmost anyone familiar with microservices architecture, has heard about scaling. Scaling is the process which enables load balancing by running multiple instances of a service (container).In any of the existing orchestration platforms, scaling can be done either automatically or manually. But, both approaches require some sort of administration deciding when a microservice needs to scale. This article introduces an autonomous scaling method driven by OS system calls without the need for external interference .MotivationAutonomy is one of the main principles of microservices architecture, and is essential for building agile ecosystems. In an agile ecosystem, along with agility in #development, microservices (...)
Micro Services & #git
▻https://hackernoon.com/micro-services-git-d840305e6220?source=rss----3a8144eabfe3---4
Mono/Multi Repo, Balancing Feature Branches and Continuous IntegrationIf you are confused between mono repository or multi-repository or a branch and merge strategy for micro-services - feature branches, trunk based development or release branches, then this post will have something for you. There is no one right way, but as with life, to choose a better way ,you need to be first self aware. Similarly to choose a source control strategy for your project, you need to be aware of the analysis process, development process, balance of parallel feature development with CI and CD,code review and merge process and component ownership patterns in your teams.Git is by default the version control system used by most modern software projects. I have seen that the perspective is different if you (...)
#continuous-integration #microservices #mono-multi-repo #micro-services-and-git