Hello Power Platform friends! In the next few posts I’d like to focus around a somewhat less technical or ‘how-to’ type topic, and we’ll look at solution and project architecture when working with the Power Platform! Within this series, I’ll give you a bit of a high level as to what the different parts of solution architecture look like from discovery on a project, right the way through to moving into support.
Stay tuned to learn all the things about solution architecture when working with low-code friends! We will also touch on elements around ecosystem and platform architecture but this series will primarily focus on the solution! In the future I’ll go more in depth on other architecture forms 👀
In this post, let’s take a step back to begin with and look at different types of architecture on the Power Platform! 🚀
What is ‘architecture’?
Architecture in the IT world refers to the design and structure of software systems, such as applications, databases, networks, and platforms. It defines how different components of a system interact with each other, what standards and protocols are used, and what are the goals and constraints of the system. Architecture in the IT world is important for ensuring the quality, performance, security, and scalability of software systems.
Some examples of architecture in the IT world are:
- Cloud architecture: the design of cloud-based systems that use remote servers and networks to store, process, and deliver data and services.
- Microservices architecture: the design of software systems that consist of small, independent, and loosely coupled services that communicate through APIs.
- AI architecture: the design of software systems that use artificial intelligence techniques, such as machine learning, natural language processing, computer vision, and speech recognition, to perform complex tasks.
So guess what people… with Lewis being obsessed with all things new AI… that was what Edge Copilot thought of architecture in the IT world 🌍 😄
Solution architecture
I’d probably add a few things given we’re talking about a low-code platform here. I’d agree on the best part with the points above around the broad topic of solution architecture, with that being focused on the end-to-end process of designing and delivering a solution built on the low-code platform, however I’d probably also add platform architecture specifically for when working with something like low-code.
Platform architecture
When I say platform architecture, I’m talking about the methodology we put into configuring, administering and protecting the platform with digital guardrails.
Ecosystem architecture
Finally I’d probably add a point around ecosystem architecture being around how we configure, and protect the links between the platform and its wider ecosystem, but also things more relevant to the enablement of people that use the platform or build on the platform, or even the processes we wrap around various elements of the platform, implementation of solutions, integrations with other services in the ecosystem (the cloud platform, the business utilising the thing, the ‘outer space’).
What’s coming up?
So friends, stay tuned. In the next few posts coming up, I’ll dive into solution architecture specifically and we’ll look at the various elements of this on the end to end, and well ongoing journey of architecting a solution on the Power Platform!
Let me know in the comments below, if there’s any area to this series that you’d like me to focus on and I’ll be sure to cover these topics! Stay tuned friends! 🤩