Software Architecture lives in quality, the hidden part which delights the customer
Functional features are things we discuss all the time while developing software, but what about its reliability or performance?
Software Qualities can be the difference of a great user experience or a product that breaks under pressure, leaks information. These things are important lets see how.
With distributed software delivery teams, the key to scaling, is empowerment.
Many teams will need to create a lot of common software components, which will need to comply with regulations (Databases, Queues, etc)
Self-service is one solution to allow squads to create this components on demand, in a way that considers all the software qualities consistently
You platform is more than just using AWS or Azure, its your application and integration architecture realised.
A platform is key to enabling multiple engineering squads to focus/deliver the unique business value.
In order to scope correctly, we need to consider beyound the infrastrcuture, and include such topics as the patterns of Application and Integration Architecture.
No more, i have no idea why we use this, lets understand really why we made that decision.
Software solutions will be made of multiple decisions, as we progress we will need to understand when a decision is obsoleted.
We use Architecture Decision Records (ADR) to keep this context.
Agile architecture is not just software and technology its how we work too
A good architecture will take into account how multiple teams will work together to deliver a software solution.
This is a possible way to implement Platform Engineering / Team Topologies.
notes to setup Certs for a dev server (becuase i will forget this)
Lets say you are behind a firewall and want to set HTTPS on your Istio ingress using Self-Cert.
you can do this doing the following.
We will do this the Clicky-buntie way in Rancher.
this is common where the Istio will have some part of the route to identify which service, and will want to remove the identifier.
We look at how we can rewrite the URL routing to downstream services.
our services will be deployed in a number of seperate namespaces, this is how you can do the routing
we want to setup the Gateway in a central namespace, and place the virtual service close the the service it is setting up routes too.
OK this is a really simple post, but it was not obvously documented (it does not follow the DNS resolution like services follow)
simple extra config answer which is required
Rancher has integrated Istio into its management dashboards. During the setup there are several options which you can customise, one is the Ingress controller
By default (at the time of this article) you need to provide an extra answer to the set to enable TLS on the Istio Ingress.
we will look at the settings, and how to confirm the setup.
Ensuring messages are sent and handling errors is tricky
RabbitMQ offers a lot of excellent features, but one which is not supported out of the box is message retries.
In this post we look at a way to support message retries, with processing back-off while supporting deadletter queues.
