Here at Apiumtech, we offer services of consulting and development. The truth is that we don’t really like using the term “consulting” because of the typical image that most of us have in mind. I am sure you know who I’m talking about; the classic consultant with high fees that knows perfectly how to sell and present his solution to you but at the end, does not really help you… I guess we can blame some of the large consulting firms but of course, there are great professionals who deserve respect.
Since we’ve started this business adventure that is Apiumtech, 60% of our customers have asked us consultancy or auditing services. The audit, as we understand it, is nothing more than collecting information regarding the macro and micro architecture of the customers, understanding their processes, the procedures involved in the development of features, look at how they make estimates, teamwork, etc…
It usually takes 3 to 5 days – depending on the size and structure complexity of the client. We divide the work in three stages: collection of the information, analysis of the data and finally, action planning in order to enhance these processes. Actually, there’s a lot more than this. If you’re a company, a professional or a student and would like to know more about what is an audit for us, don’t hesitate to contact us… We love sharing!
PERFORMANCE TEST
Well… one of the actions that are necessary to audit is performance testing. In my opinion, this type of test is open to considerable confusions. A performance test is not about using jmeter nor is it about using your web massively to see what happens. Basically, we make it following this pattern:
- We ask what are the user’s processes, or the flow that the user follows to get something.
- We automate this flow and execute it massively.
- We collect metrics, a lot of metrics.
- We analyze the results.
- We hypothesize and then validate.
- We report the results and explain the bottlenecks.
- We give some recommendations to solve the problems and if necessary, make the platform scalable and increase the performance.
By the way… almost every time, what the performance test uncovers is a bad architectural design.
I was pleasantly surprised the other day when a few friends came over for dinner. We had a pleasant evening, relaxing, telling anecdotes and experiences… Well turns out that one of these friends – a great professional with high knowledge regarding SEO, had a very good idea that none of us had ever thought about.
As you do performance tests to increase the speed of a site, why don’t you focus it to provide services of WPO?
To be honest, we had not thought about it, but we love it. Partly because we won’t make any efforts to provide this service… by default, we’re improving performance.
The Web Performance Optimization is a practice in SEO that consists in increasing the loading speed of a website with the objective of improving the position.
Besides the obvious… (minimizing, compress the CSS, javascript, reduce the CSS rules, images in sprites, maps, base64 in CSS, monitoring nested tags, using CDN’s, cache, etc…) some architectural patterns will help you:
- Separate the reading from the writing on the persistence layer, for example with CQRS
- Make Event-Driven and be asynchronous
- Better to push than polling
Finding new applications of something you love is very really rewarding.
