James Alexandrou

James Edward Bye

Following his departure from the TV soap in 2007, James said: “I’ve decided to leave the show to experience other aspects of my industry. “Having turned 21, I felt it was a good time to leave. I owe everything to the show and would love to come back one day – that’s if EastEnders would have me.”

Where is Martin Fowler actor James Alexandrou now? The 34-year-old has taken on several acting roles since leaving EastEnders, including minor parts in Casualty and Silent Witness. He has also turned his hand to theatre and played Romeo in the Globe Theatre’s production of Romeo and Juliet.

Fowler was born and grew up in Walsall, England, where he went to Queen Mary’s Grammar School for his secondary education. He graduated at University College London in 1986. In 1994 he moved to the United States, where he lives near Boston, Massachusetts in the suburb of Melrose.

Not only will Martin have a new target placed on his back, but Sonia Fowler (Natalie Cassidy) will be left committing the “unthinkable” to help him. He admitted to Sonia he thought he’d killed another man, bringing them closer together. Martin has now found out that he’s not dead after all and in hospital.

Martin (played by James Bye) married Ruby (Louisa Lytton) earlier this year on EastEnders after he believed his relationship with ex-spouse Stacey Slater (Lacey Turner) had come to an end.

In short, the 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. A guide to material on martinfowler.com about microservices.

Microservices: The individual services and functions – or building blocks – that form a larger microservices-based application. RESTful APIs: The rules, routines, commands, and protocols – or the glue – that integrates the individual microservices, so they function as a single application.

Microservices architecture is a method of development where a large application is divided into small modular services. The adoption of microservices applications is increasing exponentially — Set to grow more than 23.4% to reach $1.8 Million by 2025.

Scoping Microservices A common question people ask is “How big (or small) should my microservice be?” One common answer is that the size of a microservice can be variable, but it should be coded by no more than a dozen people (the so-called “two pizza rule”).

The number of endpoints is not really a decision point. In some cases, there may be only one endpoint, whereas in some other cases, there could be more than one endpoint in a microservice. For instance, consider a sensor data service, which collects sensor information, and has two logical endpoints–create and read.

The catch here is “micro”, these pieces should ideally be under 10K lines of code. As they are independent it helps the business release features faster.

Application Development Trends: 73% of firms using or planning to use microservices see it as very or extremely beneficial for building next-generation services and applications. Nearly two-thirds of the organizations surveyed (63%) are building some (18%) or all (46%) of their applications using microservices.

While Google built systems that share many characteristics with microservices as they exist today (as well as a powerful infrastructure that has since been replicated by a number of open-source projects), not every design choice that Google engineers made should be duplicated.

Allows experimentation & innovation, leveraging cutting edge technologies, but localize the related risk only to a specific service. Because of independent services, scaling of teams is easier, as Microservices reduces coupling between teams and enables more autonomy and accountability.