Posts

Achieving Microservices Flexibility… Through Patterns!

Whether organizations turn to microservices to solve issues with existing applications or build greenfield applications, creating applications that consist of many single purpose microservices introduces the need for those individual services to interact in real-time to provide value to the end user.

Today REST is most commonly used for these interactions, and it works fine for some situations, but as discussed in my previous blog post there are many advantages to using messaging instead, not the least of which is the ability to use a wide range of synchronous and asynchronous message exchange patterns. These patterns, such as publish/subscribe, request/reply, one-way notification and multi-request/single-response have been a staple of enterprise architecture for many years, and they are ideal for microservices since they are inherently distributed. To prove this point, lets look at how you might solve a real-world problem.

Meet Sol-Beer

The problem I have chosen to solve is near and dear to my heart (as I hope it is to yours!).… Read the rest

Webinar Recap: Microservices in Practice

Microservices are extremely popular these days, and for good reason. They provide a blueprint that make it easier to create robust and scalable applications. During a webinar called “Microservices in Practice” (which you can watch here), Jonathan Schabowsky of Solace’s office of the CTO demonstrated how important the right choice of communications between services really is.

As you might expect, REST was the opening topic. But REST has some limitations that any architecture needs to consider. Jonathan described the challenges in interaction cardinality of synchronous and asynchronous, and how the wrong choice can lead to tightly coupled architecture. During the talk, a poll of the viewers found that 71% felt that asynchronous delivery is very important.

Jonathan then highlighted a few desirable characteristics for microservices: scaling, fault tolerance, performance, management and security. Using personal experience, he guided participants through the role each of these items plays and how to achieve them.… Read the rest

Solace Says: Enabling Event-Driven Microservices

In this edition of Solace Says, I interviewed Jonathan Schabowsky of Solace’s office of the CTO, who recently wrote a blog post about event-driven microservices that’s turned out to be quite popular. In that post, and this video, Jonathan describes the characteristics most microservices share, what they’re commonly used for, and how they share information with REST and/or messaging technology.

Read the rest

Experience the Awesomeness of Event-Driven Microservices

Microservices are extremely popular these days, and for good reason. They provide a blueprint that makes it easier for developers to repeatedly create robust and scalable applications. While there is no official industry-adopted definition of microservices, there are some generally accepted attributes that make up a microservice:

  • Small and single in purpose
  • Communicate via technology agnostic protocols
  • Support continuous integration
  • Independently deployable.

Many of these attributes are interrelated – since services are to be small and single in purpose, they must communicate with each other to provide real business value, and to be independently deployable they need to be small and single in purpose. While each of these are vital attributes, the ability to communicate without being tightly coupled to one another is a critical aspect of microservices architecture.

Smart Endpoints and Dumb Pipes

Well-known author and developer Martin Fowler advocates what he calls “smart endpoints and dumb pipes” for microservices communication.… Read the rest

Webinar Recap: Solace: Messaging with Purpose on Pivotal Cloud Foundry

On May 30, Solace Senior Architect Jonathan Schabowsky explained how messaging and microservices work with Pivotal Cloud Foundry as part of a Brighttalk webinar. He provided a great introduction to the concept of microservices and then dove into the details of architectural considerations.

As part of that he covered how Platform as a Service (PaaS) makes it easier to deliver on the microservice promise by eliminating some of the distractions that app developers face while providing a “deploy anywhere” capability. But, as Jonathan covers, “deploy anywhere” comes with its own headaches around communication and data movement.

Jonathan dug into a comparison of REST and other open protocols, like AMQP and MQTT. One of his comments (often mentioned in technology) refers to the fact that not everything is a nail to the REST hammer. Fortunately, we find out that there are a lot of different tools available in the Solace toolbox. You can find even more on microservices on the Solace dev site and find code, demos and more examples on the Labs site and Github repositories.… Read the rest

Events

Nothing Found

Sorry, no posts matched your criteria