🚀 David Boyne’s Post

Private Service Connect lets a service producer offer services privately to a service consumer. Private Service Connect offers the following benefits: A service producer VPC network can support more than one service consumer. Each consumer connects to an internal IP address that they define. Private Service Connect performs network address translation (NAT) to route the request to the service producer. Private Service Connect uses endpoints and service attachments to let service consumers send traffic from the consumer's VPC network to services in the service producer's VPC network as the following architecture.

Been modelling how to create a highly available application architecture made up of secure network, public ALB, autoscaling groups and launch templates. It was quite straightforward to build and felt very composible! I was able to create the model AND the infrastructure at the same time. I could even make this in small steps All the orange frames are the networking stack, the white frame is the application artifacts (autoscaling group, instance profile, launch template) and the yellow frame is the load balancer, the listener and the target group! There's going to be so much more of this coming as examples of how to use System Initiative. If you want to see more, get in contact with me and I can take you on a tour of it!

Want to build a reliable messaging system? You need to know the Outbox pattern. Here's a high-level overview of the system architecture with the Outbox introduced. - We introduce an Outbox table in the database - Instead of publishing a message, you store it in the Outbox - This operation is atomic, ensuring our system remains consistent - A worker process polls the Outbox for messages and publishes them Curious to learn more? Start here: https://lnkd.in/eEHycBz5

[ tweet handle: https://lnkd.in/dv7huSWt ] << ...Great point by Sven Müller in his “Software architecture trends and how to avoid them” at #BedCon: Separation of Concerns architectures (Hex, Onion) are great if the domain is stable. If it’s rather volatile, you end up adapting adapters, ports et al. for a lot of changes... >>

The two most common questions I get about #UNS or #UnifiedNamespace ? 1. Where does the UNS live? 2. Can I limit access to some areas of the namespace and not others? In the video below -- I answer both questions and a couple others. The simple fact is -- UNS is omniscient and omnipresent -- it knows everything (or at least it SHOULD) and it is everywhere (like a fabric). Infrastructure is how we plug into UNS, RBMS and ACL are how we limit what we can see. A couple of important notes -- 1. What is UNS, from the node's persepective, is a function of where a node plugs in and what it can access 2. UNS is an architecture Word to the wise -- there are ALOT of people using the term UNS incorrectly. There are ALOT of people who are being confused by these incorrect usages. UNS is architecture, it is structure, it is events, it is data, it is information, it is function, it is description... and it is current state in real time. All built on a common technology that is edge driven, report by exception, lightweight and open architecture. It really is that simple. #iiot #digitaltransformation

Industry 4.0....are you lost in the rabbit hole of buzzwords, acronyms and terminology? No doubt you've came across the term UNS (Unified NameSpace). Walker Reynolds breaks UNS down into a straight forward to the point explanation in this video!!

We've partnered with James Higginbotham to create a series of articles covering the fundamentals and best practices when building event-driven applications and architectures (EDAs). In the first article, Event-Driven Architecture Fundamentals and Common Pitfalls (and How to Avoid Them), James summarizes the fundamentals of event-driven architecture, including: 1. Message types: command, reply, and event 2. What constitutes a message, including body, headers, and network protocol 3. Message interaction patterns such as request-reply, fire-and-follow-up, and fire-and-forget 4. Event design patterns: event notifications, event-carried state transfer, using hypermedia links in events, and event batching. Throughout, he highlights common pitfalls and the best practices to avoid them. https://lnkd.in/e3ZNR5Yv

Many software developers have requested a feature that allows them to create their own virtual folders and modules. In the new version of inno.navi v1.5 we have added this feature, as you can see in this short video below. 😊 By moving the elements and creating new elements, you can now visualize 100% any individual software architecture. 👍

Setting up an environment that monitors ECU performance during development helps ensure that issues related to timing are found and addressed much earlier. As a reminder, most of these issues are currently found during integration, making them much more challenging to resolve. INCHRON’s ECU Performance Monitoring starts by reviewing your ECU’s architecture and its requirements. Then, regular analysis of trace data is implemented to ensure the requirements are fulfilled. If issues are found, our team of experts is on hand to provide support and options for resolution. If regular analysis of your ECU’s performance would help, drop me a line to learn more.

𝗪𝗵𝗮𝘁 𝗶𝘀 𝘃𝗲𝗿𝘁𝗶𝗰𝗮𝗹 𝘀𝗹𝗶𝗰𝗲 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲, 𝗮𝗻𝗱 𝗵𝗼𝘄 𝗱𝗼𝗲𝘀 𝗶𝘁 𝘄𝗼𝗿𝗸? For many software systems, layered architectures are the foundation, organizing the system around technical layers. However, this organization often results in low cohesion between these layers, making system enhancements and maintenance challenging. Instead of organizing by technical constraints, what if we organized the system by the features themselves? This would maximize coupling in a single feature and minimize coupling between unrelated features. This is the essence of vertical slice architecture. Tomorrow, our subscribers will learn all about vertical slice architecture. 📩 Join us to get the issue (it’s free): https://lnkd.in/gJGtmrBc