Solution architecture
Turning vague requirements into designs a team can build. I test the risky assumptions first and stay involved through implementation.
Carlos Valls
Senior Solution Architect Appian SME
I design and build enterprise systems across application platforms, cloud services, integration and infrastructure.
I like difficult technical problems, direct communication and solutions that still make sense when they reach production.
- Based in
- Madrid, Spain
- Working as
- Independent Solution Architect
- Deepest specialization
- Appian
What I do
Platform architecture
Designing and running large application platforms: identity, connectivity, governance, upgrades, and what the application teams on top of them actually need.
Cloud & integration
The services around those platforms, mostly on Azure and AWS: APIs, messaging, and connections to the established systems that still matter.
Technical leadership
Design reviews, whiteboard sessions and shared standards, so teams reach sound technical decisions and understand why they made them.
How I work
Understand the actual problem
I normally start by taking the technology out of the conversation. What are we trying to achieve, and what can’t change? Once that is clear, the design usually gets simpler.
Prove the difficult parts early
If a design depends on something uncertain, I want to test it with a small proof of concept before it surfaces halfway through delivery. If that means going deeper into a technology I don’t know yet, I would rather learn it than treat it as somebody else’s problem.
Design for production
Failure handling, security, observability and maintainability belong in the first draft. I want to know what happens when a dependency is slow, down or answers with something unexpected.
Be direct
If I think something is a bad idea, unrealistic or more complicated than it needs to be, I will say so and explain why. My opinion isn’t the absolute truth, so I expect the same directness back.
Deep Appian expertise
Appian has been a major part of my career: first building applications, then administering the platform, designing it, moving it to the cloud and running it in production.
That depth is useful because I understand both the product and the systems around it. When something fails between Appian and the rest of the estate, I can usually tell which side the problem is on.
- Application teamsRequirements, reviews, standards
- AppianPlatform architecture, administration, integration, identity, governance, troubleshooting
- Integration & identityAPIs, messaging, single sign-on
- Cloud & networkingAzure, AWS, private connectivity
- OperationsUpgrades, incidents, root cause
Career
I joined VASS in 2018 and started working with Appian. Since then the work has moved from delivering applications to leading an Appian development practice, and then to solution and platform architecture, with Azure and AWS becoming a larger part of it along the way.
- VASSAppian Consultant
- Atos — Openbank engagementSenior Appian Consultant
- OpenbankBPM Chapter Lead
- HCLTechSolution Architect / Appian SME
- IndependentSenior Solution Architect
The full history is on LinkedIn. Carlos Valls on LinkedIn (opens in a new tab)
Let’s talk.
If you want to talk about solution architecture, Appian, cloud integration or a difficult technical problem, LinkedIn is the easiest way to reach me.
I’m always glad to have a good technical conversation.