DevTestSecOps
138 subscribers
469 photos
29 videos
37 files
695 links
Forwards and notes on development, testing, security, and operations from @q587p.

About me: studied as System Architect, worked as a SysAdmin, working now as an Test Automation Engineer. Also, I'm interested in hacking (and everything related to it).

జ్
Download Telegram
#programming #microservices

https://twitter.com/ScottWlaschin/status/1247572618343059456

For the record, at Uber, we're moving many of our microservices to what
@copyconstruct calls macroservices (wells-sized services).

Exactly b/c testing and maintaining thousands of
microservices is not only hard - it can cause more trouble long-term than it solves the short-term.
#video

#Microservices promise a scalable #architecture, increased flexibility, and better performance. But then you find out what’s actually involved in designing and running a microservices-based architecture. Turns out it’s not that straightforward after all.

Often the discussion around
microservices is framed by a false dichotomy between the messy monolith and the lean and mean microservices architecture. Fortunately, there’s a third way: the modularized application. Functional decomposition doesn’t imply that every component has to become its own independent process.

Modularization is about strong encapsulation, well-defined interfaces, and explicit dependencies. Many languages offer in-process modularization features (for example, Java with its all-new module system). In this session we explore the right (and wrong) reasons for going with a
microservices architecture, as well as what a modularized application entails. There’s a place for both independently deployed microservices and larger applications with a strong internal modular structure. Choose wisely.

https://youtu.be/AJW2FAJGgVw
#video #programming #dotNET #microservices

11 hours! 😱

In this step-by-step tutorial I take you through an introduction on building microservices using .NET. As the name suggests we build everything completely from start to finish –with the full scope of the course outlined in the time-stamp section below. However, at a high-level we’ll cover:

• Building two .NET
Microservices using the REST API pattern
• Working with dedicated persistence layers for both services
• Deploying our services to Kubernetes cluster
• Employing the API Gateway pattern to route to our services
• Building Synchronous messaging between services (HTTP & gRPC)
• Building Asynchronous messaging between services using an Event Bus (RabbitMQ)

https://youtu.be/DgVjEo3OGBI