Microservices Architecture ..

Microservices architecture as a service-oriented architecture composed of loosely coupled elements that have bounded contexts. It is a software architecture style in which complex applications are composed of small, independent processes communicating with each other using language-agnostic APIs. These services are small, highly decoupled and focus on doing a small task, facilitating a modular approach to system-building.

Microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies.

Microservices, in some ways, make for a better developer experience too, which allows you to grow your business more rapidly. More and more people are flocking to try the microservices architecture because its modularity of small, focused, quasi-independent services allow businesses to deploy and scale services more easily. This segmentation also allows smaller teams that create smaller code bases. Microservices also lend themselves to agile, scrum and continuous delivery software development processes with shorter lifecycles. This architecture distinguishes itself from service-oriented architecture (SOA) because each microservice only belongs to one application, not multiple.

ref:

Microservices overview - http://martinfowler.com/articles/microservices.html

Microservices Architecture Pattern - http://microservices.io/patterns/microservices.html

Microsoft Azure Service Fabric and the Microservices Architecture - https://msdn.microsoft.com/en-us/magazine/mt595752.aspx

Microservices Wiki - https://en.wikipedia.org/wiki/Microservices

Adopting Microservices at Netflix: Lessons for Architectural Design - https://www.nginx.com/blog/microservices-at-netflix-architectural-best-practices/

Four-Tier Application Architecture - https://www.nginx.com/blog/time-to-move-to-a-four-tier-application-architecture/

Microservices Architecture for Enterprises - https://www.thoughtworks.com/insights/blog/microservices-architecture-for-enterprises

Misc - 

1. http://nordicapis.com/microservices-architecture-the-good-the-bad-and-what-you-could-be-doing-better/
2. http://capgemini.github.io/architecture/is-rest-best-microservices/
3. http://www.infoworld.com/article/2682502/application-development/application-development-what-microservices-architecture-really-means.html

Systems Engineering ..

Systems engineering is an interdisciplinary field of engineering that focuses on how to design and manage complex engineering systems over their life cycles.

1. Focus on holistic product Architecture(Eco-System, System, Sub-System, Component)
2. Know your key stakeholder & involve them early in the decision making process
3. Focus on Why .. Ask right questions all the time
4. Trace tests(System tests, integration tests, unit tests) to Requirements/Needs
5. Focus on Usage model to come up with Business Requirements
6. Focus on Logic Architecture before jumping to product physical design
7. Follow RAPID approach in decision making
8. Follow V model of development

ref:

Systems Engineering - http://en.wikipedia.org/wiki/Systems_engineering

V-model - http://en.wikipedia.org/wiki/V-Model_%28software_development%29

WebServices Frameworks

Java WebServices Development Tools:

Apache CXF: Apache CXF is an open source services framework. CXF helps you build and develop services using frontend programming APIs, like JAX-WS and JAX-RS. These services can speak a variety of protocols such as SOAP, XML/HTTP, RESTful HTTP, or CORBA and work over a variety of transports such as HTTP, JMS or JBI.

Apache Axis2: is a Web Services / SOAP / WSDL engine, the successor to the widely used Apache Axis SOAP stack. There are two implementations of the Apache Axis2 Web services engine - Apache Axis2/Java and Apache Axis2/C.

Apache Wink: Apache Wink is a simple yet solid framework for building RESTful Web services. It is comprised of a Server module and a Client module for developing and consuming RESTful Web services.

JAX-WS: JAVA-API( XML-based Webservices, means mainly WSDL/SOAP though REST is possible too )

RI(Reference Implementation): JAX-WS: { javax.xml.ws.**.* , core Web services support } = JAX-WS “RI” [is subset of] Metro
Note: Metro = JAX-WS “RI” + WSIT/Tango ( WSIT/Tango provides support for Security, Reliability, Transactions and Interoperability with .NET 3.0 )

JAX-RS: JAVA-API( RESTful Web Services )
RI(RI(Reference Implementation): JAX-RS = { javax.ws.rs.**.* } = Jersey

AWS Toolkit for Eclipse: The AWS Toolkit for Eclipse is an open source plug-in for the Eclipse Java IDE that makes it easier for developers to develop, debug, and deploy Java applications using Amazon Web Services. With the AWS Toolkit for Eclipse, you’ll be able to get started faster and be more productive when building AWS applications.

Eclipse WST Web Services UI: The Web Services project is a sub-project in the Eclipse WTP Top-Level Project. The project consists of two components: The JST Web services component, which contains tools for developing and interacting with Java Web services and the WST Web services component, which contains tools for Web services development which is not Java specific.

Eclipse with Lomboz plugin: Lomboz is an open source and free J2EE development environment for businesses and individuals. You can develop, test, profile and deploy Web, Web services, Java, J2EE and EJB applications with this IDE. Lomboz has comprehensive support for most J2EE standard application server runtimes, and supports most popular open source runtimes such as JOnAS, and other vendor runtime environments. Lomboz is buillt on the Eclipse open source platform and the Web Tools Platform (WTP) projects.

OpenSource WebService Testing Tools:

• soapUI

• TestMaker

• WebInject

Miscellaneous:

• Tools to view HTTP requests and responses - Wireshark, Fiddler, IEInspector HTP Analyser, Firebug, HttpFox

           Web Development: Client side debugging tools/plugins inside Browser:

            Chrome => Chrome developer Tools ( F12 )

            Firefox  => FireBug/Poster

            IE          => Fiddler

• Tools to test RESTful Webservices - RESTClient(from GoogleCode; A Java application to test RESTful webservices), HTTP4E(REST HttpClient for Eclipse)

• POSTER add-on to Firefox - RESTful Web Services can be tested using a firefox addon called Poster. It's a developer tool for interacting with web services and other web resources that lets you make HTTP requests, set the entity body, and content type. This allows you to interact with web services and inspect the results.

• Microsoft’s WCF & Service Trace Viewer Tool - Windows Communication Foundation (WCF) Service Trace Viewer Tool helps you analyze diagnostic traces that are generated by WCF

ref:

Open Source Web Services Tools in Java - http://java-source.net/open-source/web-services-tools

WebServices (SOAP vs REST) - http://www.ajaxonomy.com/2008/xml/web-services-part-1-soap-vs-rest

JAX-WS and JAX-RS United in CXF - http://sberyozkin.blogspot.com/2011/01/jax-ws-and-jax-rs-united-in-cxf.html

SaaS(Software as a Service) LinkedIn Discussions

Why You Need A SaaS Strategy -

http://www.linkedin.com/news?actionBar=&aIdx=16&articleID=105293146&aogid=106558284&gid=122612&gid=122612&srchType=dsc&trk=news_brkout&goback=.nvr_122612_2

How Much Investment Does It Take To Start a SaaS Co -

http://www.linkedin.com/news?viewArticle=&articleID=105314869&gid=122612&srchCat=WOTC&articleURL=http://montclairadvisors.com/blog/2010/01/how-much-investment-does-it-take-to-start-a-saas-co/&urlhash=JCqT

What is the most popular platform used your companies for building the SaaS apps -

http://www.linkedin.com/groupAnswers?viewQuestionAndAnswers=&discussionID=12443905&gid=122612&trk=EML_anet_qa_ttle-cThOon0JumNFomgJt7dBpSBA

The Basics of Software as a Service Pricing -

http://www.linkedin.com/news?viewArticle=&articleID=105441208&gid=122612&srchCat=WOTC&articleURL=http://softwaremaven.innerbrane.com/2010/01/basics-of-software-as-service-pricing.html&urlhash=RgjR

Let Them Build It and They Will Come -

http://www.linkedin.com/news?viewArticle=&articleID=106558284&gid=122612&srchCat=RCNT&articleURL=http://leveragepoint.typepad.com/leveragepoint_perspective/2010/02/let-them-build-it-and-they-will-come.html&urlhash=RdMG

What are the diffrent pricing models for SaaS -

http://www.linkedin.com/groupAnswers?viewQuestionAndAnswers=&discussionID=15592660&gid=122612&trk=EML_anet_qa_ttle-cThOon0JumNFomgJt7dBpSBA

Should Cloud Computing Be On Your Roadmap? -

http://electronics.wesrch.com/pdfEL11TZMN7KIXY

The Eight Fallacies of Distributed Computing - Peter Deutsch

Essentially everyone, when they first build a distributed application, makes the following eight assumptions. All prove to be false in the long run and all cause big trouble and painful learning experiences.

1. The network is reliable

2. Latency is zero

3. Bandwidth is infinite

4. The network is secure

5. Topology doesn't change

6. There is one administrator

7. Transport cost is zero

8. The network is homogeneous

ref:

http://en.wikipedia.org/wiki/Fallacies_of_Distributed_Computing

http://www.rgoarchitects.com/Files/fallacies.pdf

WebServices and Eight Fallacies -

http://www.oreillynet.com/xml/blog/2002/07/web_services_and_the_eight_fal.html

Distributed Computing Fallacy - http://feedblog.org/2007/09/23/distributed-computing-fallacy-9/

Microsoft Architecture Journal online

Learn Architecture from Microsoft Architecture Journals -

http://msdn.microsoft.com/en-us/architecture/cc511514.aspx

Role of an Architect -

http://msdn.microsoft.com/en-us/architecture/cc505966.aspx

http://download.microsoft.com/download/3/d/7/3d718c6c-e5f3-41e3-b346-6e9f114e2531/journal15_english.pdf.zip (pdf version)

Strategies for Design -

http://msdn.microsoft.com/en-us/architecture/bb245653.aspx

http://download.microsoft.com/download/4/d/a/4da0ddee-77e0-47d1-aaa7-a5dd619b8bca/journal6_english.pdf.zip (pdf version)

Web Architecture -

http://msdn.microsoft.com/en-us/architecture/bb735857.aspx

http://download.microsoft.com/download/f/5/2/f520c83a-d2ed-4be8-9bc6-b39a1f9a4562/AJ12_EN.zip (pdf version)

Mobile Architecture -

http://msdn.microsoft.com/en-us/architecture/bb985491.aspx

http://download.microsoft.com/download/2/9/0/290aa77c-8fb0-4fa1-97e2-61d9d83d2bdb/journal14_english.pdf.zip (pdf version)

Data by Design -

http://msdn.microsoft.com/en-us/architecture/bb245655.aspx

http://download.microsoft.com/download/4/d/a/4da0ddee-77e0-47d1-aaa7-a5dd619b8bca/journal8_english.pdf.zip (pdf version)

Distributed Computing -

http://msdn.microsoft.com/en-us/architecture/dd129905.aspx

http://download.microsoft.com/download/c/2/b/c2b3f5f0-4ff5-4bbd-aba9-c33090cd5476/AJ17_EN.zip (pdf version)

Software plus Services -

http://msdn.microsoft.com/en-us/architecture/bb906058.aspx

http://download.microsoft.com/download/1/1/c/11cbcb6e-9215-4b06-b367-c97141a86cc9/Journal-13-ENG.pdf.zip (pdf version)

SOA Today & Tomorrow -

http://msdn.microsoft.com/en-us/architecture/aa699437.aspx

http://download.microsoft.com/download/9/0/6/906F57FF-3C6F-4412-A802-0AB0E4B58C71/AJ21_EN.zip (pdf version)

Architecture in Turbulent Times -

http://msdn.microsoft.com/en-us/architecture/aa894359.aspx

http://download.microsoft.com/download/2/9/0/290AA77C-8FB0-4FA1-97E2-61D9D83D2BDB/AJ20_EN.zip (pdf version)

Identity and Access Management -

http://msdn.microsoft.com/en-us/architecture/cc836389.aspx

http://download.microsoft.com/download/a/7/6/a76e5770-19b1-415b-8b6c-6ff5c7b71574/J16_EN.zip (pdf version)

97 Things Every Software Architect Should Know !!!

1. Don't put your resume ahead of the requirements by Nitin Borwankar
2. Simplify essential complexity; diminish accidental complexity by Neal Ford
3. Chances are your biggest problem isn't technical by Mark Ramm
4. Communication is King; Clarity and Leadership its humble servants by Mark Richards
5. Architecting is about balancing by Randy Stafford
6. Seek the value in requested capabilities by Einar Landre
7. Stand Up! by Udi Dahan
8. Skyscrapers aren't scalable by Micheal Nygard
9. You're negotiating more often than you think by Michael Nygard
10. Quantify by Keith Braithwaite
11. One line of working code is worth 500 of specification byAllison Randal
12. There is no one-size-fits-all solution by Randy Stafford
13. It's never too early to think about performance by Rebecca Parsons
14. Application architecture determines application performance by Randy Stafford
15. Commit-and-run is a serious crime. Respect your Colleagues by Niclas Nilsson
16. There Can be More than One by Keith Braithwaite
17. Business Drives by Dave Muirhead
18. Simplicity before generality, use before reuse by Kevlin Henney
19. Architects must be hands on by John Davies
20. Continuously Integrate by Dave Bartlett
21. Avoid Scheduling Failures by Norman Carnovale
22. Architectural Tradeoffs by Mark Richards
23. Database as a Fortress by Dan Chak
24. Use uncertainty as a driver by Kevlin Henney
25. Scope is the enemy of success by Dave Quick
26. Reuse is about people and education, not just architecture by Jeremy Meyer
27. There is no 'I' in architecture by Dave Quick
28. Get the 1000ft view by Erik Doernenburg
29. Try before choosing by Erik Doernenburg
30. Understand The Business Domain by Mark Richards
31. Programming is an act of design by Einar Landre
32. Time changes everything by Philip Nelson
33. Give developers autonomy by Philip Nelson
34. Value stewardship over showmanship by Barry Hawkins
35. Warning, problems in mirror may be larger than they appear by Dave Quick
36. The title of software architect has only lower-case 'a's; deal with it by Barry Hawkins
37. Software architecture has ethical consequences by Michael Nygard
38. Everything will ultimately fail by Michael Nygard
39. Context is King by Edward Garson
40. It's all about performance by Craig L Russell

41. Engineer in the white spaces by Michael Nygard
42. Talk the Talk by Mark Richards
43. Heterogeneity Wins by Edward Garson
44. Dwarves, Elves, Wizards, and Kings by Evan Cofsky
45. Learn from Architects of Buildings by Keith Braithwaite
46. Fight repetition by Niclas Nilsson
47. Welcome to the real world by Gregor Hohpe
48. Don't Control, but Observe by Gregor Hohpe
49. Janus the Architect by Dave Bartlett
50. Architects focus is on the boundaries and interfaces by Einar Landre
51. Challenge assumptions - especially your own by Timothy High

52. Record your rationale by Timothy High
53. Empower developers by Timothy High
54. It is all about the data by Paul W. Homer
55. Control the data, not just the code by Chad LaVigne
56. Don't Stretch The Architecture Metaphors by David Ing

57. Focus on Application Support and Maintenance by Mncedisi Kasper
58. Prepare to pick twoby Bill de hOra
59. Prefer principles, axioms and analogies to opinion and taste by Michael Harmer
60. Start with a Walking Skeleton by Clint Shank
61. Share your knowledge and experiencesby Paul W. Homer
62. Make sure the simple stuff is simple by Chad LaVigne
63. If you design it, you should be able to code it by Mike Brown
64. The ROI variable by George Malamidis
65. Your system is legacy, design for it by Dave Anderson
66. If there is only one solution, get a second opinion by Timothy High
67. Understand the impact of change by Doug Crawford
68. You have to understand Hardware too by Kamal Wickramanayake
69. Shortcuts now are paid back with interest later by Scot Mcphee
70. "Perfect" is the Enemy of "Good Enough" by Greg Nyberg
71. Avoid "Good Ideas" by Greg Nyberg
72. Great content creates great systems by Zubin Wadia
73. The Business Vs. The Angry Architect by Chad LaVigne
74. Stretch key dimensions to see what breaks by Stephen Jones
75. Before anything, an architect is a developer by Mike Brown
76. A rose by any other name will end up as a cabbage by Sam Gardiner
77. Stable problems get high quality solutions by Sam Gardiner
78. It Takes Diligence by Brian Hart
79. Take responsibility for your decisions by Yi Zhou
80. Dont Be a Problem Solver by Eben Hewitt
81. Choose your weapons carefully, relinquish them reluctantlyby Chad LaVigne
82. Your Customer is Not Your Customer by Eben Hewitt
83. It will never look like that by Peter Gillard-Moss
84. Choose Frameworks that play well with others by Eric Hawthorne
85. Making a strong business case by Yi Zhou
86. Pattern Pathology by Chad LaVigne
87. Learn a new language by Burk Hufnagel
88. Dont Be Clever by Eben Hewitt
89. Build Systems to be Zuhanden by Keith Braithwaite
90. Find and retain passionate problem solvers by Chad LaVigne
91. Software doesnt really exist by Chad LaVigne
92. Pay down your technical debt by Burk Hufnagel
93. You can't future-proof solutions by Richard Monson-Haefel
94. The User Acceptance Problem by Norman Carnovale
95. The Importance of Consommé by Eben Hewit
96. For the end-user, the interface is the system by Vinayak Hegde
97. Great software is not built, it is grown by Bill de hora

ref:

http://97-things.near-time.net/wiki