Friday, November 22, 2019

About the job of Solution Architect

The theme is about the work of Solution Architect (hereinafter abbreviated as SA). I want more people to know what SA is. SA is really interesting! I want to shout. In this post, I will talk about when I was doing SA on AWS , but I understand that it is only a story of experience and “I was doing this” , not a representation of AWS . Please give me.

I was in mixi for about 2.5 years from 2010/2 to 2012/7 and has been developing advertising-related applications. It was a very long experience for me, but in retrospect it was very short. And then, I have been doing SA for a long time, although AWS , Hortonworks, SORACOM and the company have changed.

From the point of view of someone who has worked with me, I think it looks like a sales engineer or, in some cases, an evangelist , and that's what it is. But in fact, that's not all, so I want everyone to know about it. It's a very interesting job, so I'm happy if it spreads as one of the career paths of engineers .

What are you doing?

I think that there are many people who are familiar with AWS, so I will talk about it as an example. What AWS SA does is to get AWS to “use” and provide all technical support to help your business succeed and solve problems . It is the job.

If you are the first person to use AWS, I will explain something like "Common configurations of XX (for example, web) applications built on AWS ". If you have something you want to do, but you have a poorly designed application, you can use a whiteboard to architect. For customers who have already settled on the design, we will review based on the design and have a discussion aiming at a better architecture .

If you are in trouble with MySQL 's performance, we will provide support for finding where the problem is and propose a way to solve it in AWS like the problem that you see . Of course, you often find out that it was an application or query issue.

This is an interesting part of SA, but I don't talk about it like "Oh, that's about the application, please solve it there". Deep dive until you find out how to solve the problem by digging into discussions such as creating the application, the contents of the query, and how to throw the query. We will find the root cause of the problem, have a common understanding with our customers, and create actions for it. Of course, it is best if you can solve the problem suddenly, but it is often the case that you cannot suddenly change a running application to drastic. First of all, we will discuss application refurbishment while coping with provisional instance size increase, read replica addition, and faster storage IO.

Besides, or writing an application for verification of whether or not meet the required performance and function, related to open source software source code , or protocol of RFC will also crap read a whole bunch of. In some cases, the customer may see the usage fee and usage trend, and suggest that if the application is modified in this way, a cheaper instance type will be available at all.

Do the right things, it ’s just do it if you can believe that it ’s correct / sympathetic if your application can run more stably. .

Why do you do this? That is because it is very important to “use a platform (eg AWS ) sustainably ”. A service like AWS is a stock-type business, not a sell-out type, so it maximizes not only the height but also the area by multiplying the length by using it for a long time rather than raising the momentary sales. It is important.

It's a chicken egg, but because of this kind of business, SA can do everything to help customers as an engineer. Theoretically, the customer's applications and business will be stable as long as they are helped, resulting in longer and more scalable use.

No comments:

Post a Comment