Blog Mission

A brain dump of my day to day endeavors in the world of systems programming an architecture.

Comments

Post a Comment

Popular posts from this blog

What an architect should first think about

I'm currently reading the book Beautiful Architecture . In one of the chapters the author outlines what an architect should take into consideration when thinking of a new system. There are 9 things. Functionality What functionality does the product offer to its users? Changeability What changes may be needed in the software in the future, and what changes are unlikely and need not be especially easy to make in the future? Performance What will the performance of the product be? Capacity How many users will use the system simultaneously? How much data will the system need to store for its users? Ecosystem What interactions will the system have with other systems in the ecosystem in which it will be deployed? Modularity How is the task of writing the software organized into work assignments (modules), particularly modules that can be developed independently and that suit each other's needs precisely and easily? Buildability How can the software b...
Read more

Notes from Release It! Book

Unbounded Result Sets / Unbounded Capacity In any API or protocol, the caller should always indicate how much of a response it is prepared to accept. TCP does this in the "window" header field. Search engine APIs allow the caller to specify how many results to return and what the starting offset should be. Limit results coming out from the database. SELECT TOP 15 colspec FROM tablespec SELECT colspec FROM tablespec WHERE rownum <=15 SELECT colspec FROM tablespec LIMIT 15
Read more