Emarketeer is a marketing software platform that “streamlines the way leads are generated and the way business is won.” The solution provides a range of marketing modules, including event management, surveys and evaluations, marketing automation, mobile apps, and lead exploration. With eMarketeer for example, you can design, schedule, automate and execute your entire event process before, during and post the event. eMarketeer also offers service packages to maximize customer use and increase expertise.

Transforming the Business with Microservices

eMarketeer, an e-commerce company offering a marketing software platform with over 1500 customers worldwide, recently has undergone a transformation with migration from 10-year old legacy product on premises to a serverless platform on AWS Cloud and the go-to-market of its new Leadexplorer solution, which provides insights about companies visiting your website. 

Supporting a New Product Introduction 

According to eMarketeer’s CTO, Leadexplorer was built on 100% serverless. The challenge for eMarketeer was getting visibility into every stage of production and supporting the introduction of Leadexplorer. The goal was to integrate existing and new products so that users would have one login and seamless switching between products.

The company was migrating from PHP servers on AWS EC2 instances to serverless and AWS Cloud. The migration of data was prioritized and segmented over time. The migration was done by moving different domains of the applications into serverless microservices. In some scenarios, it made more sense to use containers and, in these cases, eMarketeer used AWS Fargate. The container benefit was the ability to package and power a large amount of data easily. 

Since its introduction at eMarketeer, serverless has worked well. “It’s easy to build with microservices and isolate components and minimize the problem space. It is also cost-effective,” explained Magnus Baudin, eMarketeers CTO. But, with serverless, there is no central way to see what’s in production and monitor it. “First, I tried AWS X-Ray but it does not have unified reporting, which I needed. Our developers then built their own monitoring tool that integrates with X-Ray and works fairly well but still is lacking somewhat,” Magnus said.

Controlling the Unexpected

Magnus was looking for a monitoring solution for serverless that would allow him to see everything in production, provide insights through analytics, and alert 24×7 so that “the unexpected does not cost us dearly. With real-time alerting in Epsagon, we can act more quickly to identify and resolve memory issues and timeouts that cost us money,” Magnus noted. “As we add services, we use Epsagon to automatically monitor, troubleshoot and fix in seconds issues as they arise.” 

“As we add services, we use Epsagon to automatically monitor, troubleshoot and fix in seconds issues as they arise.”

Visibility into Production Environment

eMarketeer easily can check the general status of its environment in the dashboard, as well as see errors in Issues Manager, such as cold starts or slow functions, which impact productivity and user experience. Epsagon Trace Search takes developers to the source causing the issue. eMarketeer also uses AWS AppSync to synchronize data for mobile and web apps and plans to explore Epsagon’s integration with App Sync for tracing and visibility.

Monitoring Functions in Development and Production

Eight, very experienced, developers use Epsagon daily. With separate Epsagon accounts for production and development, each team can receive filtered information and alerts and see issues specific to the team’s role and function. Moving forward when developers touch a service, they will add Epsagon to the service.

Going to Market Much Faster with Epsagon

Magnus recommends deploying and using Epsagon service by service. “Testing before you go to production is important. It’s easier and guarantees success.”

eMarketeer uses Epsagon in development because it is much easier to see the logs.  

“We were trying to add logs to every function, but we forget and it is tedious to do. While you can use logs to find the source of the issue, it just takes too much time,” Magnus explained. 

Epsagon automatically records the logs and provides the payload data. “You can use the payload information to see what’s happening locally,” Magnus said.

“You can use the payload information to see what’s happening locally.”

“In addition, our new product is going to market much faster. There is more trust regarding what is happening in production. We can see it in the Architecture View.”

And developer velocity has increased. “When we have a problem, my developers can fix anything in at least half the time it used to take. They are much more efficient, especially when locating an error.”

The major business benefit:” I worry less about how production is going and spend more time building new services, which is the whole point of the migration from legacy to containers and serverless.”

” I worry less about how production is going and spend more time building new services, which is the whole point of the migration from legacy to containers and serverless.”