tryexceptpass

Blog | Podcast | Categories | Tags | Authors

Episode 13 - Practicality of the Microservices Obsession

15 mins

2020-05-25 engineering

Based On

Practicality Beats Purity - Microservices vs Monoliths
by Cristian Medina

As an expanding industry trend, architecting solutions with microservices is yet another swing of the proverbial hammer that intends to solve every possible software problem. But just like everything else in the real world, the reality of implementing this type of solution involves costs and trade-offs that you should be aware of. We explore them in this episode. What are the benefits? Modularity. Scalability. High availability. Deployments with no downtime. Continue reading

practicality microservices

Episode 8 - Microservices Cheat-Sheet: Answers to 8 Common Questions

13 mins

2020-04-20 engineering

Based On

35 Microservices Interview Questions You Most Likely Can't Answer
by Alex from FullStack.Cafe

The majority of enterprises are either running in a microservices environment or studying how to do so. The concept has been around for a while, but used a lot like an industry term that means different things to different people. We’ll try to define the concept and some of the terminology used along with it.

practicality microservices ci cd deployments

Conveying Build and Test Information with Repository Badges

2019-09-08 python engineering Dustin Mendoza

When you check out a repository on github, sometimes theres a little bit of flare at the top of the project that catches your eye. This bit of flare is called a badge and can be used to indicate build status, test coverage, documentation generation status, version support, software compatibilty statements or even community links to gitter or discord where you can find more help with the project. I used to think that badges were fancy fluff people added to their projects to make them seem more professional. Continue reading

python ci cd builds microservices

Practicality Beats Purity - Microservices vs Monoliths

2018-05-10 engineering Cristian Medina

In recent years there’s a growing trend to move away from large all-in-one applications. These “monoliths”, developed with one codebase and delivered as one large system, are hard to maintain. In their place, the industry now favors splitting-off the component systems into individual services. As separate “microservices”, they perform the smallest functions possible grouped into logical units. They are independent deliverables, deployable, replaceable and upgradeable on their own.

Going further into the Practicality Beats Purity series, this article will cover the implications of transitioning to a microservices architecture.

practicality microservices