CTO Operations

Magazine on Entrepreneurship, Project Management, Marketing and Products

Webapplications: scale or you get killed

| 0 comments

Developing Webapplications and proprietary applications that scale in terms of performance, code and team is challenging. Not only that these topics contrary in terms of ressources and goals, also they all have to be met in order to have a successful application. You got to be proactive. It sometime requires the Projectmanager is required to implement Quickwins to get back into business, but this is not a lasting strategy at all.

Application Scaling

  • Generally there are some great Tipps on Scaling an Application

 

Checklist for Webpage Speed:

  1. Use Y-Slow Browser Check for a general overview. A real insider is this the Y-Slow Scoremeter
  2. Get your self sure using the free Pingdom tools
  3. Check if your site validates correctly to make sure, your users don’t waste time locally
  4. Use Google Webmaster tools to analyze their view

 

Some good tweaks are:

 

Checklist for Application Scaling:

  1. Great Blog Post: Scale PHP
  2. Also pretty good Article on improving PHP Code

 

Information on Scaling, by Zend

And a older version of the same Presentation:
UPDATE:
  • Efficiency – Traded Off for Scalability
    • Efficiency is traded off for scalability. The most efficient thing is to write it in C and cram it into one process, but that’s not scalable.
    • Focus on the macro level, your components, and how they break out. Does it makes sense to do this an RPC or do it inline? Break it into a subpackage and just someday this may be different.
    • Focus on algorithms. In Python the effort to implement a good algorithm is low. There’s the bisect module, for example, where you can take a list, do something meaningful, and serialize it to disk and read it back again. There’s a penalty versus C, but it’s very easy.
    • Measurement. In Python measurement is like reading tea leaves. There’s a lot of things in Python that are counter intuitive, like the cost of grabage colleciton. Most of chunks of their apps spend their time serializing. Profiling serialization is very depending on what you are putting in. Serializing ints is very different than serializing big blobs.

     

  • Efficiency in Python – Knowing What Not to Do
    • More about knowing what not to do. How dynamic you make things correlates to how expensive it is to run your Python app.
    • Dummer code is easier to grep for and easier to maintain. The more magical the code is the harder is to figure out how it works.
    • They don’t do a lot of OO. They use a lot of namespaces. Use classes to organize data, but rarely for OO.
    • What is your code tree going to look like? He wants these words to describe it: simple, pragmatic, elegant, orthogonal, composable. This is an ideal, reality is a bit different

     

    Read the Full Article

Author: Guntram Bechtold

Produkte von der ersten Idee zur fertig Lösung zu bringen ist zentrale Aufgabenstellung von Bechtold. "Als Industrial Designer finde ich es absolut spannend wie die Produkte der Digitalisierung unsere Welt gestalten. Wissen und Kreativität so zu kombinieren dass nachhaltiger Nutzen für Anwender und Unternehmen entsteht ist entscheidend". Als #Certified Scrum Master hat Bechtold sich auf die Planung und Umsetzung von innovationsgetriebener Geschäftsmodellen spezialisiert.

Leave a Reply

Required fields are marked *.


*