Building a Common Message Solution with MongoDB at Vertafore

Building a Common Notification
Solution with MongoDB
John Gao | September 16, 2014
1 © 2014 Vertafore, Inc. and its subsidiaries.
Steven Engelhart

Agenda
1 About Vertafore
2 Problem Statement
3 Design and Implementation
4 Product Demo
© 2014 Vertafore, 2 Inc. and its subsidiaries.

The Company
#1 software supplier to independent insurance
44 years transforming insurance
80 of the top 100 carriers use Vertafore
96 of the top 100 agencies use Vertafore
1,000 agencies adopted AMS360 in 2012
20,0000 customers use Vertafore
13,000,000 Producer Lifecycle Mgmt transactions
50,000,000 real-time transactions

Vertafore Solution Suite
Agency Carrier MGA/Wholesaler
Content and Business
Process Management
Business Intelligence
Agency Management,
Download and Real-time
Benefits Management
Connectivity
Process Management
© 2013 Vertafore, Inc. and its subsidiaries. 4
Process Management
Business Intelligence Business Intelligence
Agency Management,
Policy Issuance Policy Issuance
Producer Lifecycle
Management
Producer Lifecycle
Management
Producer Lifecycle
Management
Comparative Rating Rating Interfaces Rating Management
Reference Libraries Reference Libraries Reference Libraries
Producer Tools Producer Tools Producer Tools

Breaking the Mold
• Need solutions to be re-usable
• Breaking the traditional SQL solution development
pattern
• Freedom to choose the right technology to solve the
problem

Design Goals
• Simple and Easy to User API
• Performance and Scalability
• Need to support both pull and push

Design Decisions
• “RESTful” web service using OData
• MongoDB for database
• RabbitMQ for queue to support mobile push

Why MongoDB?
• Performance and scalability
• No object to relational model translation
• Object model can be very flexible
• Supports all major platforms
• Excellent .NET and LINQ support

Overall Architecture

Object Model – NotificationMessage
• Type – admin, user, …
• Priority – normal, critical, …
• Author
• Publisher
• Recipient
…

Object Model – UML Diagram

MongoDB Document – NotificationMessage

Message Service – Layered Diagram

Odata Layer - Controller
public class NotificationMessagesController : ODataController
{
public IQueryable<NotificationMessage>
Get(ODataQueryOptions<NotificationMessage> query);
public async Task<NotificationMessage> Get([FromODataUri]
string key);
public async Task<IHttpActionResult> Post([FromBody]
NotificationMessage message);
public async Task<IHttpActionResult> Put([FromODataUri]
string key, NotificationMessage entity);
public async Task<IHttpActionResult> Patch([FromODataUri]
string key, Delta<NotificationMessage> patch);
}

Domain Layer – Domain Services

Data Layer - Interface
public interface IRepository<T, U>
{
T Get(Expression<Func<T, U>> keyExpression, U key);
IQueryable<T> Get();
T Create(T entity);
T Update(T entity);
bool Delete(T entity);
}

Data Layer - Implementation
public MongoRepository(MongoDatabase database, string
collection)
{
Collection = database.GetCollection<T>(collection);
}
public T Get(Expression<Func<T, U>> exp, U key)
{
return Collection.FindOne(Query<T>.EQ(exp, key));
}
public IQueryable<T> Get()
{
return Collection.AsQueryable();
}

How Are The Three Layers Linked?
private void InitializeStructureMap(IQueryRules rules)
{
DomainStructureMap.Map(container,
(ConfigurationSection)ConfigurationManager.GetSection("Notificat
ionCreatedEventQueue"));
DataStructureMap.Map(container,
ConfigurationManager.ConnectionStrings["MongoDB"].ConnectionStri
ng);
});
}

Structure Map – Domain
public static void Map(IRegistry container,
ConfigurationSection notificationConfigurationSection)
{
;
}

Structure Map – Data
public static void Map(IRegistry container, string dataConnection)
{
();
container.For<IRepository<MessageHistory, string>>()
.HybridHttpOrThreadLocalScoped()
.Use(r => new MongoRepository<MessageHistory,
string>(r.GetInstance<MongoDatabase>(), "MessageHistory"));
}

Bson Class Map
BsonClassMap.RegisterClassMap<NotificationMessage>(map =>
{
map.SetDiscriminator("NotificationMessage");
});
BsonClassMap.RegisterClassMap<UserRecipient>(map =>
{
});
// Other mappings omitted for clarity

MongoDB Replica Set

Usage Examples – Linq Queries
NotificationMessages.OrderByDescending (nm => nm.CreatedAt)
.Skip(100).Take(50);
NotificationMessages.Where(n => n.Id == "54132e3bf11fbc138c8f7448");
NotificationMessages.Where(x =>
x.Summary.Contains("New opportunity")).Take(10);

Usage Examples – Odata Queries
https://ServiceEndpoint/NotificationMessages()
?$orderby=CreatedAt desc&$skip=100&$top=50
https://ServiceEndpoint/NotificationMessages('54132e3bf11fbc138c
8f7448')
https://ServiceEndpoint/NotificationMessages()
?$filter=substringof('New opportunity',Summary)&$top=10

Usage Examples – MongoDB Queries
"op" : "query",
"ns" : "NotificationService.Messages",
"query" : {
"$query" : {
},
}
},

Mobile Push Service
• Mobile device registration service
– Register mobile device
– Odata web service
– Registration stored in MongoDB
• Windows service
– Monitor queue message
– Send message that has mobile destination to
Apple or Google for actual delivery

Device Registration – MongoDB Document
{
"_id" : "54174aad92d00721d4ef7315",
"AppId" : "SeattleDemo",
"VendorId" : "PipelineManager - Agent",
"CreatedDt" : ISODate("2014-09-15T20:23:08.747Z"),
"ModifiedDt" : ISODate("2014-09-15T20:23:08.747Z"),
"DeviceData" : {
"Data" : null
}
}

Mobile Push Service - Workflow

Overall Dev Experience
• What we liked
– Very easy to setup
– Great documentation and online resources
– Great community support
– No more mismatch of object to relational
– Quick development cycle
– Flexible schema works well

Overall Dev Experience
• Things that could have been better
– 2.6 release felt to be rushed out.
– No out of box encryption support
– No MongoDB Management Service (MMS) on
windows

Operations Experience
• Hosting team was able to ramp up quickly
• Simple installation
• Quick and intuitive deployment of packages
• Easy to scale out

Push Notification Demo

Questions

Building a Common Message Solution with MongoDB at Vertafore

Recommended

Recommended

More Related Content

Similar to Building a Common Message Solution with MongoDB at Vertafore

Similar to Building a Common Message Solution with MongoDB at Vertafore (20)

More from MongoDB

More from MongoDB (20)

Recently uploaded

Recently uploaded (20)

Building a Common Message Solution with MongoDB at Vertafore

Editor's Notes