We are a Westshore-based group of talented designers and developers devoid of heavy corporate structures, approval processes and tight boundaries. Noted by our clients as giving that “little extra”, we seek to ship customized solutions, build sustained client relationships and deliver strategic counsel with zealous service.
Looking for a no-politics zone to do your best work? Mercury is the place for you.
HTML5It all starts with clean, semantic, standards-based markup. Local storage, geolocation and native media players are some of our favorites.
CSS3
Separating content from presentation with judicious use of SASS use (mixins, partials and variables) keeps our UIs robust. And BEM’s not so bad, either.
JavaScript
Bundlers and transpilers like WebPack and Babel support our use of the latest JavaScript and versions of React, Angular and Knockout libraries.
Robust data layers go a far way in these parts – without them we just have websites, not web applications.
SQL ServerSQL Server, whether on prem, installed on IaaS VMs or consumed via SQL Azure provides the hearty data storehouse we need for scalability and rapid querying.
MySQLIt’s not all about SQL Server if you want to get relational with it – MySQL definitely show up around the Mercury shop, too.
MongoWe have much love for Structured Query Language but NoSQL is cool, too. And there’s nothing like Mongo for a document database, if you ask us.
Application code, service layers and even middleware are big parts of what we do around here. We like to keep the business logic clean and separated and our services RESTful.
.NET and C#C# and the .NET Framework are old friends of ours – while not as trendy as the JavaScript frameworks it’s hard to do better when you need to roll business logic, marshal data or automated processes.
MVCWebForms and ViewState are history – you won’t find them around here. But if you want to roll with .NET then MVC is your friend – and it’s good for JavaScript development, too.
WebAPIYa, we went the WCF route. Then we simplified with WebAPI and never turned back.
NodeLow overhead and thin requirements – there’s a lot to like about Node. And there’s nothing like being able to share JavaScript between the data, application and interface tiers.
We love the web. Like, really love the web. But sometimes you have to code to the platform to really get the most out of it. Here’s how we do it.
React JSReact Native extends that elegance of React development for cross-platform native development. Share common code with your web application and nearly 100% across iOS and Android with React Native.
XcodeWe love the web and we love React Native but sometimes you need to get straight down in Xcode to Objective C and Swift for your app or custom React Native components.
Android StudioMarket domination isn’t easy but Android does it well. We rock Java in Android Studio to build out custom native Android apps and React Native components even more often than iOS.
Words about what we use systemically.
GitDistributed version control for the win.
Continuous Delivery / DevOpsBuild, integrate and push to testing, staging and production environments on every code commit.
Azure / Amazon Web ServicesDeploy to the cloud.
SeleniumTest every key function of the application on every release so you know you’re not pushing out regressions.
At Mercury we have been utilizing Azure DevOps for our CI/CD process and have seen the implementation of Pipelines change and continuously improve. In this series I’ll be walking through setting up an end to end pipeline using multi-stage pipelines in YAML
Having 4, 6, 12, or even more accounts with individual invoices, billing methods, support contracts, reserved instance pools, and everything else that comes along would be enough to drive anyone crazy. Luckily, AWS offers a great solution that is easy to set up and manage.
Recovering from a production site outage during peak hours can be a daunting task. While everyone wants a 100% uptime, it can be near impossible because of things out of our hands. However, we can plan for these potential outages and architect the application and infrastructure to allow for a quick recovery.
In the second installment of our multi-part post on using multiple AWS accounts in your organization we’re going deeper into the technical side of creating cross-account roles for IAM authentication.
Considered to be best practices in AWS, as well as one of the most popular ways to fully maximize the potential of AWS, is to utilize multiple accounts. Accounts can be set up as either per-organization, per-department, or even per-application and can be utilized to logically and physically separate any resources to fit your organization’s needs. This, combined with master-account billing and properly utilizing Tags, can allow you to be as separate, yet collected, as you see fit.
Feature flags are a powerful tool with many uses, they should be thoughtfully considered as a development tool. Feature Flags allow developers to achieve continuous deployment and clients see great value in the speed at which issues can be resolved.
Start progressing your career now by joining a talented group of professionals who craft and ship incredible web and native applications.
View Open Positions
