Tag Archives: SOA
One Datastore per MicroService?
This article represents details on whether to use single datastore per microservice. Please feel free to comment/suggest if I missed to mention one or more important points. Also, sorry for the typos. From what I researched, the preferred architecture for microservices is polyglot persistence pattern. (http://martinfowler.com/bliki/PolyglotPersistence.html ). You could further read about this on following pages: http://martinfowler.com/articles/microservices.html#DecentralizedDataManagement http://microservices.io/patterns/data/database-per-service.html As per the best practices, each micro-service should have one database private to it. There are different ways to achieve the above objective. Some of them are listed below: Same database system for different services. In this following could be done: Different set of tables specific to microservice in the same database …
Lessons from Evernote Usage of Apache Thrift Framework
This article throws light on underlying technology used by Evernote to meet the primary requirement of having client applications on different OS platforms connect to server application for accessing/updating the notes. What is Evernote? As per Wikipedia…Evernote is a suite of software and services designed for notetaking and archiving. A “note” can be a piece of formatted text, a full webpage or webpage excerpt, a photograph, a voice memo, or a handwritten “ink” note…. Evernote supports a number of operating system platforms (including OS X, iOS, Chrome OS, Android, Microsoft Windows, Windows Phone, BlackBerry, and webOS) and also offers online synchronisation and backup services. The diagram below illustrates …
Where do these SOA Transformation projects come from?
If you have been working on one of those SOA transformation projects as an technical architect, some of you might as well have wondered on the very fact as to what is the origin of such projects? Why companies invest on these initiatives? From where do they know that they would require to transform their application landscape into services based on SOA and much more. The answer to the above question lies with enterprise architecture initiatives and various enterprise architects who would have worked on it. Why EA initiatives in the first place? Lets look at some of the following pain-points which may lead to EA initiatives: A large enterprise …
I found it very helpful. However the differences are not too understandable for me