Hail, Architect- Don't just get swayed by the hype around new releases of Sitecore.

It's not just about sitecore or it's new releases or update which is announced to all out there. Its about plan it and time it well. Your stakeholder is dependent upon you. What you say is written on the stone. So be careful. Like all other releases of software or product there is cooling period for any product to get matured and get adopted to the ecosystem. What I meant is a time to make your product stand strong against all issues which may surface in production and can haunt you for a week. If you see in the past almost all product or software underwent changes due to fixes or unstable or may be success to certain degree or call it a flop show.

Having said this, cooling period is something one must consider while setting up expectation with stakeholder. Watch the space carefully. 

Just don't get swayed by the hype of features it comes with rather you face the reality with risk/issues the new release can offer in return.

Next time you hear something about releases with new feature .Hold your horses! 

Assess it well! Act Smart ! Sell while Deliver !

This is my opinion and may not concur with everyone.

System Level Jargons

1. Thick Client
2. Thin Client
3. Smart Client
4. Rich Client
5. Agent
6. Upstream application
7. Downstream application
8. Back door entries
9. Backend
10. Frontend
11. OLTP- Online transaction Processing
12. Master- Transaction tables
13. OLAP
14. MOLAP
15. Datawarehourse
16. Datamart
17. Reporting
18. Staging Database
19. ETL- Extract Transform Load
20. Load balanced.
21. Custom Development vs Packaged Application
22. Reverse Engineering/forward engineering

 

Technical Design - Application Architecture These Terms does matters.

At application architecture level, we come across layers and tiers terminology.I will not delve much into these terms now but would rather focus on the details of it.  Yes we know presentation , business, service , data access layer and many such stacks that defines application architecture at logical level. We then built solution taking these layers pointers into consideration. Then comes what the code files where we have domain entities, utilities , classes, interface and so on..

Well, sometimes it becomes non trivial to appropiately name such source code files unders these layers.

To complete these blogs actually I need an expert advice to make this meaningful and comprehensive. I'm sure there is no such reference atleast available online. Everyone has their own theisis of explanation and fundamentals behind.

Most common suffix ending list of file name.

1. Manager
2. Provider
3. Handler
4. Helper
5. Factory
6. Services
7. Extender
8. Contract

So On

The point is as naive architecture I may put them wrongly and may latter refractor based on review. I'm sure there can be rule book across but fail to find one.

Need help.