All posts by Samudra Weerasinghe

Verifone: Using WSO2 Technology to Provide a Unique Payment Terminal that Increases Customer Engagement

In Honolulu, Hawaii, one man’s vision for the future of commerce has now become one of the world’s largest point-of-sale (POS) terminal vendors and a leading provider of payment and commerce solutions. Verifone still upholds this vision and keeps innovating for the future. At WSO2Con USA 2017 Ulrich Herberg, a senior Java architect at Verifone, joined us via Skype to speak about how they leveraged WSO2 technology when creating Verifone Carbon – a powerful device that combines elegant design into an integrated POS solution.

Verifone Carbon is a payment terminal that sets a new standard for a valuable and engaging consumer experience. It consists of two parts: a larger Android tablet facing the merchant and a smaller terminal with different kinds of payment functionality, such as Apple pay and payment through credit cards. These two devices are placed on a mobile base, which is used for charging the devices, printing receipts, and connecting to the ethernet.

What makes Verifone Carbon unique is that it’s embedded in an ecosystem called the Verifone Commerce Platform, which consists of a number of additional systems that provide more than what a typical payment terminal offers, explained Ulrich.

  • The developer portal allows third-party developers to create their own customer and merchant facing application by using Verifone’s APIs to download software development kits (SDKs) that can trigger payments, get information of successful or failed payments and more.
  • The app marketplace provides an interface similar to the Google Play Store or the Apple App Store where these apps can be placed and purchased.
  • The estate owner portal is used by large corporations that directly deal with the merchants to
    • Manage the estate (all the devices)
    • Get an overview of the devices
    • Manage, create, remove and update merchants
    • Purchase apps for the merchants
  • The merchant portal provides a smaller scope for the merchants only, which allows them to see their devices and purchase apps for their devices

With Verifone Carbon, merchants can now reward their best customers with loyalty points, display promotional media and coupons, leverage beacons for store analytics and invite customers to redeem personalized offers in real-time among other things.

Ulrich explained that for all of this to happen, they needed a solution that allowed them to manage and monitor all the Carbon devices. They started by evaluating commercial products. The commercial products worked on a pay-per-device model which would have been costly as they scaled up. At often times they didn’t have all the features they required and didn’t provide the flexibility to create any customized features.

The fully open source WSO2 Enterprise Mobility Manager (WSO2 EMM which is now significantly enhanced to provide enterprise IoT solutions as well as mobile device and app management in a single download via WSO2 IoT Server) overcame all of these challenges. “We were able to create a solution that fit our exact needs by either modifying the product on our own or getting WSO2 support services to help modify it,” said Ulrich. They avoided vendor lock-in and are independent of anyone else because they have control over the source code. They were also able to easily integrate WSO2 EMM with their existing terminal management infrastructure.

Ulrich then went on to discuss three major use cases of WSO2 EMM in Verifone Carbon.

Use case 1: Blank Android devices are shipped to the merchants so that they all have the same operating system image. WSO2 EMM uses individual device certificates to identify, authorize and authenticate these devices using mutual Transport Layer Security (TLS).

Use case 2: Verifone already has a legacy terminal management system which runs on a different operating system that can’t directly connect with and use Android features. So they used WSO2 EMM to communicate with the tablet.

Use case 3: Verifone doesn’t use the interface provided by WSO2 EMM so they had figure out how to use WSO2 EMM as a black box. They call it from their terminal management system, sends commands and monitors all the devices through it without having to know how it works internally. They did this by working closely with WSO2 to create a thorough list of RESTful APIs that were documented in Swagger.

Ulrich went on to list a few more WSO2 EMM features they currently use including

  • Getting device information including location data
  • Over-the-air (OTA) update that allows you to update the OS remotely
  • APK installation/update/removal in the background
  • Remotely locking, rebooting or factory resetting the devices
  • Debugging and sending Android logs to the server
  • Sending pop up notification to the tablet

He concluded by explaining in detail how they plan on scaling WSO2 EMM as the number of devices becomes larger.

To learn more about how Verifone used WSO2 technology to increase customer engagement through a unique payment terminal watch his talk at WSO2Con USA 2017.

West Interactive: Using WSO2 Identity Server to Enhance Customer Experience

Headquartered in Omaha, West Corporation is all about telecommunication – be it conferencing solutions, safety services, interactive voice response solutions or speech application automation. Pranav Patel, the vice president of systems development at West Interactive, recently spoke at WSO2Con USA 2017 about the unique customer experience they offer through their multi-tenanted role-based identity and access management solution built using WSO2 Identity Server.

An increasing numbers of users today are turning to various different channels like the web, mobile devices, and social media to interact with vendors. Pranav explained that knowing the customer and making sure that they can access West Interactive’s services from whichever channel they prefer is a key requirement for them.

West has been in the telecommunication industry for the last 30 years, and quite commonly, have many solutions that are siloed and distributed. Connecting all these solutions was a major challenge they needed to overcome in order to provide a holistic experience to their customers, explained Pranav. This meant dealing with and managing various different identities that belonged to many different customer portals. They needed to create a solution that revolves around centralizing user identities to a single user portal and creating an efficient identity and access management system.

Pranav then examined the requirements they needed to meet in order to achieve operational efficiency, easily manage accounts, save costs, and provide great customer experience. Other than the evident single sign-on and federation requirements, multitenancy with hierarchical tenant management was an important feature that enabled them to serve all their tenants (a client of West represented as a domain in the system) and users (individuals that require access to the portal and are grouped at the tenant level) through their portal. The system also needed to enforce rule-based access control that allows access to certain products (web applications that need to be integrated) depending on who the user is. In addition to this, they had corporate policy requirements for passwords, needed to maintain password history and had a password expiry date that prompted users to frequently change the password. Audit logging and user bulk imports were some other requirements.

“WSO2 fulfilled several of our requirements out-of-the-box, especially support for various protocols and heterogeneous multiple user stores,” observed Pranav. He went on to explain that they could easily extend the product and customize it for any features that it didn’t already have, making it the perfect solution for West.

WSO2 Identity Server is used for

  • Introducing a relationship hierarchy between the parent tenant and child subtenant and allowing multi-tenancy
  • Asking for and storing answers to five security questions per user
  • Defining permissions or roles for products (web applications) and users
  • Providing single sign-on and federation for users
  • Allowing employees to mimic a user and see how they perceive the user portal
  • Enforcing password policies set by tenants

Pranav expressed how WSO2 Identity Server meets all their current requirements and how they would like to introduce customizable login pages (by tenant), two-factor and multi-factor authentication, automated user provisioning and self-registration among other features in the future. He concluded by saying they were looking forward to adding WSO2 Data Analytics Server to the mix in order to monitor what’s really going on in the system.

To learn more about West Interactive’s story listen to Pranav’s talk at WSO2Con USA 2017.

WSO2Con USA 2017 – ballerinas, blockchain, oxygen bars and more!

San Francisco met us with bitter, cold winds, but we didn’t let that stop us from hosting the best user conference ever! With a fully restructured agenda, major product and roadmap reveals and phenomenal entertainment, this year’s WSO2Con USA was bigger and better than ever.

This year, we even had an actual oxygen bar inside the WSO2 Oxygen Bar: a place where attendees were able to meet with WSO2’s solutions architecture and engineering teams to answer all their questions on integration, API management, analytics, identity and access management, and the Internet of Things.

The conference started off with a bang, literally. The Taiko drummers marched on to stage and gave a warm welcome to everyone in the crowd!

WSO2 Founder, CEO and Chief Architect Dr. Sanjiva Weerawarana then presented the repositioning of WSO2’s product strategy to focus on providing a platform that enables digital transformation through integration, API management, identity and access management, smart analytics, and the Internet of Things.

Thomas Squeo, the senior vice president of digital transformation and enterprise architecture at West Corporation, followed this with another keynote. He explored how to digitally disrupt from within your enterprise by empowering your employees who will in turn engage with customers, transform your products and optimize operations.

Next, cue the ballerinas…

…which led to WSO2’s big reveal: Ballerinalang

Sanjiva examined Ballerina in detail: the general purpose, concurrent and strongly typed programming language with both textual and graphical syntaxes, optimized for integration. Following this, Sameera Jayasoma, the associate director, architect and lead choreographer of Ballerina showcased a few demos of the language in use.

The first day then broke off into the individual tracks; integration, analytics and strategy; with introductory, advanced and hand-on sessions as well as customer talks from Motorola Mobility and State of Arizona.

The end of day one was met with smooth Jazz sounds of The San Francisco Metro Combo at our networking event where attendees got to mingle with their peers and WSO2 experts.

The second day commenced with a keynote by State of Arizona Chief Technology Officer Jason Simpson who examined their cloud-first strategy towards becoming a digital government. He spoke on the challenges of moving their legacy technology and systems to the cloud with low budgets to meet the increasing demands of their users and went on to explain how State of Arizona overcame them.

This was followed by an insightful customer panel on bridging IT and business in digital transformation moderated by our very own Vice President of Solutions Architecture Asanka Abeysinghe. The panel consisted of Jason Simpson, the CTO of State of Arizona, Sri Harsha Pulleti, an integration architect at Motorola Mobility and Naresh Sikha, the chief architect at StubHub.

The second day’s tracks consisted of technical sessions on integration, analytics, API management, IoT and Security by WSO2 experts and many customer talks and panels including:

Yet another day of learning and exchanging ideas came to an end. But that wasn’t it for day two! Right after the sessions we went into the carnival themed conference party where attendees got to mingle, play old-school arcade games like Street Fighter, take funky pictures at the photo booth and dance the night away. DJ Nikkie Matteo scratched some killer beats but the band, Pacific Soul, stole the show and made everyone cut loose, footloose and kick of their Sunday shoes!

Day three went straight into the tracks that included technical sessions in the areas of IoT, security and devops. It also had a track specially for partners and one specially by partners. The customer and partner talks on day three included:

  1. IoT in Airline Operations, Suresh Subasinghe, Principal Architect, United Airlines
  2. Multi-tenanted, Role-based Identity & Access Management Solution at West, Pranav Patel, VP, Systems Development, West Interactive
  3. 0-60 with WSO2: API Management and User Authentication and Authorization Automation, Ismail Seyfi, Lead Software Architect, iJET International and Matt Barnes, Automation and Software Engineer, iJET International
  4. Enhancing Customer Experience with WSO2 Identity Server, Manoj Thirutheri, Director, SaaS and Tools Engineering, Nutanix
  5. Providing a Pathway from Stovepipe Systems to a Secure SOA Enterprise, Neil Custer, Senior Enterprise Systems Engineer, Eagle TG
  6. Rise to the Challenge with WSO2 Identity Server and WSO2 API Manager, Stefan Smeets, Enterprise Architect & Unit Manager, RealDolmen
  7. Journey of Migration from Legacy ESB to Modern WSO2 ESB Platform, Michael Enos, Senior Director, Techsoup and Ratnavel Sundaramurthi, Integration Architect, Aspire Systems
  8. Integrating Systems for University of Exeter Using Zero and the WSO2 Platform, Jack A. Rider, CTO, Chakray

We even had a session through Skype on Managing Verifone’s New Payment Device “Carbon” with WSO2’s EMM by Ulrich Herberg, a senior Java architect at Verifone, who couldn’t be physically present at the venue!

For the unconference sessions, Sameera had to get back on stage to do more Ballerina demos for the eager crowd. They just couldn’t get enough of it!

The attendees gathered in the main hall once again to listen to the last few keynotes of the conference.

Catheryn Nicholson, an engineer, entrepreneur, mother, and former U.S. Naval Officer, who is also the Founder of BlockCypher gave the first engrossing keynote on blockchain’s digital disruption and why developers, startups, corporations, academic institutions, and governments are all examining what blockchain technology can solve.

After exploring the past and present of blockchain technology and how it may influence your business, Catheryn made quite an exciting reveal on the future of blockchain and cryptocurrency. A group of open source developers with Harry Potter pseudonyms are currently developing a protocol (called Mimblewimble), which is still largely theoretical but has a lot of potential to solve a number of the clunkiness issues that bitcoin has. She predicts that the project will come out this year. So make sure to keep an eye out for that!

WSO2 Vice President of Solutions Architecture Asanka Abeysinghe, gave the closing keynote on a pragmatic approach to digital transformation through iterative architecture. He spoke of his experience as a consultant and evangelist of digital transformation and examined how to overcome technical and non-technical barriers to your vision by thinking big and acting small.

Before the final adieu, we made sure to recognize customers who have been with us for the past ten (of our eleven) years. Sanjiva presented Ron Murphy from eBay, Jey Bala from Kaiser Permanente, Prakash Iyer from Trimble, and Concur (who wasn’t able to attend the conference) with a small token of appreciation for taking our first steps with us, and helping us get to where we are today.

Stay tuned for news on our next conference, and hope to see you there soon!

Join the #WSO2 Identity and Access Management Tweet Jam!

In today’s connected business, increased business interactions and activities create complex environments. Because of this, identity and access management not just across organizations, but across different technologies, standards, and models becomes a key factor in an enterprise architecture.

We’re hosting our first two-hour long Tweet Jam on Thursday, December 2 at 12:00 p.m. PT. Prabath Siriwardena, the director of security architecture at WSO2, will be moderating this session and answering all questions on the topic of ‘Identity and Access Management’. Anyone with a Twitter account is welcome to join us by using the #WSO2 hashtag to accompany all tweeted questions.

TweetJamFB

Participation Guidelines

  • To participate, just follow the #WSO2 hashtag at 12:00 p.m. PT.
  • Ask any of your questions related to the topic, accompanying #WSO2
  • Start all questions with the question number and #WSO2.
    • Example – “Q1: <question> #WSO2”

About the Moderator

Prabath Siriwardena has over 11 years of industry experience that currently involves providing security architecture solutions to many of WSO2’s key customers such as Dubai eGovernment, WEST, Seagate and VeriFone. He has spoken at numerous conferences including ApacheCon, OSCON, QCon and European Identity Conference. He has also authored four books related to Apache Maven, enterprise integration, and API security.

What questions about identity and access management would you like to see at the jam? Questions can be given ahead of time by direct messaging us on Twitter.

We look forward to your participation!

Add to your calendar

Managing Identity Across the Internet of Things

 

network-782707_960_720 (1)

It’s estimated that at least 50 billion devices will be connected to the Internet by end-2020. That’s more than six times the entire population of the world! With this rapid increase of the Internet of Things (IoT), the concept of identity management has extended to the Identity of Things (IDoT).

WSO2 Director of Security Architecture Prabath Siriwardena wrote a white paper that explores the benefits, risks and challenges of implementing an IDoT solution based on the concept of “connected identity”.

He explains that through IDoT, organizations can assign unique identifiers with associated metadata to devices, enabling them to connect and communicate securely and effectively with other entities over the Internet. Your ultimate goal is to reach out to as many customers, partners, distributors, and suppliers as possible that would result in more business interactions and revenue growth. This would greatly increase the number of external digital identities that interact with your enterprise. An external identity provider can be treated as an identity silo that shares its identity data or IDoT via APIs. You first need to trust the identity provider in order to accept the given user identity. Beyond this, you need to speak the same language to transport the identity data. If not, you need to either fix the identity provider’s end to speak the same language or do the same for your own enterprise.

This is not a scalable approach, and will eventually end up in a spaghetti identity anti-pattern. To avoid this, you should build a protocol-agnostic security model. With the identity bus or identity broker pattern, your enterprise isn’t coupled to a specific identity provider or a given federation protocol. The broker maintains the trust relationships between each entity as well as identity tokens between multiple heterogeneous security protocols. This creates a common, connected identity platform that enforces controlling, auditing and monitoring of identities.

Some benefits of this pattern include

  • Frictionless approach to introducing new service and identity providers and removing existing ones.
  • Easy enforcement of new authentication protocols.
  • Ability to perform claim transformations, role mapping, and just-in-time provisioning.
  • Centralized monitoring, auditing and access control.
  • Easy introduction of a new federation protocol.

When implementing an identity broker you need to follow certain fundamentals. It needs to be federation protocol, transport protocol, and authentication protocol agnostic. Additionally, it should provide the ability to perform claim transformations, home realm discovery, and multi-option and multi-step authentication, among others.

WSO2 helps you solve identity management needs across your enterprise applications, services, and APIs by utilizing the full breadth of the WSO2 platform. By combining WSO2 Identity Server’s comprehensive security model based on OAuth 2.0 with WSO2 API Manager, you can easily build an end-to-end API security ecosystem for your enterprise. Avoid vendor lock-in and enable integration across systems with WSO2’s open source model, which acts as a fully functional enterprise identity bus.

To learn more, download Prabath’s white paper here.

Enterprise Mobility Management: Moving Beyond Traditional Mobile Device Management

Today, managing mobility is not just confined to embracing the bring your own device (BYOD) or corporately owned, personally enabled (COPE) concepts in your enterprise, or which device platform or operating system you use. The focus has shifted to more advanced strategies that enable enterprises to become connected and reach a new level of agility through digital transformation.

While the modern enterprise mobility management landscape has transformed significantly, it has also brought about more complexities.

Employees now work from locations all over the world, access data from various data centers and share this data not only through corporate networks, but also through cloud services and APIs. Because of this sense of globalization and the advent of cooler and more convenient mobile devices, enterprises started adopting mechanisms that consider all these factors in their infrastructure in order make their employees and their company as a whole more productive.

Mobile_Device_Management

This made device management not only about managing, securing and storing device data. It’s now about making mobility management part of the entire enterprise ecosystem. This means you need to think about broader aspects like governance, analytics, and identity provisioning. Such a system needs to

  • Be extensible enough to support all devices and operating system types.
  • Have a plug-in model that allows you to integrate with other tools (such as analytics and governance tools) existing in your environment.
  • Be able to moderate, approve and provision applications through a corporate app store.
  • Produce analytics dashboards, audit trails and reports to supplement business strategies.
  • Have comprehensive policy management and enforcement functionality with capabilities such as compliance monitoring, containerization, data encryption and password enforcement.

So how exactly do you go about building such a comprehensive enterprise mobility management system? By using the right tool for the right job. You need to implement a tool that not only meets the above requirements, but is also scalable enough to accommodate your enterprise’s growth. It should also be user-friendly and customizable in order to win over your employees.

Where can you find such a solution? Right here. WSO2 Enterprise Mobility Manager (WSO2 EMM) offers all of this and more. Key advantages of adopting WSO2 EMM:

  • Gives you the ability to compose, enforce and manage granular level security policies for individual and groups of devices.
  • Enables strategic decision making by making information gathered across all mobile business activities available through powerful dashboards with analytics and reporting.
  • Strengthens security through data encryption and password enforcement among other things.
  • Embraces device ownership schemes like BYOD enabling employees to be more efficient and make decisions faster while saving enterprises the procurement and data plan cost associated with each user.

WSO2 EMM is a 100% open source comprehensive enterprise-grade platform with all the capabilities you need for enterprise mobility management including device configuration management, policy enforcement, app management, device data security, and compliance monitoring.

To learn more about WSO2 EMM and its capabilities, watch WSO2 Technical Lead Prabath Abeysekara’s talk on Enterprise Mobility Management: Moving Beyond Traditional MDM at WSO2Con Asia 2016.

Modern Solution Development: The Battle Between ‘Retaining’ and ‘Changing’ Technology

In today’s fast-paced technology world, change is constant and rapid. New concepts continually emerge, gain traction, disappear, and reemerge. While it’s important to embrace this evolution, core concepts that work in older technology should not be tossed out either.  

During his closing keynote at WSO2Con USA 2015, Dr. Donald Ferguson – former vice president and CTO of Dell, identified concepts independent of the specific technology realization in order to highlight requirements that current technologies don’t meet.

image00

He noted that although concepts such as loose coupling, service delivery, and asynchronous messaging have been used for various different technologies like common object request broker architecture (CORBA), Web services, and service-oriented architecture (SOA), each of these is just an improvement, yet based on the same ideas. “The key thing when going forward is to make sure that we don’t loose some of the things that we managed to bring forward because they were good,” he adds.

He explains these similarities, improvements, and limitations are apparent when comparing SOA to microservices for instance; features such as programming style, code type, messaging type, and the use of databases are similar in both concepts whereas there are certain important distinctions in means of evolution, systematic change, and scaling. “It’s more about how you do it – the internal architecture, than the externals. With one exception – smart endpoints and dumb pipes” says Ferguson. This concept encourages the microservice community to use a light-weight message bus (a hub) that acts solely as a message router and leaves the smart part of things (receiving a request, applying appropriate logic and producing a response) to the service itself.

But as Ferguson states, “You don’t want just a hub, you want it to be active”. If you open any book on enterprise application design patterns, they first show you what not to do – a monolithic point-to-point architecture. To avoid doing this you need to connect everything through a hub that needs to be able to reformat, route and combine messages as well as understand different protocols and data types that will travel across it. This is where middleware, or specifically the enterprise service bus (ESB) becomes important.

Ferguson notes that dumb fast messaging seems more appealing than using a powerful ESB but it just repeats the fallacies of quick point-to-point connections. Using an active hub and taking advantage of middleware to do it is much more advantageous because it adds value and improves robustness, reusability and scalability.

He further adds that any organization can realize tremendous value from microservices and other new technology; however, this could sometimes result in the risk of losing benefits like interface dependency and optimized composition that emerged in the past. “This needs to be done through application design patterns and middleware that empowers them…that’s part of the value WSO2 is,”he concludes.

WSO2’s complete middleware stack includes the WSO2 integration, API management, security and analytics platforms. By leveraging these components and more you can easily develop modern solutions despite what technology you use.

To learn more, watch Don Ferguson’s presentation at WSO2Con US 2015.

 

How you can Increase Agility and Expandability with Event Driven Architecture (EDA)

From ordering your favorite kind of pizza or a taxi to manufacturing and financial processes, everything is event driven today. People expect to do everything immediately, get instant feedback on the status of their request, and interact in real-time with anybody involved in the process.

John Mathon, the former vice president of enterprise evangelism at WSO2, wrote a white paper which explores how you can keep pace with these demands by implementing event driven architecture (EDA) in your enterprise.

EDA is essentially a messaging system that notifies interested parties of events that occur in order for them to benefit from it. The publish/subscribe model was implemented in the earliest real-time event-driven systems. Anonymity, discoverability and guaranteed delivery were a few of the characteristics that made it popular.

But this simple model deemed insufficient for the demanding and varied needs of subscribers, notes Mathon. Here came the rise of the enterprise service bus (ESB), which standardized enterprise integration patterns, the business process server (BPS) which allowed messages to trigger business processes that dealt with events and business activity monitor, now named data analytics server (DAS), to monitor the health of enterprises through statistics.

These tools became standard components in an EDA and are useful even today, which is why IoT is reusing pub/subs all over again.

Screen Shot 2016-04-26 at 3

The easiest, fastest and most efficient way of implementing EDA in your enterprise is to incorporate already existing event-driven technologies. You may think writing dedicated software would be more cost efficient and cater more to your specific needs, but in the long run the cost of maintenance would be over a dozen times more than the initial cost of development.

Existing tools are designed to increase performance and reliability of your system. It’s also easy for non-programmers to use because of features such as drag-and-drop components. They can handle large loads and are robust, secure and resilient to failure.

You can choose a specific tool for a specific problem. For example, long-running processes use BPS and short-running ones use message broker (MB). Also, when the tools are combined together it can provide additional power by working together to achieve one goal.

The problem with combining tools is that they can each be large monolithic entities that require significant communication bandwidth and can cause increased load on servers. WSO2 solves this problem because all the tools you require are built as light-weight components with the same base framework making it possible to combine them in the same Java runtime.

When implementing an EDA you need to keep in mind the message flow rates and the characteristic of the message flows. Make sure not to create extremely large messages or do a lot of computation during processing. You also need to consider whether you will be designing for microservices; your architecture design depends on this. API management is another key factor that you need to keep in mind. And lastly, you need to know which tool to use for which job.

WSO2 offers a full suite of open source components for EDA to implement highly scalable and reliable enterprise grade solutions. This includes a complete middleware stack, which includes the WSO2 integration, analytics, security and API management platforms.

For more details download John’s whitepaper here.

Only 2 more weeks for WSO2Con Europe 2016!

Snip20160523_15

With only 2 weeks to go, we’re ready to rock your minds, and maybe even your bodies, at WSO2Con Europe happening at Park Plaza, Riverbank, London from June 7 to 9 this year. Get ready for three full days of knowledge, networking and entertainment at one of the biggest middleware conferences in the world!

We recently added guest speaker Roland Major, an enterprise architect at Transport for London, to the agenda, where he will be talking about Reducing Disruption to the Road Network Through the Cloud.

There’s more! Here’s what you can look forward to:

  • Inspiring keynotes from industry leaders including Vice President and Principal Analyst of Forrester Research Inc. Nigel Fenwick’s talk on Digital Predator Or Prey: Which Will Your Company Be?
  • Insightful sessions on Internet of Things (IoT), microservices, API management, security, analytics and more including 12 guest speakers from Profesia, City Sprint, Yenlo, CSI Piemonte and Emoxa among others.
  • Hands-on product tutorials by WSO2 experts covering areas such as integration, security, IoT and mobility, analytics and devops.
  • Networking opportunities with industry thought leaders, peers and WSO2 experts at the welcome reception and conference party.
  • A strategy forum that will help CxOs uncover key strategies and gain insights into how their enterprise can remain competitive and grow revenue.
  • A solutions provider track where our sponsors, including Yenlo and RealDolman, will explore customer use cases on partner driven projects built around the WSO2 platform.

Visit https://eu16.wso2con.com/ for more information about the agenda, speakers and registration.

Enabling Microservice Architecture with Middleware

Microservices is rapidly gaining popularity among today’s enterprise architects to ensure continuous, agile delivery and flexible deployments. However many mistake microservice architecture (MSA) to be a completely new architectural pattern. What most don’t understand is that it’s an evolution of Service Oriented Architecture (SOA). It has an iterative architectural approach and development methodology for complex, service-oriented applications.

microservices

Asanka Abeysinghe, the vice president of solutions architecture at WSO2, recently wrote a white paper, which explores how you can efficiently implement MSA in a service-oriented system.

Here are some insights from the white paper.

When implementing MSA you need to create sets of services for each business unit in order to build applications that benefit their specific users. When doing so you need to consider the scope of the service rather than the actual size. You need to solve rapidly changing business requirements by decentralizing governance and your infrastructure should be automated in such a way that allows you to quickly spin up new instances based on runtime features. These are just a few of the many features of MSA, some of which are shared by SOA.

MSA combines the best practices of SOA and links them with modern application delivery and tooling (Docker and Kubernetes) and technology to carry out automation (Puppet and Chef).

In MSA you need to give importance to how you scope out a service rather than the size. The inner architecture of an MSA addresses the implementation architecture of the microservices, themselves. But to enable flexible and scalable development and deployment of microservices, you first need to focus on its outer architecture, which addresses its platform capabilities.

Enterprise middleware plays a key role in both the inner and outer architecture of MSA. Your middleware needs to have high performance functionality and support various service standards. It has to be lean and use minimum resources in your infrastructure as well as be DevOps-friendly. It should allow your system to be highly scalable and available by having an iterative architecture and being pluggable. It should also include a comprehensive data analytics solutions to ensure design for failure.

This may seem like a multitude of functionality and requirements that are just impossible to meet. But with WSO2’s complete middleware stack, which includes the WSO2 Microservices Framework for Java and WSO2 integration, API management, security and analytics platforms, you can easily build an efficient MSA for your enterprise.

MSA is no doubt the way forward. But you need to incorporate its useful features into your existing architecture without losing applications and key SOA principles that are already there. By using the correct middleware capabilities, enterprises can fully leverage the advantages provided by an MSA to enable ease of implementation and speed of time to market.

For more details download Asanka’s whitepaper here.